> For instance, I don't think a triager should be able to edit other users' comments or lock conversations, but I'm afraid GitHub
> doesn't provide that level of granularity (correct?).

You are correct in that GitHub does not allow customization of the permissions, but those with the  "Triage" permission are unable to edit comments or lock conversations. In order to do either of those, the "Write" permission is required. Compared to a normal contributor, triagers are only able to add labels, close, reopen, and assign PRs/Issues.

On Fri, Aug 23, 2019 at 2:01 PM Giampaolo Rodola' <g.rodola@gmail.com> wrote:
If the concern is pruning old/stale/invalid issues/PRs, I think the proposal to add a specific "awaiting-close" (or similar) label should work. These issues can periodically be handled by a core-dev who can click on the label, then evaluate and bulk-close them in one shot if necessary. Also, it seems to me that including "devguide" and "core-workflow" repos is unnecessary since they are low-traffic administrative repos related to our internal workflow, they are attended by a small portion of the core-dev team only and labels don't play a central role as in the cpython repo. Please let's keep in mind that this role implies higher responsibilities than a usual contributor, and since the bar for being promoted is considerably lower than a core-dev's, triager permissions should reflect that and remain minimal. For instance, I don't think a triager should be able to edit other users' comments or lock conversations, but I'm afraid GitHub doesn't provide that level of granularity (correct?).

--



_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/2YYB6MAJ55U2U4KTKINFDSB4USJ3NMZY/