SIG Contributor Experience Deep Dive
summary
Kubernetes SIG Contributor Experience is building a developer guide to replace a scattered develop/ directory with many files untouched for 4+ months, proposing versioned docs in GitHub (use GitBook) and keeping docs next to code so they don’t rot. KEPs (design proposals) become a lifecycle hook to require architecture and docs. The group prototypes simple, runnable examples — a vagrant README was merged into the kubeadm repo — and emphasizes dev build/test recipes, the shared informers change, and a quarterly release cadence to keep docs current.
AI-written summary · about
chapters (20)
- 0:00SIG Contributor Experience intro
- 1:03Team intro and interactive format
- 2:28Developer guide problem statement
- 4:59Kubernetes growth and docs needs
- 7:28Developer guide overview
- 9:11GitBook for versioned docs
- 11:59Wiki challenges and docs maintenance
- 14:04Quarterly docs cadence
- 15:29Docs to code linking and automation
- 17:11Cultural change for docs ownership
- 19:41Technical review and knowledge gaps
- 21:50Architecture principles and SIG role
- 23:37Delegating docs to SIGs
- 25:23Newcomer dev environment missing
- 26:30Example dev experience improvements
- 28:01Contributor feedback and surveys
- 29:24Docs search analytics tracking
- 30:15Target users and guide scope
- 31:39Dev build test cycle impact
- 32:43Next steps and community involvement
related talks
31mKubernetes SIG Contributor Experience: A Look Back, a Step Forward
30mIntro: Kubernetes Contributor Experience SIG
34mSIG Contributor Experience Deep Dive
29mInside Kubernetes SIG Contributor Experienc...
39mDeep Dive: Contributor Experience SIG
24mSIG Contributor Experience Deep Dive
29mHow You Can Tell Your Kubernetes Contribu...
33mMeet the Gears Behind Kubernetes APIs: Introduction to SIG API-Machinery