Document clear community membership guidelines
The current community member guidelines for Kubeflow are not clearly defined, which can definitely act as a barrier to entry for new contributors.
https://www.kubeflow.org/docs/about/contributing/ contains some high level details on the roles, but no clear criteria on what allows contributors to apply for community membership, reviewer status, or approver status.
The Argo Project seems to have pretty clearly defined membership criteria. We should do something similar for Kubeflow.
Kubernetes has another great one here: https://github.com/kubernetes/community/blob/master/community-membership.md#community-membership
cc @terrytangyuan
cc @kubeflow/kubeflow-steering-committee
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.