Has Open Source outgrown the OSPO?
summary
Claim: the OSPO definition from Sun 1999 still dominates even though open source becomes core to IT and 97% of companies use OSS, so much that legal, security and engineering teams now own compliance and supply‑chain work with vendor tooling and OpenSSF guidance. Evidence: OSPO roles shrink — layoffs hit open source teams and OSPOs vanish from job listings — while platform engineering and automated scanners absorb many OSPO tasks. Built outcomes include a sustainable open source company later sold and multiple internal OSPOs created then retired.
AI-written summary · about
chapters (14)
- 0:00Introduction to OSPO history
- 1:26Open source’s 25-year static definition
- 3:18Open source’s business critical success
- 5:24OSPO’s role in stakeholder alignment
- 8:13Victory doesn’t equal job security
- 9:16OSPO value unchanged since 1998
- 10:00World changed but OSPOs didn’t
- 12:53Platform engineering shifts autonomy
- 15:42Inner source struggles with microservices
- 17:28OSPOs made themselves obsolete
- 18:55Future of OSPOs and novel value
- 21:46Open source outgrew the OSPO
- 26:05Q&A on OSPO tools and critiques
- 28:12Sustainability and funding of open source
related talks
15mFrom Code to Market: Strategic Business Models and OSPO Implementation
46mOSS Management & OSPO Ask Anything
26mOpen Source Program Offices
25mThe State of OSPOs and OSS Management 2025 Research Findings by TODO Group
30mDemystifying OSPOs
36mThe Evolution of OSPOs
36mWhy OSPOs are Important To A Company's Innovation Strategy?
37mOSPO is a Key Element for your Company, but also for the OS Ecosystem