Your Guide To How CNCF Projects Actually Do Documentation
summary
Panel documents how CNCF projects run docs: one-person bootstraps or small teams form around a shared charter, mentorship fills gaps via LFX mentorship, and corralling work relies on a rotating PR wrangler to keep around 150 open PRs manageable. A custom Go tool by Javier Romeo executes console blocks so CLI examples stay correct (docs-as-tests), linting like Vale can kill contributions, and AI (Kappa AI, ChatGPT) changes onramp etiquette and forces new guidance on acceptable AI use.
AI-written summary · about
chapters (7)
- 0:00CNCF docs projects intro
- 2:23Building a docs team
- 6:18Docs mentorship programs
- 15:55Good first issues
- 21:18AI’s impact on docs
- 26:54AI changes docs needs
- 31:35Closing remarks & Q&A
related talks
39mThe Documentation Dream: One Team, No Silos, Shared Goal
01h 15mFrom Code to Docs to Marketing: How to Contribute
32mBridge the Gap To OSS Adoption With Documentation: A Kubernetes Story
44mPushing documentation (so it doesn't hurt anymore)
23mDocs, Demos, and Mentors: Growing Open Source
12mKeynote: Welcome + Opening Remarks
04mLightning Talk: Want to Donate a Project to the CNCF? Here's How
26mLaunching Your Cloud-Native...