Metal3.io’s Path To CNCF Incubation: Governance, Processes, and Community
summary
Metal3 moves from code-first to verifiable project hygiene: it centralizes governance into a community repo, defines OWNER files across multiple repos, creates a dedicated security team with a security self-assessment and security insights file, and automates releases into a predictable automated release cadence. The project documents adopters (Red Hat, Ericsson among others), maintains public meeting notes and CI-tested quickstart instructions, and spends six years (2019→2025) preparing before CNCF incubation with only minor TOC findings.
AI-written summary · about
chapters (15)
- 0:00Metal3.io’s CNCF journey
- 1:26Project growth challenges
- 5:18Early history and code
- 7:45Governance bottleneck
- 10:35Sandbox to incubation
- 12:21Centralizing governance
- 15:10Transparent community
- 16:58Engineering for incubation
- 18:02Security governance
- 19:49Ecosystem adoption
- 21:58Incubation evaluation
- 23:03CNCF review process
- 25:32Key learnings and practical checklist
- 29:02Why incubation matters
- 29:44Q&A on TOC
related talks
06mFinally Incubated! What Comes Next For Metal3?
38mMaintainers, Project Services and CNCF
40mRooted in Open Source: How CNCF Projects Mature and Scale
18mThe CNCF & You - Growing Community in the CloudNative Landscape
13mCNCF Project Paperwork Working Session
17mHow CNCF is Enabling End User Driven Open Source
19mAnt Group’s Open Source Incubator: Aligning With CNCF Maturity Framework
19mIntro: CNCF CI