A Journey to Inner Source
summary
Seven-year Inner Source rollout at Mercedes-Benz focuses on three hard problems: tooling consolidation (pick one or two platforms, not 20; evaluated GitHub vs GitLab), legal & tax fixes (a multi-page Inner Source license plus a tax self‑assessment using the arm’s‑length idea), and culture/governance (contribution guidelines, community management). A notable success is I3: 100+ contributions and 1,200 Mattermost members in year one. SAP’s Inner Source Discovery portal is adopted as a finder tool.
AI-written summary · about
chapters (8)
- 0:00Introduction to Inner Source
- 6:48Inner Source vs Closed Source
- 7:08Tooling for Inner Source
- 9:38Legal Challenges in Inner Source
- 16:01Cultural Change in Inner Source
- 19:17Success and Challenges of Inner Source
- 23:54Key Takeaways for Inner Source
- 24:41Q&A on Inner Source
related talks
18m(Y)Our Journey to Inner Source
25mDriving the InnerSource Program at SAP
14mBootstrapping InnerSource at Airbus
27mInnerSource Community Journey Across Diverse Domains
36mUnderstanding the Benefits of InnerSource in the European Industry
16mHow SAP runs and documents its InnerSource program
24mInnerSource Patterns for Success
16mOvercoming InnerSource Challenges: 3 pitfalls and 2 key success criteria