Skip to content

Enhancement: Unclear description of how to become a triager #1595

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

Open

LamentXU123 wants to merge 2 commits into python:main

from LamentXU123:main

Open

Enhancement: Unclear description of how to become a triager #1595

Changes from all commits

Commits

Show all changes

Select commit Hold shift + click to select a range

Update triage-team.rst

LamentXU123 Jun 30, 2025

Update triage-team.rst

LamentXU123 Jun 30, 2025

File filter

Filter by extension

Conversations

Jump to

Jump to file

Failed to load files.

Loading

Diff view

Diff view

4 changes: 2 additions & 2 deletions triage/triage-team.rst

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -84,8 +84,8 @@ workload for everyone by gaining your help.

		Any existing active contributor to the Python repository on GitHub can
		transition into becoming a Python triager. They can request this to any core
	developer, either confidentially via a DM in Discourse, or
	publicly by opening an `issue in the core-workflow repository
	developerconfidentially via a DM in Discourse. The only way of becoming a triager is
	to be nominated by any core developer, who will open an `issue in the core-workflow repository
		<https://github.com/python/core-workflow/issues/new?template=triage_membership.md>`_.
		If the core developer decides you are ready to gain the extra privileges on the
		tracker, they will ask a :ref:`Python organization admin <current owners>`
Expand Down

Loading