Innersource: open source collaboration patterns beyond public FOSS projects
summary
Europace reports a two‑year InnerSource pilot inside a 170‑person company (Hypoport ~1.5k) that moves code and docs onto GitHub/GitHub Enterprise, runs small business‑impact experiments, and forms a monthly tribe. Key practices are open transparent findable repositories, preferring written over verbal decisions to build a searchable project memory, automating CI/style checks so maintainers scale, and promoting volunteers via a trusted committer role (private invite, then public announcement). Anecdote: ~50% of PRs get rejected unless contribution norms exist.
AI-written summary · about
chapters (14)
- 0:00Introduction to InnerSource
- 2:21Company Context and Pain Points
- 5:25Why Adopt InnerSource
- 6:46Key Principles of Openness
- 9:06Documentation and Guidelines
- 10:48Asynchronous Communication
- 12:03Creating Project Memory
- 13:36Fostering a Learning Culture
- 15:29Rewarding Contributions
- 17:08The Trusted Committer Role
- 17:56Getting Started with the Commons
- 19:46Implementing Experiments
- 21:10Summary and Key Takeaways
- 23:14Q&A and Conclusion
related talks
24mInnerSource Patterns for Success
19mThree points that promoted InnerSource activities
36mInnerSource at Scale: A Platform-centric Approach
45mInnerSource and OSPOs: Institutionalizing Open Source Culture Change
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
52mBottom-Up Open Source Culture
13mHow can we truly arrive at "open-source everywhere"?
26mWhy innersource is a critical component of FOSS sustainability