This issue is intended to track and discuss the requirements to move Operator Framework (along with its sub-projects) to graduate level from incubation. The following are the requirements set-forth by the CNCF:
[ ] Clear and discoverable project governance documentation.
[ ] Governance is up to date with actual project activities, including any meetings, elections, leadership, or approval processes.
[ ] Governance clearly documents vendor-neutrality of project direction.
[ ] Document how the project makes decisions on leadership roles, contribution acceptance, requests to the CNCF, and changes to governance or project goals.
[ ] Document how role, function-based members, or sub-teams are assigned, onboarded, and removed for specific teams (example: Security Response Committee).
[ ] Document complete list of current maintainers, including names, contact information, domain of responsibility, and affiliation.
[ ] A number of active maintainers which is appropriate to the size and scope of the project.
[ ] Document a complete maintainer lifecycle process (including roles, onboarding, offboarding, and emeritus status).
[ ] Demonstrate usage of the maintainer lifecycle with outcomes, either through the addition or replacement of maintainers as project events have required.
[ ] Project maintainers from at least 2 organizations that demonstrates survivability.
[ ] Code and Doc ownership in Github and elsewhere matches documented governance roles.
[ ] Document agreement that project will adopt CNCF Code of Conduct.
[ ] CNCF Code of Conduct is cross-linked from other governance documents.
[ ] All subprojects, if any, are listed.
If the project has subprojects: subproject leadership, contribution, maturity status documented, including add/remove process.
This issue is intended to track and discuss the requirements to move Operator Framework (along with its sub-projects) to graduate level from incubation. The following are the requirements set-forth by the CNCF:
Graduation application template: Link