Open Source at Scale
summary
React Native runs at scale: 100,000+ stars and millions of weekly downloads powering products for billions of users, so the talk focuses on concrete practices not platitudes. Use a monorepo with internal Buck vs Gradle builds and fbshipit for syncing, require CI and tests, insist on mandatory reproducers (failing tests or tiny repos), automate triage with GitHub Actions/GitHub Scripts, Danger for PR rules, and run release captains, co‑pilots, release candidates and community testers. Consider transfer to a foundation and use todo.group repo linters.
AI-written summary · about
chapters (29)
- 0:00Introduction to open source
- 1:16Legacy web stack and giants
- 2:44Open source project lifecycle
- 3:26From hackathon to production
- 4:49Open sourcing from a monorepo
- 8:00Duality of internal and open source
- 9:42Stable CI and test coverage
- 10:45People challenge in open source
- 11:26Going to market with a blog post
- 11:49Managing issues and notifications
- 13:14Issue triaging and bots
- 14:18Self-service APIs for users
- 15:43Mandatory reproducers
- 16:47Pull request management
- 17:30Automating reviews with Danger
- 18:32Connecting internal and external worlds
- 19:36Reaching project maturity
- 20:18Release roles and coordination
- 21:21Testing release candidates
- 22:23GitHub discussions for releases
- 23:07Handling migrations
- 24:10Defining support policies
- 25:33Communicating changes clearly
- 25:54Building external engagement
- 26:58Internal engagement with badges
- 28:04Graduation and project decline
- 29:51Archiving or reviving projects
- 30:57Transferring projects to foundations
- 32:21Wrap-up and call to action
