InnerSource at Scale: A Platform-centric Approach
summary
Argues that scaling InnerSource works by opening the internal platform (GitHub/git-based repos), appointing a trusted committer team, and running a governance board/CoE plus pilot projects and incentives. Gives concrete tooling: GitHub plus an internal InnerSource portal, CI checks, and contributor lists. Cites org scale (75,000 tech staff, 15,000 platform engineers), production pain at 200,000 RPS, and survey data (22% run InnerSource ≥5 years). Reports outcomes: external contributors submit PRs (example 200 PRs tracked), some contributors are merged into the platform team.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:03Developer challenges
- 5:18What is InnerSource
- 7:24Traditional vs InnerSource
- 13:40InnerSource adoption
- 16:51Scaling InnerSource
- 19:38Platform engineering for InnerSource
- 25:31InnerSource benefits
- 27:34Closing thoughts
- 28:37Q&A: Tools
- 32:49Q&A: Compliance
related talks
30mInnersource: open source collaboration patterns beyond public FOSS projects
24mInnerSource Patterns for Success
25mLooking at the Future of InnerSource
09mInnerSource 101
25mDriving the InnerSource Program at SAP
28mBreaking Silos With InnerSource
27mInnerSource at scale Let's innovate together!
52mBottom-Up Open Source Culture
