governance-subprojects

To document subproject governance for a CNCF project, you create a GOVERNANCE-subprojects.md file detailing each component's ownership, scope, leadership, and maturity status to ensure compliance.

A CNCF subproject governance structure defines how distinct project components relate to top-level governance, outlining formal ownership, scope boundaries, and the processes for creating and archiving subprojects.

You need to define subproject ownership documentation when your growing CNCF project has multiple distinct components requiring formal ownership tracking and compliance with CNCF governance requirements.

You list official subprojects and their maturity status by creating an inventory in the GOVERNANCE-subprojects.md file, capturing the scope, maintainers, and leadership details for each component.

Yes, CNCF governance compliance requires defining formal subproject archiving processes within your documentation to manage the lifecycle of distinct project components properly.

Documentation for multiple project components is limited to defining inventory, creation, and archiving processes, requiring clear scope boundaries to prevent overlapping ownership and maintain CNCF compliance.