Scaling teams with technology
summary
Kubernetes growth starts with 600 contributors in 2016 and about 50% of contributions coming from the core team, then the core team tripled in size while velocity falls; adoption of engineering hygiene — release cadence, working groups, governance, clearer communication — plus building a dozen extension mechanisms (cloud providers, client libraries, Container Runtime Interface, etc.) creates independent teams and restores velocity for Kubernetes, Istio, GKE and Anthos.
AI-written summary · about
related talks
23mHow Kubernetes Works: Community, Velocity and Contribution
22mThe Kubernetes Community
17mKeynote: Backstage with Kubernetes
20mKeynote: Kubernetes Community
36mThe Elephant in the Kubernetes Room: Team Interactions at Scale
16mWhy Community Matters
22mKeynote: Backstage with Kubernetes
24mKeynote: A Decade of Kubernetes: Community-Driven Evolution