The Slings and Arrows of Open Source
summary
Open source projects survive better when maintainers document governance and runbooks, automate repetitive tasks and intentionally mentor one or two successors to carry releases and roadmaps. Declaring concrete availability hours and a written exit/transition plan reduces single‑person bottlenecks and makes handovers smooth, while scheduled, periodic disconnection lowers burnout and keeps contributions steady. The talk uses a Shakespearean framing but delivers practical prescriptions: concrete artifacts, automation, delegation and boundaries that let projects continue when an individual steps back.
AI-written summary · about
related talks
06mThe Open Source Baggage We Carry
23mGood Governance Practices for Healthy Open Source Projects
44mOf Queens and Other Benevolent Dictators – the Role of Succession Planning in Open Source Community
46mConducting Your Open Source Project
29mDon't Be A Hero: Sustainable Open Source
46mMove Slow and Try Not to Break Each Other
25mSustaining Open Source Software: Exploring Community, Financial, and Engineering...
15mLessons Learned from Cultivating Open Source Projects and Communities