Good Governance Practices for CNCF Projects
summary
CNCF provides ready-to-use templates (maintainer, contributor ladder, reviewing, subprojects) and expects projects to document roles, processes and security (security.md, Dependabot) so communities scale. Graduation requires governance.md required for graduation and a committer process with at least two organizations as committers. Contributing a project to CNCF increases cross‑company leadership and adoption (Kubernetes cited) but demands ongoing staff time and often more work than keeping the project internal.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:50About Dawn
- 1:58What is governance
- 2:52Early governance
- 6:20Resources
- 6:40Requirements
- 7:57Governance Templates
- 9:47Maintainer Resources
- 10:40Setting Expectations
- 11:24Mission Statement
- 12:10Project Scope
- 14:03Governance
- 15:39Security
- 16:44Leadership
- 20:53Ownership and Control
- 21:14Governance Documentation
- 22:22Contributing to the CNCF
- 24:32Governance is never finished
- 25:09Resources for governance
- 27:06The Big Picture
- 27:50Thank You
- 28:00Questions
related talks
18mThe CNCF & You - Growing Community in the CloudNative Landscape
40mRooted in Open Source: How CNCF Projects Mature and Scale
10mTossing Our Caps: gRPC Governance Changes and the Path To CNCF Graduation
38mFrom Data To Action: Resources for Building Sustainable Graduated Projects
13mCNCF Project Paperwork Working Session
23mGood Governance Practices for Healthy Open Source Projects
17mHow CNCF is Enabling End User Driven Open Source
14mKeynote: How You Can Create a CNCF Project