Whassup owls 
! Thanks @WhyldWanderer for kicking this off with your proposal and @mitch for your great feedback…
I was working with @freshelle on updating the Giveth Organizational Chart … I think getting clear about our Circles, Working Groups, leads/stewards is an important next step before pushing this out for helping onboard new contributors.
Spoke to Griff about Operations… this is mostly Kay’s role and it requires managing/maintaining servers… making sure our DApps run and the discord server is ok. It shouldn’t really be a separate working group and imho should fall under “Platform” or more specifically “Development”. Other operational things (like managing the forum or livestreams) can be part of Communications/Community.
I think Project Verification shouldn’t be it’s own working group, but can be part of “Platform” or “Community”… This is like a separate project.
Anyway, I’d to suggest the following revisions/simplifications to the working groups. I think we should create working groups based more on the work being done or the skills of people in that working group - not on the specific project in which those skills are being. It would make things less complicated because, for example, to build a DApp like giveth.io, we need people to make decisions on what should be included (governance)… we need designs, we need developers, we need testers, we need text to be written on the DApp (comms), we need to share updates with out community, we need to support users getting on the DApp (support).
So we have skillset working groups (below), and we have Giveth projects (giveth.io, project verification, giveth TRACE, GIVgarden, etc.)… and we have people from each working group working on different projects. The working groups don’t need to have separate meetings - we can meet for the projects - but we can have sync meetings if it seems useful/necessary.
Anyway, with no further ado, I propose the following:
Community Circle
- Communications - writing all things, emails, text on the DApps, blog posts, docs, forum posts
- Community Support - supporting Giveth users, supporting new contributors
- Conflict Resolution - Gravity
Platform Circle
- Design - branding, DApp design, design for comms
- Development - giveth.io dev, TRACE dev, operations, GIVeconomy dev (liquidity mining, garden, GIVbacks)
- User Testing - supporting devs with user testing
- Project Management - can have one PM per project
GIVernance Circle
- Governance - including anyone who wants to have a say
- DAO - token voting in the GIVgarden and Aragon
LMK what you think? I’m open to adding another Community WG called “outreach” as per Mitch’s suggestion as well. Open to reworking this more with some feedback… this is just my first best attempt