diff --git a/triaging.rst b/triaging.rst index 2f09d078d1..464248984d 100644 --- a/triaging.rst +++ b/triaging.rst @@ -43,11 +43,35 @@ 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 the 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 triager +is more elevated than a developer on bpo. For example, the Python triager +has access to more repositories than just CPython. Triagers will be responsible +to handle not just issues, but also pull requests, and even managing backports. + +Any existing developers on b.p.o can transition into becoming a Python triager. +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 confidentially via a DM in Zulip or Discourse, or publicly by opening +an `issue in the core-workflow repository +`_. + +Any contributor who is not already a developer on b.p.o can also self-nominate +to be a member of Python triage team. They can request this to any core developer, +confidentially via DM in Zulip or Discourse, or publicly by opening an issue in core-workflow. +If a core developer agrees and is willing to vouch for them, the core developer +can pass the request to the GitHub administrator. They should also be added as +developer on bpo. + +For every new triager, it would be great to announce them in the python-committers +mailing list and core-workflow category in Discourse. `Example announcement +`_. - 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 '''''''''''''''''''''