This is an overview post which allows you to quickly jump to the relevant threads where we are discussing parts of this new governance model proposal.
Note that anyone is welcome to propose an alternative governance model in the same way - create a GDoc and write up the model, and then make a parent post in this category with individual threads for each section.
Each section will be open for comments and discussion as separate forum threads - with an emphasis on respectful discussion and finding a way to come to a consensus - for a period of two calendar weeks - closing on Wednesday, 7th June, at which time we will share a first draft of a proposal for voting.
EDIT: The time period for consultation has subsequently been extended to the 23rd June 2023 (making it 4 weeks total).
You can read the overview of the discussions that we have been having in #wg-governance on Slack in this document.
You can read a full version of this proposal including explanatory annotations here. NOTE: This document will now be out of date - please refer to the individual forum threads for the most up to date changes based on community discussions.
As the proposal is covering a lot of areas, we have decided to break it out into sections so that we can debate and discuss each section and come to a consensus together.
Note for reviewers:
This is a lengthy document so donât expect to read it all in one go.
It is in a certain order because:
- You need to define membership types before you can talk about who can and canât vote, and who can and canât hold leadership positions
- You need to define decision making principles before you can define how voting works
- You need to define voting rights before you can define how teams and working groups come into being or get dissolved
- You need to define how teams are created and disbanded before you can define leadership roles, durations and how elections are held
- You need to define all of the above before you can define how a council would function and why it is needed
- You need to define all of the above before you can define how the governance model might be changed in the future
Currently this does not include the Project Lead role - this is something that we need to discuss as to how we want to move forward with that role definition and position in the community governance model.
Sections
Introduction:
Welcome to Mautic!
Within the Mautic project, our governance is driven by our core values:
- Openness
- Transparency
- Integrity
- Fairness
- Respect
- Engagement
- Representation
- Action over inaction
- Project over people and companies
1. Membership
2. Decision making
3. General Assembly
4. Teams and working groups
5. Council
6. Record keeping
7. Amendment of this Governance Model
8. Tooling that might support this proposal
Contributors to this governance model (so far):
These people have been involved in discussions in the Governance Working Group Slack community, which has informed many of the parts of this proposal. Thank you all for your involvement and discussions/debate!
Ruth Cheesley
Sven Döring
Norman Pracht
Joey Keller
IonuĆŁ OjicÄ
Mthobisi Glen Sehlabela
Khalid Zamer
Daniel Lord
Resources and references
Open source project governance examples and resources
https://www.python.org/psf/bylaws/
https://peps.python.org/pep-8002/
https://medium.com/the-node-js-collection/healthy-open-source-967fa8be7951
https://www.zotero.org/groups/2310183/foss_governance/library
https://governingopen.com/
https://github.com/github/MVG
Decision making models
https://en.wikipedia.org/wiki/Direct%20democracy
https://en.wikipedia.org/wiki/Representative%20democracy
https://en.wikipedia.org/wiki/Garbage%20can%20model
https://en.wikipedia.org/wiki/Consensus%20decision-making
https://en.wikipedia.org/wiki/Instant-runoff%20voting
https://en.wikipedia.org/wiki/Anarchist%20law
https://en.wikipedia.org/wiki/Referendum
Org structures
https://en.wikipedia.org/wiki/Flat%20organization
https://en.wikipedia.org/wiki/Cooperative
Governance tools
https://communityrule.info/templates