OSS Excellence: Munich's Journey towards Public Code
summary
Munich declares in 2021 that in‑house code follows public money public code and builds an OSPO inside its 1,200‑person IT department (about 30 devs in the competent engineering unit). They standardize on Postgres, run internal GitLab and publish on GitHub, move ~2,500 services and 2,000 interfaces toward an open modern stack, offer a six‑month paid open‑source sabbatical and small sponsorships, and clear a yearlong legal review to allow permissive licensing — uptake is positive with low resistance.
AI-written summary · about
chapters (5)
- 0:00Introduction to Munich's public code journey
- 3:59Munich's open source evolution
- 10:28Forcing mainstreaming open source
- 13:30Key success factors for publishing code
- 24:47Q&A session
related talks
40mCooperation and Inclusion through Open Source
22mThe OSPO Playbook: Supercharging Open Source at Scale
26mNavigating Open Source: Establishing an OSPO for Organizational Success
28mBuilding Open Source Culture in an Enterprise: The Infosys OSPO Story
01h 02mThe Culture of Open Source between Institutions
29mFrom Tires to Code: Building Michelin's OSPO
19mFrom InnerSource To Open Source: Building a Dual-Focused OSPO in a Tradition...
55mWhat TO-DO in Europe: Welcome & Opening...