Scaling Internal Collaboration with Open Source Operating Models
summary
Argues that applying open source operating models and OSPO practices fixes duplicated work (example: similar integrations across 27 offices), slow reviews (one PR waited seven days), and undocumented services by enforcing onboarding guides, code ownership graphs, decision records, and automated PR checks. Recommends using metadata platforms like Backstage, measuring developer experience with onboarding time, review turnaround, cross-team contributions and reuse rates, and running lightweight governance so projects don’t become single-maintainer bottlenecks.
AI-written summary · about
chapters (10)
- 0:00Introduction to talk
- 1:11Common collaboration challenges
- 6:31Unstructured inner source problems
- 7:39Open source solutions for collaboration
- 8:23Designing contribution guidelines
- 12:14Governance for maintainers
- 15:05Scaling with open source principles
- 16:50Inner source maturity levels
- 18:14Measuring impact of inner source
- 19:40Key takeaways and next steps
related talks
26mNavigating Open Source: Establishing an OSPO for Organizational Success
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance
43mFostering an Open Source Culture
25mOpen Source Corporate Sustainability – Models to Consider
28mSustainability beyond funds: Extrospective OSPOs
24mBuilding a Foundation for Open Collaboration
52mBottom-Up Open Source Culture
22mThe OSPO Playbook: Supercharging Open Source at Scale
