Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Needs/want of constituencies #20

Closed
mhdawson opened this issue Sep 17, 2020 · 5 comments
Closed

Needs/want of constituencies #20

mhdawson opened this issue Sep 17, 2020 · 5 comments

Comments

@mhdawson
Copy link
Member

As agreed in meeting this week next focus area should be:

Discussed that next focus area should be what does each constituencies need

* This should actually include #16 as the Node.js maintainers are one of the constituencies
   listed.
* Next meeting to brainstorm on what each constituency needs
* Action -> Darcy to setup boards, for each constituency , with following headings:need, don’t
  need, want, don’t want

Created this issue so that it's on the agenda for next time.

@sheplu
Copy link
Member

sheplu commented Oct 1, 2020

Link to the FunRetro so that anyone can update / add new elements if needed:
https://funretro.io/publicboard/QnR9oTPWKKfMnff3RxvPiNCY3Om2/3c3f4803-9259-42b4-8ea9-2a2f43ab4c36

@mhdawson
Copy link
Member Author

mhdawson commented Oct 1, 2020

Fun retro we used

https://funretro.io/publicboard/QnR9oTPWKKfMnff3RxvPiNCY3Om2/3c3f4803-9259-42b4-8ea9-2a2f43ab4c36. We'll continue to work on this next time.

screecap of what it looked like at end of meeting:
constituent needs

@mhdawson
Copy link
Member Author

image

@mhdawson
Copy link
Member Author

Added, list from discussions today.

@mhdawson
Copy link
Member Author

Getting more input through #48 - closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants