An OSPO for OSPOs: Managing Open Source at GitHub
summary
GitHub runs an internal OSPO that inventories hundreds of orgs and repos, builds a service catalog and a beta OSPO dashboard that flags missing licenses, code of conduct and falling activity, and counts about 45,000 distinct OSS components used. License work relies on the clearly defined dataset plus an open Go library gospdx; initial scans produce ~1,000 issues, ~350 repo fixes after data cleanup, and zero cases that required code rewrites, per the reported results.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:38Open Source at GitHub
- 1:40Our Mission
- 2:26Outdated stereotype
- 3:28Open source is free
- 4:04We dont inherently do everything right
- 4:27We have a strong open source program
- 6:07A balanced intellectual property employment agreement
- 7:26GitHubs involvement in upstream projects
- 8:03Independent open source projects
- 8:19Foundationled open source
- 9:43More open source equals better
- 12:02GitHub Roadmap
- 13:25GitHub OSPO
- 13:44GitHub mission
- 14:14GitHub programs
- 17:18Get clean workflow
- 18:44Open source components
- 20:13Lessons learned
- 23:09Durability
- 24:20Lesson Learned
- 26:33Open Source Release Process
- 29:56Are the issues resolved
- 32:09GitHub sponsorships
- 33:38Discussions
- 34:58Metric Staff Word
- 36:48GitHub Dash
- 38:42Dashboard Beta
related talks
46mOSS Management & OSPO Ask Anything
37mOSPO is a Key Element for your Company, but also for the OS Ecosystem
26mNavigating Open Source: Establishing an OSPO for Organizational Success
32mOSPOs: Key Lever for Open Source Sustainability
26mOpen Source Program Offices
15mHow to set up an Open Source Program Office? Get insights and use cases from the OSPO Alliance
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance
25mThe State of OSPOs and OSS Management 2025 Research Findings by TODO Group