Skip to content
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
Link to org admin document
also change from privately -> confidentially
  • Loading branch information
Mariatta authored Aug 15, 2019
commit cb06a4c9082ab85fdc012f1cca87661416e1238b
8 changes: 5 additions & 3 deletions triaging.rst
Original file line number Diff line number Diff line change
Expand Up @@ -54,14 +54,16 @@ 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
Comment thread
Mariatta marked this conversation as resolved.
can pass the request to the Python organization admin on GitHub. The request
can be made privately via a DM in Zulip or Discourse, or publicly by opening
can pass the request to the `Python organization admin
<https://devguide.python.org/devcycle/?highlight=organization%20admin#current-owners>`_
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
<https://github.com/python/core-workflow/issues/new?template=triage_membership.md>`_.

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,
via DM in Zulip or Discourse, or publicly by opening an issue in core-workflow.
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.
Expand Down