Changing the governance model of an established project
summary
Mautic removes company control and refactors governance: it keeps fiscal hosting with Open Collective, transfers brand and trademarks there, and runs elections and votes through a custom desim portal. The project supports ~10,000 Slack members and ~40,000 sites, launched the Community Portal, and 169 people join it so far; 45 are paid or corporate members and 14 qualify via contributions. Membership rules lock in one-member-one-vote, $100/year (Big Mac index for discounts), staggered council terms, and transparent two-week decision windows.
AI-written summary · about
chapters (16)
- 0:00Introduction to governance
- 1:03Defining project governance
- 2:28Initial governance model
- 4:32Company stepping back
- 7:20Researching governance options
- 9:26Refactoring governance model
- 12:14Structuring community hierarchy
- 13:39Electing the new council
- 14:43Decision-making framework
- 15:45Voting eligibility rules
- 17:35One member one vote
- 18:40Drafting governance model
- 20:04Key lessons learned
- 21:28New governance in action
- 22:30Future sustainability plans
- 23:15Q&A session
related talks
33mLet's make this the year of the contributor experience!
53mBringing Mautic and Drupal closer together in an open DXP
23mGood Governance Practices for Healthy Open Source Projects
29mBuilding and scaling Hare's community governance
30mHow Open Collective moved from a for-profit to a non-profit
13mMVG - Minimum Viable Governance for Your Organization’s Open Collaboration Needs
32mFreeing software with governance, for public administrations
30mKeynote – Pia Mancini