Navigating Open Source: Establishing an OSPO for Organizational Success
summary
Centralized OSPO responsibility covers license compliance, policy, governance and developer education, with a cloud-scale case handling 20,000 developers across ~120,000 employees; operations use Jira and Git and favor self‑service tooling and repeatable workflows. The office acts as a one‑stop for legal, engineering and devrel, runs like an open source project (BDFL, committers, contributors), enforces peer review “two thumbs up” approvals, and focuses on risk mitigation, SBOM/CRA readiness and community engagement.
AI-written summary · about
chapters (11)
- 0:00Open source program offices
- 1:02OSPO purpose
- 3:13OSPO responsibilities
- 4:58OSPO benefits
- 7:28OSPO establishment
- 10:20OSPO evolution
- 11:06Intel’s OSPO structure
- 15:20Intel’s OSPO components
- 16:44Recommendations for companies of any size
- 18:11Q&A: Proprietary tools
- 21:48Q&A: OSPO future
related talks
26mOpen Source Program Offices
40mThree Cs to an Open Source Program Office
01h 39mWorkshop: Building and Managing an Open Source Program Office- 01h 39mWorkshop: Building and Managing an Open Source Program Office
15mHow to set up an Open Source Program Office? Get insights and use cases from the OSPO Alliance
26mLooking at Open Source Security from the Community Angle
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance
46mOSS Management & OSPO Ask Anything