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

Document the flow of our calls and types of roles people can fill in Design & UX WG #296

Open
jwflory opened this issue Apr 8, 2021 · 0 comments
Assignees

Comments

@jwflory
Copy link
Member

jwflory commented Apr 8, 2021

Summary

Add a basic description of our Working Group and the ways people can participate on the Sustain WG profile.

Background

We had a good, albeit somewhat rushed, conversation about how we plan and organize the WG meetings. But to run a meeting is a lot of work, and @Erioldoesdesign has graciously been doing this for us for the past few months. To build a healthier and more inclusive community, we want to cycle the responsibilities to avoid burnout of any one person in this role.

The goal here is that anyone who chairs a meeting one week should feel like they could miss the next month's meeting if they had to! Everyone should feel empowered to take a day off if they need it.

Details

We should write some things down! We have a nice Taiga board and Google Doc notes, but we could describe our calls and the kinds of roles people may play in the Working Group. Writing these things down aims to reduce the knowledge barrier of how the calls are run and explain how our labor is divided in the WG.

Outcome

Easier for new folks to climb on-board and transition to a leadership role if desired!

@jwflory jwflory self-assigned this Apr 8, 2021
jwflory added a commit that referenced this issue Apr 9, 2021
This commit adds clarity into the things we do as a Working Group and
also explains how a new-comer could participate with the Working Group.
The "How to get involved" section is sorted in order of difficulty,
where items on the top are easiest to complete and take the lowest
commitment. Items towards the bottom require some degree of commitment.

This is a first pass at documenting how we work, definitely room for
improvements and other iterations here. 😀

Closes #296.

Signed-off-by: Justin W. Flory (he/him) [UNICEF Innovation] <jflory@unicef.org>
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

1 participant