Don't Be A Hero: Sustainable Open Source
summary
Maintainers face becoming single points of failure for projects like Double Union and tools such as bridge troll; mitigation is concrete: add a CONTRIBUTING README, inventory every maintainer task so it can be handed off, use a shared password manager and deploy account, and triage issues into bite‑sized tasks. Project management choices matter (Pivotal Tracker vs GitHub issues), and rapid code review predicts retention — Mozilla finds 48 hours vs 7 days is the break point for repeat contributors.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:50Open source heroism
- 4:17Dangers of hero culture
- 7:09Recovering from heroism
- 8:12Documentation for collaboration
- 10:40Maintainer duties and delegation
- 11:23Project management challenges
- 13:51Recruiting contributors
- 15:39Sharing responsibilities
- 17:48Growing contributors
- 19:12Sustainable contribution habits
- 20:16Importance of retrospectives
- 21:44Celebrating contributions
- 22:47Tips for new contributors
- 25:33Motivation and accountability
- 27:24Sustainability planning
- 28:49Conclusion
related talks
14mWhat can we do to make Open Source more sustainable?
25mSustaining Open Source Software: Exploring Community, Financial, and Engineering...
33mA Third Way For Open-Source Maintenance
36mWho Will Maintain the Future? Tackling the Graying of Open Source Software
43mJust Keep Swimming: Don't drown in your open source project!
35mTending Your Open Source Garden
41mFrom Users to Maintainers - Tales from the Open Source World
31mMaintain Less, Mentor More: Community Building Techniques from Open Source