Misconceptions about ways of working: How can OSPO/ISPO help?
summary
Teams assume InnerSource means losing control, that outside patches will break builds, or that any low-usage repo makes a safe pilot; evidence shows the core team retains ownership, regressions come from missing design docs and tests, and community growth fails when maintainers lack time. OSPO/ISPOs provide checklists and workshops, enforce transparent design documentation, help implement a well-architected CI/CD pipeline, define roles and conflict paths, track ROI metrics, and require maintainers answering queries plus rewards so pilots actually gain contributors and survive.
AI-written summary · about
chapters (6)
- 0:00Introduction to talk
- 1:54Inner Source basics explained
- 3:25Benefits of Inner Source
- 5:34Top misconceptions about Inner Source
- 9:07How OSPO/ISPO can help
- 13:25Summary and conclusion
related talks
50mPanel Discussion: The Parallel Universes of ISPOs and OSPOs- 50mThe Parallel Universes of ISPOs an...
32mOSPOs: Key Lever for Open Source Sustainability
42mDoes Your OSPO Help or Hinder Contributions?
45mInnerSource and OSPOs: Institutionalizing Open Source Culture Change
30mDemystifying OSPOs
20mManaging In The Open, Managing Contributions: The challenges of OSPO developers management
26mNavigating Open Source: Establishing an OSPO for Organizational Success