We have a new Python triage team on GitHub to help improve our workflow.

GitHub has a nice table that shows what a triager can or cannot do in general:

More specific roles and responsibilities of the Python triage team are described in devguide:

The responsibilities are a little different than the Developer role that we currently have on b.p.o. On GitHub, triage team members have access to triage issues and pull requests not only in CPython repo, but also all the repositories owned by Python core team, including: devguide repo and all the bots' repos.

Existing b.p.o Developers are not automatically added to Python triage team, but they can opt-in and request membership. Several reasons:
- we don't know if the triager is still active or not
- we don't know if the triager wants the added responsibilities or not

Other contributors are also welcome to request the Python triage membership. All it takes is one core developer to approve the request.

The process is fully documented in https://devguide.python.org/triaging/#becoming-a-member-of-the-python-triage-team, and there is an issue template for requesting membership in core-workflow https://github.com/python/core-workflow/issues/new/choose

The first two triage team members are Kyle Stanley and Jeroen Demeyer.
Their requests were handled in:

If you'd like more background on Python triage team and how we came to this stage, all of these have been discussed in discourse:

We also have a project board in core-workflow: https://github.com/python/core-workflow/projects/3

This is a new thing for us, and we're all still learning and getting use to it. Suggestions and ideas for improving the workflow can be discussed in Core Workflow category in discourse. Devguide improvements are also welcome.

Thanks contributors, core devs, and The PSF infra team for all the help in getting this off the ground. And also thanks GitHub for giving us early access to the beta triage role!