From central hosting team to code maintainers
summary
A central DevOps team rewrites a Netherlands-only Cloud framework into a global, maintainable platform of a core layer and landing zones that any Ahold Delhaize brand can deploy, scaling to hundreds or thousands of zones. Collaboration uses an inner source model (horizontal SIGs, vertical SIGs, steering committee) with a benevolent‑dictator approval rule: at least two original maintainers sign off on GitHub pull requests. Success is measured by scraping PR data—global contributions rise within months—but governance, fast approvals and meeting facilitation prove critical.
AI-written summary · about
chapters (9)
- 0:00Inner sourcing at Overtime
- 1:07Overtime's cloud framework
- 5:46Global code collaboration struggles
- 8:13Inner source model structure
- 13:31Three components working together
- 15:57Inner sourcing advantages
- 17:43Success metrics with GitHub
- 18:50Lessons learned and best practices
- 20:58Wider adoption and next steps
related talks
36mWhale Care 101 - How We Organize A 200+ Devs Project
43mDevOps@bol.com a great journey towards autonomy
30mDevOps: Supporting aircraft from hanger to take-off
29mLiving with Legacy: How Bosch Built an OSPO and How You Can Do It too
28mOpen Source at Scale Building Operation in a large company
10mDevOpsCon 2016: Interview Marko Berkovic & Matthias Wiesen
25mHow to Grow & Mentor an Open Source Community & Achieve Collaboration with Over 170 Listed Corpor...
29mIaC Next Steps in Platform Engineering