Make basic community membership guidelines clearer

[anishasthana]

This PR adds guidelines around the kubeflow community membership.

This set of guidelines is heavily inspired by the Kubernetes guidelines at https://github.com/kubernetes/community/blob/master/community-membership.md?plain=1#community-membership

cc @kubeflow/kubeflow-steering-committee

[google-oss-prow]

Hi @anishasthana. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[hbelmiro]

/lgtm
/ok-to-test

cc @terrytangyuan

[terrytangyuan]

This would be a great improvements over the current process. Thanks!

One thing that is being discussed is how to encourage non-code contributions. This may not be something this PR covers and can be future improvements IMO. I'll share with the outreach team to help review.

[andreyvelich]

@anishasthana Did you address all of the comments from this PR: kubeflow/community#737?
Is this PR ready for the second review ?

/assign @kubeflow/wg-training-leads @kubeflow/wg-automl-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-data-leads

[anishasthana]

@andreyvelich this PR is ready for second review

[tarilabs]

Thanks @anishasthana I believe a clearer guideline helps a lot !

Wdyt about the suggestions below, based on previously received feedback.
Thank you for your consideration in any case.

[anishasthana]

Looks like usage of the layout is causing this. I'm not sure what's up... taking a look

[anishasthana]

aaand fixed. @andreyvelich Please take a look!

[andreyvelich]

Thank you for this effort @anishasthana!
/lgtm
/assign @terrytangyuan @kubeflow/kubeflow-steering-committee @hbelmiro @StefanoFioravanzo

[terrytangyuan]

/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: terrytangyuan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [terrytangyuan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tarilabs]

thank you @anishasthana for this work, makes a great improvement on governance aspects