Of Queens and Other Benevolent Dictators – the Role of Succession Planning in Open Source Community
summary
Argues that risk comes less from topic and more from attrition: a small core leaving breaks mature projects as badly as single-maintainer failures, with thousands of tiny packages creating systemic fragility. Cites OpenStack elections, a widely used Haskell GitHub Action that scaled unintentionally, CNCF governance patterns and the EU Cyber Resilience Act as pressures. Recommends lowering mean time to dopamine, designing polycentric governance, documenting users and roles, and baking succession into project processes to preserve continuity.
AI-written summary · about
chapters (14)
- 0:00Benevolent dictators in open source
- 2:08Open source career inflection points
- 7:32Code to policy and global impact
- 11:48Continuity versus sustainability
- 15:24Contributor onboarding speed
- 17:52Community inertia and dilemmas
- 21:46Open source fragmentation tensions
- 25:02Governance principles for resources
- 31:00Closing thoughts on cooperation
- 32:04Solo maintainer obligations
- 35:05Bureaucracy versus sustainability
- 37:11Speedrunning open source infra
- 40:10Governance improvements
- 41:59Q&A
related talks
31mPassing the Baton: Succession planning for your project
23mGood Governance Practices for Healthy Open Source Projects
15mLessons Learned from Cultivating Open Source Projects and Communities
05mThe Slings and Arrows of Open Source
25mLessons Learned from Cultivating Open Source Projects and Communities
25mLessons Learned from Cultivating Open Source Projects and Communities
36mThe Feedback Loop: Growing healthy open source projects
21mLeading and Growing an Open Source Comunity