How can we truly arrive at "open-source everywhere"?
summary
Claim: only about 20% contribute to open source and inner source trains the other 80% to share. Companies set up an Inner Source Commons, open-source their tooling and a purple handbook, and large adopters like Bosch report multi-year, multi-million dollar programs. PayPal implements code transparency on GitLab/GitHub, a trusted committer model, explicit contributing.md rules, and extrinsic rewards by retooling a fellow program. Early metrics show measurable velocity gains and reusable documentation, and the approach scales unevenly but practically across cultures.
AI-written summary · about
chapters (12)
- 0:00Introduction to open source everywhere
- 1:06What is inner source
- 2:33Inner source at companies like Bosch
- 3:58Challenges of inner source adoption
- 5:03Code transparency and trusted committers
- 6:29Host versus guest model
- 7:32Documentation and velocity increase
- 8:13Extrinsic rewards for contributors
- 9:16Including product owners in inner source
- 9:57Agile and inner source compatibility
- 10:40Inner source Commons community
- 11:43Future of inner source and open source
related talks
52mBottom-Up Open Source Culture
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
30mInnersource: open source collaboration patterns beyond public FOSS projects
43mFostering an Open Source Culture
45mInnerSource and OSPOs: Institutionalizing Open Source Culture Change
27mOpen Source: Supporting, Contributing and Evangelising
54mInnerSource 101 and the Apache Way
30mMaximizing Open Source Investment to Drive Business Innovation