A Vision of FOSS @Mercedes-Benz
summary
Mercedes‑Benz adopts a six‑year plan: creates an OSPO with FOSS coordinators, publishes the Mercedes‑Benz FOSS Manifesto (CC0, on GitHub) to allow company‑time contributions, and runs role‑specific trainings for use, contribution and inner‑source. Memberships include Eclipse Foundation (Software Defined Vehicle WG), Linux Foundation and CNCF; GitHub Sponsors funds maintainers. Cites studies: 2,400 codebases show ~97% include OSS (78% of code), and contributing companies realize roughly twice the monetary benefit of only using OSS.
AI-written summary · about
chapters (10)
- 0:00Introduction and the 2016 inner source struggle
- 3:15Turning inner source into a success story
- 5:22Creating an internal open source program office
- 10:39Establishing FOSS coordinators and community
- 16:20Why Mercedes-Benz embraced FOSS in its strategy
- 20:19The Mercedes-Benz FOSS Manifesto and cultural change
- 25:37Training employees on FOSS processes and rules
- 27:04Joining foundations and sponsoring open source projects
- 31:41Answering questions on organizational collaboration
- 34:52Success stories and closing remarks
related talks
31mA Vision of FOSS @MercedesBenz
37mA FOSS Manifesto to Drive Open Source
26mThe Mercedes-Benz FOSS Manifesto – Our Commitment to be Truly Open
14mThe FOSS Manifesto at Daimler TSS
41mInvest In The Software That Powers Your World
31mDrive Your Business With Open Source Sponsorship
38mDrive Your Business With Open Source Sponsorship
29mLiving with Legacy: How Bosch Built an OSPO and How You Can Do It too