Skip to content
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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

anishasthana
Copy link
Contributor

@anishasthana anishasthana commented Jul 24, 2024

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 google-oss-prow bot requested a review from 8bitmp3 July 24, 2024 21:37
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign terrytangyuan for approval. For more information see the Kubernetes Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

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.

Copy link
Contributor

@hbelmiro hbelmiro left a 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

cc @terrytangyuan

Copy link

New changes are detected. LGTM label has been removed.

@google-oss-prow google-oss-prow bot added size/L and removed size/S labels Aug 7, 2024
@anishasthana anishasthana changed the title Make basic community membership guidelines clearer WIP: Make basic community membership guidelines clearer Aug 7, 2024
@anishasthana anishasthana force-pushed the update_community_membership_guidelines branch from 2931fd6 to 4b3de1b Compare August 7, 2024 01:29
@anishasthana anishasthana force-pushed the update_community_membership_guidelines branch 2 times, most recently from b17b1ac to b0d245b Compare August 7, 2024 14:30
@anishasthana anishasthana force-pushed the update_community_membership_guidelines branch 2 times, most recently from 908075a to 90c127a Compare August 7, 2024 14:35
Copy link
Member

@terrytangyuan terrytangyuan left a 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.

@andreyvelich
Copy link
Member

@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
Copy link
Contributor Author

@andreyvelich this PR is ready for second review

Copy link
Member

@tarilabs tarilabs left a 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.

content/en/docs/about/membership.md Outdated Show resolved Hide resolved
content/en/docs/about/membership.md Show resolved Hide resolved
@terrytangyuan terrytangyuan changed the title WIP: Make basic community membership guidelines clearer Make basic community membership guidelines clearer Sep 24, 2024
@terrytangyuan
Copy link
Member

My only comment is unaddressed #3827 (comment) but otherwise LGTM. Thank you for improving the process!

Copy link
Member

@andreyvelich andreyvelich left a 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
Copy link
Member

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/

Copy link
Contributor Author

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/)
Copy link
Member

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

Copy link
Member

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 ?

Copy link
Contributor Author

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?

Copy link
Member

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

content/en/docs/about/contributing.md Show resolved Hide resolved
content/en/docs/about/contributing.md Show resolved Hide resolved
+++


**Note:** This document is a work in progress
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


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
Copy link
Member

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
Copy link
Member

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.

Copy link
Contributor Author

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 Show resolved Hide resolved
- 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
Copy link
Member

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 ?

### 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.
Copy link
Member

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""

Copy link
Member

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"?

@andreyvelich
Copy link
Member

/assign @StefanoFioravanzo @kubeflow/kubeflow-steering-committee @franciscojavierarceo

@andreyvelich
Copy link
Member

cc @akgraner

@anishasthana anishasthana force-pushed the update_community_membership_guidelines branch 4 times, most recently from 4a783b4 to 7bd7793 Compare September 27, 2024 18:38
Signed-off-by: Anish Asthana <[email protected]>
@anishasthana anishasthana force-pushed the update_community_membership_guidelines branch from 7bd7793 to 80c5677 Compare September 27, 2024 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants