Panel Discussion: The Parallel Universes of ISPOs and OSPOs
Panelat OSPOCon @ Open Source Summit Europe 2024 · on Wednesday, 2024-09-18· at 16:05· Room 0.96-0.97 (Level 0)·
summary
Explains why organizations create an InnerSource Program Office and what it actually does: culture change, governance, tooling and discoverability, and training. Gives concrete practices that work—developer exchanges (week-long pairing), 10% time for contributions, a maturity model and a guild-led approach—and surprising metrics: one internal project shows 73 active uses, which secured dedicated maintainer time. Shares repeatable patterns (core team, documentation-as-code, near-peer mentorship), notes export‑pricing and measurement workarounds, and reports which experiments reliably scale.
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
50mThe Parallel Universes of ISPOs an...
19mISPOs and OSPOs - differences and similarities
45mInnerSource and OSPOs: Institutionalizing Open Source Culture Change
30mDemystifying OSPOs
14mMisconceptions about ways of working: How can OSPO/ISPO help?
01h 39mWorkshop: Building and Managing an Open Source Program Office
46mPanel Discussion: Lessons Learned: OSPOs in Universities
26mOpen Source Program Offices