8000 Add procedure for adding people to the Python Triage team by Mariatta · Pull Request #521 · python/devguide · GitHub
[go: up one dir, main page]
Skip to content

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.

Sign up for GitHub

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

Merged
merged 5 commits into from
Aug 17, 2019
Merged

Add procedure for adding people to the Python Triage team #521

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
125cf58
Add procedure for adding people to the Python Triage team
Mariatta Aug 9, 2019
ff7549b
Apply suggestions from code review
Mariatta Aug 12, 2019
a9e1c15
Update triaging.rst
Mariatta Aug 12, 2019
6a1716b
link to the triage membership template
Mariatta Aug 12, 2019
cb06a4c
Link to org admin document
Mariatta Aug 15, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 25 additions & 4 deletions triaging.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,11 +43,32 @@ or a veteran core developer, they're actively choosing to voluntarily donate the
time towards the improvement of Python. As is the case with any member of
the Python Software Foundation, always follow the `PSF Code of Conduct`_.

.. note::
Becoming a member of Python Triage team
---------------------------------------

Any Python core developers are welcome to invite a Python contributor to the
Python Triage team. Do note that the responsibilities of a Python Triage member
is more elevated than a bug triager in bpo. For example, the Python Triage member
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.
Copy link
Member

Choose a reason for hiding this comment

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

Even simpler:

Suggested change
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.

Copy link
Contributor
@aeros aeros Aug 10, 2019 •
edited
Loading

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.

They can request this to any core developer, and the core developer
can pass the request to the Python organization admin on GitHub. The request
can be made privately via DM in Zulip or Discourse, or publicly by opening
an issue in core-workflow.

Any contributor who is not already a triager in b.p.o can also self-nominate
to be a member of Python Triage team. They can request this to any core developer,
via DM in Zulip or Discourse, or publicly by opening an issue in core-workflow.
If a core developer agrees and willing to vouch for them, the core developer
can pass the request to the administrator. They should also be added as
triager in bpo.

For every new triager, it would be great to announce them in Python-committers
mailing list and core-workflow category in Discourse. `Example announcement
<https://discuss.python.org/t/abhilash-raj-has-been-granted-triage-role-on-github/2089>`_.

Existing members with the "Developer" role on the `issue tracker`_ are welcome to
self-nominate for triage team membership if they are interested.


GitHub Labels for PRs
'''''''''''''''''''''
Expand Down
0