Allow triagers to close PRs if the PR is of very low quality (#828)
Allow triagers to close PRs if the PR is of very low quality (#828)

As discussed on the CPython core-dev discord channel, there are several issues of the current policy that states that triagers should never close PRS:
- Github's setup allows members of the triage team to close PRs, regardless of the policy stated in the devguide.
- This policy isn't consistently followed by all members of the triage team. Some triagers occasionally close PRs (I have closed one or two myself in situations where it seemed abundantly clear that there was no prospect of the PR being merged).
- This policy isn't really enforced in any way if triagers do close PRs. This lack of enforcement seems to be an implicit endorsement of the idea that it is okay for triagers to close PRs in some circumstances.
- It feels silly to have to bother a core dev with a request for a PR to be closed if it's self-evident that it should be closed (e.g. if the PR makes changes to a deprecated module, makes solely cosmetic changes to a module, or simply has a 0% chance of ever being merged)
- Changing this policy will help towards the goal of reducing the CPython PR backlog

Co-authored-by: Hugo van Kemenade <5a499df1e6a266942706a9de3d4c03795108f8e3@users.noreply.github.com>
ezio-melotti/devguide