Governance guidance for CNCF projects: Choosing the right structure for your project’s size and stage

CNCF's governance review of 72 projects reveals a clear gap between what the foundation formally requires and what the data shows actually works. The requirements focus on documentation and process, but the data demonstrates that structural mechanisms like org-balanced voting and steering committees are what sustain maintainer diversity over time. This distinction matters because many projects meet CNCF's formal requirements while still experiencing maintainer concentration that threatens long-term health.

The guidance identifies three governance models that map to different project archetypes. Maintainer councils work well for small, tightly-scoped projects with cohesive contributor groups, but become problematic when a single organization dominates. Elected steering committees with term limits and org representation caps work better for large projects with established contributor communities. The third model, working groups with delegated authority, suits projects with enough scope to benefit from separating strategic direction from technical execution.

The data shows that documentation alone cannot prevent governance concentration. Multiple projects with well-written governance documents still experienced maintainer concentration because they lacked structural mechanisms like org-balance voting. This finding challenges the common assumption that good documentation is sufficient for healthy governance. The guidance emphasizes that org-balance mechanisms need to cover where the work happens, not just the governance layer, as seen in one archived project that had diversity rules for its governance committee but not its maintainer body.

Contributor count proves to be a poor predictor of project health compared to governance structure and organizational diversity. This insight shifts focus from raw contributor numbers to the pathways and structures that sustain diverse participation. The guidance provides concrete transition points where projects should evolve their governance model, such as when a single organization comes to dominate the maintainer list through hiring or attrition. These transition points help engineers anticipate governance needs before problems emerge.