Open Source Program Offices
summary
Companies describe standing up OSPOs to centralize license compliance, run inner-source pilots before public release, and manage long‑term relationships with upstream projects; one organization recently open‑sourced kernel modules after a multi‑year effort, another treats the OSPO like an open project that must get internal contributions, and retailers use OSPOs to drive code sustainability. Early wins focus on legal tooling and a concierge model that proves value so the program can scale organically.
AI-written summary · about
chapters (8)
- 0:00Open Source Program Offices intro
- 1:45Why companies start OSPOs
- 6:18Open source in company strategy
- 10:31Inner sourcing basics
- 15:47OSPO maintenance challenges
- 21:09Starting an OSPO advice
- 24:21Sustainability via open source
- 25:01Closing remarks
related talks
40mThree Cs to an Open Source Program Office
26mNavigating Open Source: Establishing an OSPO for Organizational Success
30mDemystifying OSPOs
32mOSPOs: Key Lever for Open Source Sustainability
36mThe Evolution of OSPOs
15mHow to set up an Open Source Program Office? Get insights and use cases from the OSPO Alliance
01h 39mWorkshop: Building and Managing an Open Source Program Office
39mOSPOs in Energy, Transport, Automotive & Public Sector