This is somewhat related to PEP 581, but I’m thinking we can benefit from having a Bug triage team even now.
Proposal: Create a “Bug triage” team to Python’s GitHub repos (not just CPython, but other repos like devguide, core-workflow), and grant this permission to people who currently hold the “bug triager” permission on bpo.
Reason: Bug triagers are valuable to our workflow, they can help with applying appropriate labels, closing issues/PRs. At the moment only core developers can do this. By granting bpo bug triagers capabilities to apply labels, closing issues, marking things as “easy” etc, it will help lessen the workload of a core developer, and at the same time empowering the active contributors to continue participating in core Python development.
- We can grant write privileges to the “Bug Triage” team, but restrict the merging to the “CPython core developers” team (by adding branch protection)
- miss-islington should only allow “ automerge” label to be added only by core developers
- we’ll also want to clean up inactive “Bug Triagers” from bpo before going forward.
- There is no GitHub API for “nosying”/“subscribing” someone to an issue/PR (unlike the “nosy” feature in bpo), the only way to do this is by @-mention someone on GitHub. Because of this, we will need to come up with some kind of etiquette/guideline on when people should be @-mentioned, and include it to the devguide.
- Sounds good
- I’m concerned … (explain)
- This needs a PEP