Skip to content

website: Adjust contributor progression guidelines to foster community growth #4061

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rareddy
Copy link
Contributor

@rareddy rareddy commented Mar 27, 2025

Checklist:

  • [ x] You have signed off your commits
  • [ x] Ensure you follow best practices from our guide. Contributing.
  • You have included screenshots when changing the website style or adding a new page.

Description of your changes:
A minor variation to the requirements of the Kubeflow membership agreement.

The suggestion is to start the reviewer vetting period from the first contribution rather than from membership.

Issue

As being owner and contributor of the Model registry component and part of the community what I observed is

  • The current process from new member to committer takes too long (7-12 months) in the best-case scenario.
  • There are artificial time constraints between stages that may be unnecessary.
  • IMO, it is not balanced towards fairness and community growth.
  • We should be placing the importance of observing contributions over time not artificially keeping someone out.
  • I do hope this encourages more active participation from new contributors, and recognize them quickly.
  • IMO, there is not much difference between the reviewer and member as both can do this task; it is more on the approver to trust the reviewer; time is not giving any trust, anyway, I did not make any changes there.
  • full disclaimer, I do have many associates who are trying to earn their stripes and mentioned to me that this is a concern.

</area website>

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

@rareddy rareddy changed the title Webiste: Adjust contributor progression guidelines to foster community growth webiste: Adjust contributor progression guidelines to foster community growth Mar 27, 2025
@rareddy rareddy changed the title webiste: Adjust contributor progression guidelines to foster community growth website: Adjust contributor progression guidelines to foster community growth Mar 27, 2025
@tarilabs
Copy link
Member

I support/welcome these proposed changes

/lgtm

@rareddy rareddy force-pushed the contributor-agreement branch from df7d28b to ede6ee6 Compare March 31, 2025 18:51
@google-oss-prow google-oss-prow bot removed the lgtm label Mar 31, 2025
Copy link

New changes are detected. LGTM label has been removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants