Can you measure InnerSource?
summary
Three concrete measurements let organizations quantify InnerSource: cross-team participation (map contributors to teams and compute the inner source ratio — percent of work by external teams), contribution volume (commits, pull requests, issues broken down by contributor), and cross-repository impact (which repos attract shared work and reduce duplication). The open source tool Measure Innersource (github.com/githubmeasure-inource) uses an org data.json to generate Markdown/JSON reports; beware pitfalls like gitis, vanity metrics, and the measurement death spiral.
AI-written summary · about
chapters (8)
- 0:00Introduction to measuring InnerSource
- 1:09Why measuring InnerSource is hard
- 3:37Three core challenges in measurement
- 9:20What’s at stake without measurement
- 11:28Solution framework for measurement
- 16:46Common measurement pitfalls
- 19:18Tool walkthrough and implementation
- 21:24Call to action and summary
related talks
48mInnerSource Metrics for Changing Engineering Culture and Driving Open-Source...
14mLeveraging scorecards to scale InnerSource
25mDriving the InnerSource Program at SAP
28mA Frictionless Inner Source Journey
30mInnersource: open source collaboration patterns beyond public FOSS projects
19mWhen there is no alternative to InnerSource
14mAdopting InnerSource to maximize Developer Experience
27mIs InnerSource Commons good for open source?