Posted on August 17, 2026 by CNCF Technical Oversight Committee Clear patterns have emerged from governance reviews across 72 CNCF projects, distinguishing between what the CNCF requires at each maturity level versus what the data recommends for long-term project health. This post captures those patterns as guidance for projects choosing or evolving their governance structure. Governance reviews across 72 graduated, incubating and archived projects show: The CNCF project template repository provides three governance templates.
Each maps to a project archetype: Best for: Focused, single-repo or tightly-scoped projects with a small, cohesive group of contributors. A self-selecting council of maintainers makes all project decisions. There is no distinction between the people who write the code and the people who govern the project. Decisions are made by lazy consensus (no objections within a defined timeframe means approval) among maintainers, with formal votes reserved for disagreements or governance changes.
When it works well: - The project has a clear, bounded scope - 3-10 active maintainers who regularly collaborate - Most contributors know each other and communicate directly - Most decisions are uncontroversial and made by consensus Key elements: - MAINTAINERS file with names, affiliations, and domains of responsibility - Documented process for adding and removing maintainers (including inactivity) - Emeritus status for maintainers who step back - Lazy consensus as the default, with defined voting thresholds for governance changes - Security response team (can be the same as the maintainer group for small projects) When to evolve this model: If a single organization comes to dominate the maintainer list through hiring, acquisition, or attrition of external contributors, consider adding org-balanced voting or transitioning to an elected steering committee.
See The transition points below. Best for: Large projects with established contributor communities where leadership accountability to the broader community matters. A steering committee is elected by eligible contributors and provides strategic direction, while delegating technical work to working groups or Special Interest Groups (SIGs). Elections create accountability, and term limits and company representation limits ensure diversity of perspective. Some projects call this a Technical Steering Committ