The O[S]PO Organization for the Age of AI
summary
Argues that existing OSPOs should become OPOs to cover software, models, weights and data, citing HPE’s decision to place the team in legal for IP alignment and to extend governance to open models, open data and open hardware. Notes practical signals: Hugging Face replaces GitHub for models with millions of assets and over 40 active court cases about training data and weights, and operational metrics they use are track GitHub contributions and Jira response time. Describes a champions program with compliance, inner‑source and AI reps.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 3:32Evolution of Open-Source Program Offices
- 15:58AI impact on open source
- 25:01OSPO as AI driver
- 27:51Q&A
related talks
19mOSP0s and Open Technology - Nithya Ruff, Amazon
43mBoF: Open Source & AI: Where OSPOs Make It Work
44mTowards Industrial AI Governance Inspired by OSPO: A Primer
15mKeynote: What Agentic AI Asks of Open Source Strategy: A New Layer for OSPOs
30mDemystifying OSPOs
37mOSPO is a Key Element for your Company, but also for the OS Ecosystem
16mBuilding an AI Fit OSPO
26mOpen Source Program Offices