InnerSource Contribution Insights
summary
Companies extract commit and repo metadata from Git/GitHub and join it to Azure AD and ERP records to map author → department → legal entity; Bosch notes 400,000 employees and 400 legal entities. Heuristics include privilege/team membership, calculating org-structure distance from core committers, and building a heat map per repository. Practical limits: monorepos and stale team configs break rules, statistics remain probabilistic. A working dashboard stores historized counts, shows growth after events, and treats repositories with 5+ legal entities threshold as likely successful InnerSource.
AI-written summary · about
chapters (6)
- 0:00Introduction and speakers
- 1:31InnerSource similarities and differences
- 6:08Data sources and contributor insights
- 10:04Measuring InnerSource activity
- 12:51Success metrics and silo breakdown
- 14:16Q&A
related talks
18m(Y)Our Journey to Inner Source
28mA Frictionless Inner Source Journey
25mDriving the InnerSource Program at SAP
30mInnersource: open source collaboration patterns beyond public FOSS projects
28mA Journey to Inner Source
17mEnabling Data Mesh in Large Organizations with InnerSource
48mInnerSource Metrics for Changing Engineering Culture and Driving Open-Source...
27mIs InnerSource Commons good for open source?