The Feedback Loop: Growing healthy open source projects
summary
Argues that healthy projects adopt a one-OSS vs two-OSS governance model, favor positive-sum solutions over zero-sum shortcuts, and actively turn frustrated users into contributors. Gives concrete tactics: Shawn Larkin’s de‑escalating tweets for webpack bugs, Rust’s move to community-led governance away from Mozilla control, and Ember/LinkedIn/Skylight examples where small documentation fixes grow into core contributions. Recommends changing decision rules, empowering employees to file pull requests, and measuring success by contributors gained rather than walls erected.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:22Open Source Pixie Dust
- 1:03The Feedback Loop
- 2:16The Grove
- 4:44Open Source Burnout
- 5:22Webpack
- 5:37Growing a thick skin
- 6:43First reaction
- 7:30CCTV feed
- 8:00What does it take
- 9:14Example
- 10:37Burning out
- 11:33Maintainer vs Community
- 11:54Game Theory
- 12:05Zerosum Solutions
- 15:13Treating Users as part of the solution
- 16:10Relationship between community and companies
- 17:00Rust
- 20:54Is independence good
- 22:44Company perspective
- 24:22Onramps
- 25:38Examples
- 28:32Celebrating Success
- 29:21Growing Your Project
- 29:54Open Source Funding
- 31:42Cast a Wide Net
- 33:51OSS Model
- 34:37Conclusion
related talks
21mLeading and Growing an Open Source Comunity
13mOpen Web, Open Source, Open Communities
26mBuilding Open Source Communities
25mLessons Learned from Cultivating Open Source Projects and Communities
28mGrowing Open Source Seeds
23mGood Governance Practices for Healthy Open Source Projects
20mHumans of Open Source
49mCommunities Over Code: How to Build a Successful Project