From Tires to Code: Building Michelin's OSPO
summary
Michelin launches a six-person OSPO in March 2024, uses GitLab internally, an internal artifactory for SBOM and scans, and a GitHub app to track public contributions. Policy decisions: Apache 2 default license, strict prohibition of GPL/AGPL, DCO + company CLA handling IP. Outcomes so far: half a million components downloaded in 2025, about 32 active contributors with 250+ external PRs, nine public projects in 2025, 757 inner-source projects, gamified badging and an AsciiDoc training-as-code project (Eclipse Oozilk).
AI-written summary · about
chapters (14)
- 0:00Introduction to Michelin's OSPO
- 2:37Michelin's IT and open source journey
- 7:22Creating Michelin's OSPO team
- 9:29Developing open source policies
- 12:18Open source contributions and tracking
- 14:50Launching new open source projects
- 16:36Inner source strategy and adoption
- 18:01Communication and governance portal
- 19:26Open source champion program
- 21:10Training program for teams
- 22:59Funding and resource challenges
- 24:44OSPO ecosystem engagement
- 25:48Roadmap and key achievements
- 27:11Key takeaways and Q&A
related talks
19mFrom InnerSource To Open Source: Building a Dual-Focused OSPO in a Tradition...
43mPanel Discussion: The Automotive OSPO
43mThe Automotive OSPO
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance
01h 02mThe Culture of Open Source between Institutions
29mOSS Excellence: Munich's Journey towards Public Code
29mLiving with Legacy: How Bosch Built an OSPO and How You Can Do It too
45mAn OSPO for OSPOs: Managing Open Source at GitHub
