- Getting started
- Development workflow
- Issues and triaging
- Documentation
- Testing and buildbots
- Development tools
- Core team
- CPython’s internals
- Status of Python versions
- Python Contributor’s Guide (draft)
- [Plan for the Contributor’s Guide]
- Introduction
- The CPython project
- Issues and triaging
- Documentation contributions
- Code contributions
- Core team
- Accessibility, design, and user success
- Security and infrastructure contributions
- Workflows
Triage Team¶
The Python triage team is a group dedicated towards improving workflowefficiency through thoughtful review and triage of open issues and pullrequests. This helps contributors receive timely feedback and enables coredevelopers to focus on reviewed items which reduces their workload. Theexpectations of this role expand upon the “Triager” role on theissue tracker. The responsibilities listed below are primarily centeredaround the Python GitHub repositories. This extends beyond CPython, and, asneeded, to other repos such as devguide and core-workflow.
Responsibilities include:
Classifying issues and PRs
Applying appropriatelabels to issues/PRs
Notifying appropriate core developers
Assisting contributors
Although triagers have the power to close PRs, they should generally not do sowithout first consulting a core developer. By having triagers and core developers work together,the author receives a careful consideration of their PR. This encourages futurecontributions, regardless of whether their PR is accepted or closed.
Nonetheless, triagers should feel free to close a PR if they judge that thechance of the PR being merged would be exceedingly low, even if substantialrevisions were made to the PR. This includes (but is not limited to) thefollowing:
PRs proposing solely cosmetic changes
PRs proposing changes to deprecated modules
PRs that are no longer relevant. This includes:
PRs proposing fixes for bugs that can no longer be reproduced
PRs proposing changes that have been rejected by Python core developerselsewhere (for example, in an issue or a PEP rejection notice)
If a triager has any doubt about whether to close a PR,they should consult a core developer before taking any action.
Triagers can also make use of thepending andstalelabels to suggest that a PR may be suitable for closure.For more information, see the entries in theOther labels section.
Note that it is of paramount importance to treat every contributor to the Pythonproject kindly and with respect. Regardless of whether they’re entirely newor a veteran core developer, they’re actively choosing to voluntarily donate theirtime towards the improvement of Python. As is the case with any member ofthe Python Software Foundation, always follow thePSF Code of Conduct.
Becoming a member of the Python triage team¶
All Python core developers are welcome to invite a Python contributor to thePython triage team. Triagers will be responsible to handle not just issues, butalso pull requests, and even managing backports. A Python triager has access tomore repositories than just CPython.
When you have consistently shown the ability to properlyhelp triage issues without guidance, you may request that yoube given the “Triager” role on theissue tracker.You can make the request to any core developer. If they decide you are readyto gain the extra privileges on the tracker they will then act as a mentor toyou until you are ready to do things entirely on your own. There is no set ruleas to how many issues you need to have helped with before or how long you havebeen participating. The key requirements are that you show the desire tohelp, you are able to work well with others (especially those already with theTriager role), and that have a firm grasp of how to do things on the issuetracker properly on your own.
Gaining the Triager role will allow you to set any value on any issue in thetracker, releasing you from the burden of having to ask others to set values onan issue for you in order to properly triage something. This will not only helpspeed up and simplify your work in helping out, but also help lessen theworkload for everyone by gaining your help.
Any existing active contributor to the Python repository on GitHub cantransition into becoming a Python triager. They can request this to any coredeveloper, either confidentially via a DM in Discourse, orpublicly by opening anissue in the core-workflow repository.If the core developer decides you are ready to gain the extra privileges on thetracker, they will ask aPython organization adminto invite you to the Python organisation, and then act as a mentor to you untilyou are ready to do things entirely on your own.
For every new triager, it would be great to announce them in theCommitters categoryon thePython Discourse(example announcement).