Scaling open source communities
summary
Fastlane grows from a side project into a Google-integrated tool with ~15,000 stars, ~13,000 commits and 600+ external contributors, and the maintainer reduces open issues from ~700 to <300 using automation. Concrete practices: clear, actionable error output, searchable error-to-issue linking via G inspector, automated triage and staleness rules with the Fastlane bot (close after inactivity, then lock), and CI-assisted PR feedback using danger; plugin system yields ~160 third‑party plugins.
AI-written summary · about
chapters (24)
- 0:00Intro
- 2:46Scaling open source projects is hard
- 3:20Keeping the momentum
- 3:45Handling support
- 5:41Reviewing external PRS
- 6:13Maintainers stop being users
- 7:10Information imbalance
- 7:58How to scale open source projects
- 8:15Improve your error messages
- 10:09Use of bots
- 11:51Answers based on keywords
- 12:43Stale issues
- 14:15Lock resolved, inactive issues
- 15:33Responding to pull requests
- 17:09Steering the direction
- 17:50Scaling contribution
- 18:05Code of Conduct
- 18:15Onboarding instructions
- 18:31Keeping the code base simple
- 18:59Be welcoming and friendly
- 19:11Enabling users to extend the project
- 19:28Domain Specific Language (DSL)
- 21:01Plugins
- 21:44Final words
related talks
31mScaling Open Source Communities
23mScaling Open Source Communities
35mOpen Source at Scale
26mKeynote: "Open" as in "Welcoming": Facilitating Contributions
28mGrowing Open Source Seeds
39mManaging an Open Source Project
31mMaintaining a big open source project: lessons learned
23mKeep cool and maintain an open source project