As part of the CNCF graduation due diligence review, we are specifically reviewing the Engineering Principles requirement:
Roadmap change process is documented.
In the current DD application (cncf/toc#1538), this points to:
buildpacks/community/GOVERNANCE.md#roadmap
Problem / What’s confusing today
GOVERNANCE.md#roadmap currently states that the TOC is responsible for establishing a yearly roadmap, but it does not clearly describe the roadmap change process. For external reviewers (including CNCF reviewers) following the DD link to GOVERNANCE.md#roadmap, the documented “change process” is not obvious.
In practice, the roadmap lifecycle appears to be driven through the RFC repository (e.g., roadmap RFCs) and then implemented by updating buildpacks/community/ROADMAP.md via PR, but this end-to-end flow is not summarized in GOVERNANCE.md.
Would be great to add a short mention of this in governance document to show how the roadmap change process is.
As part of the CNCF graduation due diligence review, we are specifically reviewing the Engineering Principles requirement:
In the current DD application (cncf/toc#1538), this points to:
buildpacks/community/GOVERNANCE.md#roadmapProblem / What’s confusing today
GOVERNANCE.md#roadmapcurrently states that the TOC is responsible for establishing a yearly roadmap, but it does not clearly describe the roadmap change process. For external reviewers (including CNCF reviewers) following the DD link toGOVERNANCE.md#roadmap, the documented “change process” is not obvious.In practice, the roadmap lifecycle appears to be driven through the RFC repository (e.g., roadmap RFCs) and then implemented by updating
buildpacks/community/ROADMAP.mdvia PR, but this end-to-end flow is not summarized inGOVERNANCE.md.Would be great to add a short mention of this in governance document to show how the roadmap change process is.