-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make basic community membership guidelines clearer #3827
base: master
Are you sure you want to change the base?
Make basic community membership guidelines clearer #3827
Conversation
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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 Once the patch is verified, the new status will be reflected by the 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/ok-to-test
New changes are detected. LGTM label has been removed. |
2931fd6
to
4b3de1b
Compare
Signed-off-by: Anish Asthana <[email protected]>
b17b1ac
to
b0d245b
Compare
908075a
to
90c127a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
@anishasthana Did you address all of the comments from this PR: kubeflow/community#737? /assign @kubeflow/wg-training-leads @kubeflow/wg-automl-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-data-leads |
@andreyvelich this PR is ready for second review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
My only comment is unaddressed #3827 (comment) but otherwise LGTM. Thank you for improving the process! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for driving this @anishasthana!
I left my comments.
Also, should we also add the section for WG Leads and WG Chairs ?
I think, it would be nice to explain how to become WG members in this doc as well.
|
||
### Follow the code of conduct | ||
|
||
Please make sure to read and observe our [Code of Conduct](https://github.com/kubeflow/community/blob/master/CODE_OF_CONDUCT.md) | ||
and [inclusivity document](https://github.com/kubeflow/community/blob/master/INCLUSIVITY.md). | ||
|
||
## Joining the community | ||
## Membership |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we link this doc from the Community doc ? I think, it would be nice to reference it from there
https://deploy-preview-3827--competent-brattain-de2d6d.netlify.app/docs/about/community/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
|
||
Follow these instructions if you want to: | ||
Details about the different types of Kubeflow members as well as membership criteria can be found at [Community Membership](/docs/about/membership/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the different types of Kubeflow members
Is that statement correct ?
E.g. currently, we have information about Kubeflow WGs here: https://deploy-preview-3827--competent-brattain-de2d6d.netlify.app/docs/about/community/#kubeflow-working-groups
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should move this part into Community Membership doc, WDYT @anishasthana @terrytangyuan @kubeflow/kubeflow-steering-committee @StefanoFioravanzo @hbelmiro ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is that statement correct ?
I think it is -- the changes in the other file are introducing the contents right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence seems correct to me
+++ | ||
|
||
|
||
**Note:** This document is a work in progress |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want, you can try to use Hugo rendered Notes, like here: https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/workloads/controllers/job.md?plain=1#L309-L315.
They look pretty nice on the website: https://kubernetes.io/docs/concepts/workloads/controllers/job/#handling-pod-and-container-failures:~:text=Note%3A,they%20are%20detected.
content/en/docs/about/membership.md
Outdated
|
||
The following apply to the part of codebase for which one would be an approver in an [OWNERS] file (for repos using the bot). | ||
|
||
- Reviewer of the codebase for at least 3 months |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should also approver be the reviewer before ?
- Reviewer of the codebase for at least 3 months | ||
- Primary reviewer for at least 10 substantial PRs to the codebase | ||
- Reviewed or merged at least 30 PRs to the codebase | ||
- Nominated by a WG Lead, Chair or owner |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would only leave WG Lead or Chair.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking of situations where a root approver may nominate an approver for a subdirectory or similar. WG Leads and Chairs aren't necessarily involved with the day-to-day of every repository right?
content/en/docs/about/membership.md
Outdated
- Reviewed or merged at least 30 PRs to the codebase | ||
- Nominated by a WG Lead, Chair or owner | ||
- With no objections from other Leads or owners | ||
- Done through PR to update the top-level OWNERS file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be top-level OWNER ?
content/en/docs/about/membership.md
Outdated
### How inactivity is measured | ||
|
||
Inactive members are defined as members of one of the Kubeflow Organizations | ||
with **no** contributions across any organization within 12 months. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should explicitly say ""with no technical and non-technical contributions""
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't that the same as "with no contributions"?
/assign @StefanoFioravanzo @kubeflow/kubeflow-steering-committee @franciscojavierarceo |
cc @akgraner |
4a783b4
to
7bd7793
Compare
Signed-off-by: Anish Asthana <[email protected]>
7bd7793
to
80c5677
Compare
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