WIP: add governance review#151
Conversation
Signed-off-by: Zhonghu Xu <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a comprehensive CNCF Governance Review and Assessment for the Volcano project's graduation application. The review covers aspects such as governance evolution, discoverability, maintainer lifecycle, and subprojects. Feedback on the document includes removing an extra blank line, correcting a broken link to the security team documentation, and adding a missing newline at the end of the file.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| - The maintainer body demonstrates vendor-neutrality and survivability, with active maintainers from NVIDIA, Huawei, Baidu, and Hjmicro. | ||
| - The community has expanded its meeting schedule across Asia, Europe, and Pacific time zones, which improves accessibility for a global contributor base. | ||
|
|
||
|
|
There was a problem hiding this comment.
There's an extra blank line here. Please remove it to improve formatting consistency and readability.
|
|
||
| Role assignment for the main project is documented through the community membership ladder. Members, Reviewers, Approvers, Maintainers, each have documented requirements, sponsorship rules, responsibilities, and privileges. | ||
|
|
||
| Security team and process are documented in [Security Team](../security-team). |
There was a problem hiding this comment.
This link to ../security-team appears to be broken or incorrect. The document likely intends to reference the security process documentation. Other parts of this review reference SECURITY.md for security-related topics. Please update the link to point to the correct document, which is likely ../SECURITY.md.
| Security team and process are documented in [Security Team](../security-team). | |
| Security team and process are documented in [Security Team](../SECURITY.md). |
| Assessment: Satisfactory. Contributor and community processes are well documented and publicly discoverable. Consolidating subproject communications would further improve completeness. | ||
|
|
||
| [project milestone or other requirement]: https://github.com/cncf/toc/tree/main/process#how-to-apply-to-move-levels | ||
| [vendor-neutrality]: https://contribute.cncf.io/maintainers/community/vendor-neutrality/ No newline at end of file |
There was a problem hiding this comment.
The file is missing a newline character at the end. It's a good practice to end files with a newline character to avoid issues with file concatenation and some command-line tools.
| [vendor-neutrality]: https://contribute.cncf.io/maintainers/community/vendor-neutrality/ | |
| [vendor-neutrality]: https://contribute.cncf.io/maintainers/community/vendor-neutrality/ | |
2 participants
No description provided.