InnerSource and OSPOs: Institutionalizing Open Source Culture Change
summary
Many OSPOs embed InnerSource as a stepping stone to external open source, reporting over 40% have formal InnerSource programs and another ~20% planning one; common moves include running projects on GitHub pull requests with CI, explicit governance models and mentoring flows. Examples show it works: a police force shares a micro-architecture for camera/plate/license scanning so teams swap detection modules without exposing UIs. Outcome: developer education, fewer silo blockers, and measurable lifts in teams ready to publish or maintain public projects.
AI-written summary · about
chapters (8)
- 0:00Welcome and introductions
- 3:21Why InnerSource as a step
- 10:20InnerSource and OSPO roles
- 18:35OSPO functions in InnerSource
- 25:40Diversity in InnerSource culture
- 31:14Closing and resources
- 32:35Tim Willoughby on policing InnerSource
- 38:18Q&A session
related talks
47mHow Should Your OSPO Work with InnerSource?
30mInnersource: open source collaboration patterns beyond public FOSS projects
19mFrom InnerSource To Open Source: Building a Dual-Focused OSPO in a Tradition...
50mPanel Discussion: The Parallel Universes of ISPOs and OSPOs
54mInnerSource 101 and the Apache Way
26mOpen Source Program Offices
47mWhat Is InnerSource? How Do You Implement It ...
52mBottom-Up Open Source Culture