You keep using that word Governance
summary
Practical checklist for project governance: publish a visible process and dispute path (how proposals are raised, who adjudicates, and an audit trail), maintain a public maintainer roster and succession plan, record durable metadata for releases (provenance, licenses, contributors), and ensure an accessible neutral contact for escalation. References include OW2 and WTO/TBT accreditation-style criteria; expect semi-distributed enforcement rather than full automation, and plan for archive durability so agreed versions remain findable.
AI-written summary · about
chapters (10)
- 0:00Introduction to governance
- 1:09Why focus on fairness
- 3:16Governance as predictability
- 7:53BDFL and alternatives
- 13:03To-do list for governance
- 19:43Self-governed communities
- 24:02Q&A and next steps
- 26:14Durability in governance
- 31:17Governance failures
- 34:25Summary and closing
related talks
23mGood Governance Practices for Healthy Open Source Projects
38mOpen Source Governance for Software Engineers
31mOperationalizing Open Source Projects: When the Rubber Meets the Road
38mBuilding a successful OSPO with the Good Governance Initiative Handbook
05mThe Slings and Arrows of Open Source
30mA Strategic Approach to Assessing Viability of OSS Projects
49mCommunities Over Code: How to Build a Successful Project
30mHow to Drive Consensus & Transparency in OpenSource Communities