Rooted in Open Source: How CNCF Projects Mature and Scale
summary
Describes how projects move from Sandbox to Graduation using a real example, Alpaca, with concrete requirements: Apache 2 license, transfer of trademark and domain to CNCF, GitHub two‑factor and vendor‑neutral metadata, TOC review cycles (meets every two months), adopter interviews (typically 2–7), at least one year in Incubation, and a mandatory third‑party security review before Graduation. Covers tooling and support (GitHub Actions CI, CNCF marketing, docs, Zoom), governance checklists, contributor ladders, and common pitfalls like incompatible licenses.
AI-written summary · about
chapters (19)
- 0:00Introduction and thanks
- 1:14Is my project right for CNCF
- 3:02Benefits of joining CNCF
- 5:10CNCF maturity levels explained
- 5:31Requirements for sandbox projects
- 8:18Sandbox project best practices
- 10:44Security requirements for CNCF
- 12:06Applying to CNCF sandbox
- 13:32Life as a sandbox project
- 17:26Moving from sandbox to incubation
- 19:58Incubation requirements and process
- 21:44Governance and contributor growth
- 25:18Security and compliance for incubation
- 26:46Life as an incubating project
- 28:31Preparing for graduation
- 30:16Graduation requirements and review
- 31:42Life as a graduated project
- 34:51Sustaining project maturity
- 35:32Q&A session
related talks
18mThe CNCF & You - Growing Community in the CloudNative Landscape
38mMaintainers, Project Services and CNCF
35mGood Governance Practices for CNCF Projects
19mAnt Group’s Open Source Incubator: Aligning With CNCF Maturity Framework
36mNavigating the CNCF Landscape: One Piece at a Time
35mKeynote Session:The Graduated Projects Panel
23mOne-on-One Discussion
17mHow CNCF is Enabling End User Driven Open Source