Graduation Process: Contributors and Community

[varodrig]

Contributors and Community

Note: this section may be augmented by the completion of a Governance Review from TAG Contributor Strategy.

Suggested

• [x] Contributor ladder with multiple roles for contributors.

Required

• [x] Clearly defined and discoverable process to submit issues or changes.

• [x] Project must have, and document, at least one public communications channel for users and/or contributors.

• [x] List and document all project communication channels, including subprojects (mail list/slack/etc.). List any non-public communications channels and what their special purpose is.

• [x] Up-to-date public meeting schedulers and/or integration with CNCF calendar.

• [x] Documentation of how to contribute, with increasing detail as the project matures.

• [x] Demonstrate contributor activity and recruitment.

[andreyvelich]

/area cncf-graduation

[franciscojavierarceo]

This is already done on the website and on the community repo

[franciscojavierarceo]

https://github.com/kubeflow/community/blob/master/ADOPTERS.md