Scaling Open Source Communities
summary
A first-hand case study of scaling fastlane from a side project to 13,000 stars and 500+ external contributors, with concrete tactics: improve error messages, surface StackOverflow links and reproducible commands, and show similar issues via the inspector gem; automate triage and staleness with bots and issue templates, use danger to comment failing CI on PRs, offer plugins (120 third‑party plugins) and a DSL, and reduce open tickets from ~700 to under 300.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:09Scaling open source communities
- 3:02Scaling open source projects is hard
- 3:40Keeping the momentum
- 4:03Handling support
- 6:27Maintainers stop being users
- 7:19Information imbalance
- 8:08How to scale open source projects
- 14:19Lock resolved, inactive issues
- 15:42Responding to pull requests
- 17:13Steering the direction
- 17:54Code of Conduct
- 18:05Onboarding instructions
related talks
31mScaling Open Source Communities
23mScaling open source communities
39mMaintaining a big open source project: lessons learned
29mThe Open Source Development Surprise
31mMaintaining a big open source project: lessons learned
40mTightrope Walking: Best Practices & Lessons Learned on Community and Business Buildi...
40mPanel Discussion: Build a Community, Not a Framework
35mOpen Source at Scale