Sustaining Open Source Software: Tools for Change
summary
Argues that maintenance beats creation and gives a checklist for assessing health of OSS projects with concrete fixes: add governance, conflict‑resolution, and support contracts. Cites research showing 70% of projects maintained by three or fewer people, warns those are single‑point failures. Points to regulatory levers like the EU Cyber Resilience Act and Australia’s cyber rules that force vendors to pay for fixes. Recommends saying no to unpaid maintenance and selling commercial support instead.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:03Why sustaining open source matters
- 2:06Open source economics problems
- 3:29Software as a common pool resource
- 6:17Artifacts vs living ecosystems
- 7:42Open source maintenance burden
- 9:29Why people contribute for free
- 10:56Governing open source commons
- 12:18Eight principles for sustainability
- 13:21Designing congruence
- 14:24Conflict resolution in open source
- 15:06Collective choice in governance
- 16:10Change must come from outside
- 17:11Government regulations
- 18:37Maintenance over creation
- 19:41Ubiquity of open source
- 20:44Sovereign tech and collective action
- 21:47Public health for software quality
- 22:08Moral case for saying no
- 23:33Legislation ending impunity
- 24:15Summary
- 24:58Q&A corporate obligations
- 26:21Q&A liability and legislation
- 27:45Q&A passion vs monetization
related talks
25mSustaining Open Source Software: Exploring Community, Financial, and Engineering...
14mWhat can we do to make Open Source more sustainable?
36mSOS Sustainable Open Source
41mArchitecting for the Long Haul: Technical Strategies for Sustainable Open-Source Support Models
30mThe Real Costs of Open Source Sustainability
42mWhat Do Legislations Have To Do With Tackling Maintainer Burnout?
39mSOS: Sustainable Open Source
36mFreedom vs Sustainable Business: A Candid Necessary Debate