The Parallel Universes of ISPOs an...
summary
Claim: InnerSource Program Offices (ISPOs) are often necessary to make InnerSource work at scale by providing governance, tooling and advocacy rather than expecting collaboration to appear magically. Examples: a health‑tech org tracks 73 uses of a shared project to justify paid maintainer time; a media org uses a guild and a maturity model to certify projects; successful low‑friction starts include documentation as code and short developer exchanges to onboard contributors. Patterns: core teams, near‑peer mentorship, and transfer‑pricing guidance.
AI-written summary · about
chapters (13)
- 0:00Panel introduction
- 1:04Panelist backgrounds
- 2:28What is inner source
- 4:15Inner Source Program Offices
- 8:29BBC’s inner/open source
- 14:52Open versus inner source
- 27:34Business value of inner source
- 30:45Maintainer workload
- 37:44Inner source in distributed teams
- 39:30Education vs engineering
- 43:50Developer time and ROI
- 47:45Measuring success
- 49:32Closing and Q&A
related talks
50mPanel Discussion: The Parallel Universes of ISPOs and OSPOs
19mISPOs and OSPOs - differences and similarities
45mInnerSource and OSPOs: Institutionalizing Open Source Culture Change
14mMisconceptions about ways of working: How can OSPO/ISPO help?
26mOpen Source Program Offices
47mHow Should Your OSPO Work with InnerSource?
30mDemystifying OSPOs
40mThree Cs to an Open Source Program Office