-
-
Notifications
You must be signed in to change notification settings - Fork 845
Add procedure for adding people to the Python Triage team #521
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
Conversation
A suggestion from what I posted on discuss. To reduce traffic to the core team, is there a problem or risk with current bpo triagers publicly opening an issue in core-workflow with details confirming they have triage rights on bpo already and requesting to be added to the Python Triage Team? |
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 for the PR Mariatta. I think this extensively covers the consensus reached in the Discuss topic. I had a few minor suggestions, but I would approve of this section either way.
triaging.rst
Outdated
has access to more repositories than just CPython. Triages will be responsible | ||
to handle not just issues, but also pull requests, and even commanding backports. | ||
|
||
Any existing triagers in b.p.o can transition to the Python Triage role. |
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.
Even simpler:
Any existing triagers in b.p.o can transition to the Python Triage role. | |
Any existing triager in b.p.o can become a Python triager. |
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.
Personally, I think that we should refer a member of the role on on bpo as a "developer". That is the official name of the role on there, and it also helps to avoid confusing it with the new Python triagers on GitHub.
Co-Authored-By: Kyle Stanley <[email protected]>
Promoting and recognizing contributors and triagers are responsibilities of core developers. If for some reason core devs find this too noisy, can they can filter out Github email notification containing "Request for Python Triage membership". But that should be personal choice. |
Additionally, there is potential for automating the process (described in python/core-workflow#350) |
Awesome! This would definitely be far more time effective than requiring a core dev to contact an org admin, and requiring them to manually invite the person as a triager. If the steering council decided to block the promotion, the persons permissions could simply be removed. But perhaps a better way to do this would require a set amount from when the PR is approved to when they're sent the invite. |
also change from privately -> confidentially
Good! maybe will be great mention if anybody apply (or self apply) to be a member of the team, What do you think? |
Thanks all for the reviews.
Sounds great. Feel free to propose a PR for this. |
Based on discussion: https://discuss.python.org/t/criteria-for-promoting-people-to-the-python-triage-team/2105/ Closes python#308 Co-Authored-By: Kyle Stanley <[email protected]>
Based on discussion: https://discuss.python.org/t/criteria-for-promoting-people-to-the-python-triage-team/2105/
Closes #308