OSPO is a Key Element for your Company, but also for the OS Ecosystem
summary
Claims that an OSPO centralizes license and security checks, coordinates inbound/outbound/releasing flows, and turns consumption into strategic contribution — Samsung contributes upstream so hardware ships with support. Practical tools named: CHAOSS metrics, OpenChain, and TODO Group guidance; Tidylift/OpenCollective are funding paths. Empirical points: about 1000 developers per 1 OSPO is a reported staffing ratio, GitHub analysis shows ~200 weekly “users” vs ~50 contributors for large JS frameworks, and sudden user spikes (Jitsi) cause maintainer burnout.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:17Open Source is eating the Software World
- 2:22Corporations & Open Source
- 10:49How to manage an OSPO?
- 17:01Unbalanced world
- 20:29GOAL: OSS ecosystem sustainability Users
- 23:07Multiple Options Business
- 27:35Final remarks An OSPO manages the complex and diverse relationship between your organization and its open source software (OSS) ecosystem
- 30:58Let's go for questions
related talks
32mOSPOs: Key Lever for Open Source Sustainability
39mOSPOs in Energy, Transport, Automotive & Public Sector
46mOSPOs: Key Lever for Open Source Sustainability
26mLooking at Open Source Security from the Community Angle
26mOpen Source Program Offices
46mOSS Management & OSPO Ask Anything
50mSo What is Next for OSPOs in 2023 and Beyond?
30mDemystifying OSPOs