Circles (Working Groups)

[benhylau]

Proposal

The following proposal was unanimously approved by @benhylau @mikemh @osb @wouter @aaronhirtenstein @dvdjaco @petter @chris @Yasuaki at our All Hands meeting on July 9, 2020.

@benhylau

Our meeting notes from today’s meeting is here . I believe @aaronhirtenstein and I both believe that ~3 Circles would be the right number for us at this stage, and they should map to critical functions of Meet.coop.

My rough proposal:

• Organizational Operations
  • @wouter @osb @mikemh @aaronhirtenstein …
  • Governance model, financial processes, organizational mission, All Hands meetings
• Product Strategy and Services
  • @osb @melissamcnab @wouter @hng …
  • Determine service levels, reseller program, roadmap, branding, external communications, events liaising
• Technology Operations
  • @chris @decentral1se @Yurko @hng …
  • Manage the infrastructure and GitLab spaces, development of new features, answer technical questions on forum, etc.

Then there is the “everyone” circle that is our general assembly aka. All Hands style meeting. Each other these groups have authority to make decisions within their clearly designate domain of responsibility and decide things based on consent (consent is the absence of disagreement rather than consensus of agreement).

Each circle also needs a leader , who is committing the most attention to ensure things move forward. In my opinion it is most important that this role within a Circle is the first waged position. @aaronhirtenstein also mentioned facilitator , secretary , and delegate positions in Circles, which we can add later.

Clarifications

• Organizational Operations are responsible for convening All Hands meeting, not that All Hands are part of the Organizational Operations circle
• The specific accounts under each circle serve as examples, and do not indicate their actual membership

Voting

• Agree
• Abstain
• Block