Why I love open source development & what I learned from K8s
summary
Kubernetes experience leads to concrete practices: treat contributions as ownership, plan succession so projects outlive individuals, and use mailing lists plus social media for durable and ephemeral communication. The project scales from tiny to huge in ~3 years, spawns many SIGs and even social groups like SIG bouldering and SIG late night, which help retention. Prioritize hiring/mentoring the people who show up, build cycles for rest to avoid burnout, and measure success by whether new maintainers appear and the tooling continues to work.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:44Share your unique perspective
- 2:46Monocultures are unhealthy
- 4:50Belonging is a team sport
- 6:25Plan your succession
- 9:22Invest in those who Show Up
- 10:18Help Others shine
- 11:49Burnout hurts everyone
- 15:42Communication
- 17:38Have fun!
related talks
34mHow to Build Collaboration and Influence Open Source Projects
25mLessons Learned from Cultivating Open Source Projects and Communities
44mBuilding On-Ramps for Non-Code Contributors in Open Source
19mWelcome to the world of Open Source Stories by Kubernetes contributor
25mLessons Learned from Cultivating Open Source Projects and Communities
05mLightning Talk: Developing Your Career While Working on Kubernetes
31mKubernetes SIG Contributor Experience: A Look Back, a Step Forward
15mLessons Learned from Cultivating Open Source Projects and Communities
