A guide to Indie Open Source Software
summary
Argues that indie open source succeeds by specific practices: diversify core team membership across companies, insist on 20% time for maintainers who also ship apps, and avoid big rewrites after an 18‑month Rails‑style stall. Describes building an automated release pipeline and adopting six‑week release cycles with master/beta/stable channels (like Chrome), and shipping Ember features (ES6 modules, promises, Ember CLI) incrementally so most users stay on the latest or one version behind. Results: faster feature delivery and fewer ecosystem forks.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:14Dont die
- 2:15Diversify
- 5:33The most effective projects
- 6:24The core team
- 7:49Who has legitimacy
- 9:17Strengthening resolve
- 10:10Protecting against big mistakes
- 12:22Round wheels
- 13:33Incrementalism
- 15:03Stability without stagnation
- 16:29Avoiding bifurcated ecosystems
- 17:43Play the long game
related talks
30mBringing Continuous Delivery to Open Source
23mTake the Leap into Open Source Projects
52mBottom-Up Open Source Culture
27mDesign Your Open Source Project
32mOpen Source: When Nights & Weekends Are Not Enough
46mMove Slow and Try Not to Break Each Other
36mMaking it as an Indie Developer
35mTending Your Open Source Garden