A Frictionless Inner Source Journey
summary
Company standardizes on GitHub and GitLab, runs an InnerSource discovery portal now on GitHub Enterprise Cloud, and measures contribution health by counting repos, license adoption and external contributions — finding one project with 48 issues from 34 users and ~50 pull requests. A survey maps the entire contribution journey, reveals scattered docs, burdensome compliance and slow feedback, and leads to concrete fixes: a license-bot that opens a PR, streamlined workflow, centralized knowledge hub, and a non‑monetary contributor reward program under worker‑council review.
AI-written summary · about
chapters (11)
- 0:00Introduction to Inner Source
- 1:13Mercedes-Benz Inner Source Setup
- 3:38Inner Source Success Story
- 5:01Why Inner Source Works
- 6:24Inner Source Challenges
- 9:13Developer Pain Points
- 11:58Identifying Frictions
- 15:27Actionable Initiatives
- 18:17Simplifying Processes
- 21:06Summary and Next Steps
- 22:10Q&A Session
related talks
18m(Y)Our Journey to Inner Source
19mThree points that promoted InnerSource activities
30mInnersource: open source collaboration patterns beyond public FOSS projects
19mA Frictionless Inner Source Journey
25mDriving the InnerSource Program at SAP
36mInnerSource at Scale: A Platform-centric Approach
28mA Journey to Inner Source
25mLooking at the Future of InnerSource
