-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
GOV more pragmatic decision making process for small PRs #31430
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
base: main
Are you sure you want to change the base?
Conversation
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. Thank you!!
@scikit-learn/core-devs @scikit-learn/communication-team @scikit-learn/contributor-experience-team @scikit-learn/documentation-team Open for voting. PS: Hope I pinged correctly 😄 |
@thomasjpfan I thought we had moved away from the "core contributor" terminology. Otherwise it implies all other roles are "non-core". |
@reshamas With the current governance, all the named roles are considered "core". Specifically, the contributor experience, communication, documentation, and maintainer teams are all "core contributors". Before this PR, only the maintainer team can approve PRs. With this PR, any of the other teams can approve PRs. Although, in practice, I think we normally considered the other approvals as valid. |
@reshamas Earlier it was „core developer“ or „core maintainer“. Because we have more roles than just devs or maintainers, we called the privileged group (voting right etc) „core contributor“. |
@reshamas So particular you have voting rights! |
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.
Honest question, shall we modify the terminology across the documentation e.g. in about.rst
? Such that it's clear who are those referred here.
In any case I'm giving my +1.
Reference Issues/PRs
This was discussed during the monthly meeting 2025-03-31 https://github.com/scikit-learn/administrative/blob/master/monthly_meetings/2025-03-31.md.
What does this implement/fix? Explain your changes.
Make it easier for smaller PRs to be merged by only requiring 1 review.
Any other comments?
Changed "maintainer" by the newer term "core contributor".