OSPOs in Energy, Transport, Automotive & Public Sector
summary
Panelists map concrete OSPO work: centralize a single point of contact, enforce license and security compliance, and enable upstream contribution while scaling inner source across business units. Examples include hosting projects under the Linux Foundation, planning contributions to the Eclipse Foundation and staffing with three full-time roles to split legal, technical and governance work. Hard numbers surface: toolchains touch roughly 100,000 projects, CLAs and the CRA create bottlenecks, and success needs sponsor buy‑in, budget and clear, incremental priorities.
AI-written summary · about
chapters (9)
- 0:00Introduction and panel setup
- 1:04Why OSPOs were formed
- 4:56OSPO roles and responsibilities
- 9:35Inner Source challenges
- 17:47Key challenges in OSPOs
- 26:15Advice for starting an OSPO
- 30:33Government open source strategies
- 34:10Open source foundations and trust
- 37:03Community management in OSPOs
related talks
37mOSPO is a Key Element for your Company, but also for the OS Ecosystem
32mOSPOs: Key Lever for Open Source Sustainability
26mOpen Source Program Offices
30mBuilding OSPOs in Practice...
40mTODO Steering Committee - Management & OSPO Ask Anything
36mOSPO Issues in a Conglomerate Company
40mThree Cs to an Open Source Program Office
42mDoes Your OSPO Help or Hinder Contributions?