Top 5 Myths of InnerSource
summary
InnerSource uses pull requests, discoverable repos and clear READMEs to scale internal collaboration; data from Microsoft shows 90% of pull requests come from the owning team, 9% from nearby teams and 1% from elsewhere. Proven builds include the Xbox adaptive controller and Visual Studio Code whose Monaco editor started as a shared component. Expect most users to be consumers, a small fraction to file issues and an even smaller fraction to submit code; success needs documentation, good-first-issue tags and incentive changes, not stickers.
AI-written summary · about
chapters (7)
- 0:00What is InnerSource?
- 6:27Myth 5: Free work
- 14:14Myth 4: Stickers motivate sharing
- 19:10Myth 3: Code must be perfect
- 21:57Myth 2: Framework teams
- 25:25Myth 1: Won’t work here
- 28:00Closing and resources
related talks
36mInnerSource at Scale: A Platform-centric Approach
24mInnerSource Patterns for Success
25mLooking at the Future of InnerSource
30mInnersource: open source collaboration patterns beyond public FOSS projects
25mDriving the InnerSource Program at SAP
09mInnerSource 101
28mInner Source
36mUnderstanding the Benefits of InnerSource in the European Industry