InnerSource 101 and the Apache Way
summary
Claims that adopting open‑source practices inside the company cuts duplicated work, speeds reuse, and improves security and innovation; cites experience helping dozens of companies and the Inner Source Commons (PayPal sponsor) as active resources. Recommends concrete practices: open asynchronous communication (mailing lists over chat), build and test tools to allow external teams to contribute, tagging newbie issues, and preferring libraries/frameworks/messaging for inner sourcing. Warns failures come from corporate control; reports improved hiring and retention anecdotally.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:55About Me
- 2:00What is "InnerSource"
- 4:31Why InnerSource?
- 7:34What is The Apache Way
- 8:16So why focus on Apache?
- 9:39Origins of The Apache Way
- 13:30Basic Memes
- 16:13Peer-based
- 17:17Why Community - Code
- 18:30Consensus decision making
- 19:32Collaborative Development
- 19:45Responsible Oversight
- 22:03Principles of InnerSource
- 22:14Principles: Culture
- 23:13Principles: Communication
- 27:00Principles: Transparency
- 30:37Principles: Collaboration
- 35:42Principles: Meritocracy
- 37:28Final Thoughts
related talks
09mInnerSource 101
47mWhat Is InnerSource? How Do You Implement It ...
24mInnerSource Patterns for Success
30mInnersource: open source collaboration patterns beyond public FOSS projects
40mBuilding an Open Source Community from the Ground Up: 10 Lessons Learned from Inner...
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
46mOpen Source, InnerSource - Similarities, Differences, Connections
47mHow Should Your OSPO Work with InnerSource?