On Wed, 21 Aug 2019 at 22:17, Raymond Hettinger <raymond.hettin...@gmail.com> wrote:
> Thanks for doing this. I hope it encourages more participation. > > The capabilities of a triager mostly look good except for "closing PRs and > issues". This is a superpower that has traditionally been reserved for > more senior developers because it grants the ability to shut-down the work > of another aspiring contributor. Marking someone else's suggestion as > rejected is the most perilous and least fun aspect of core development. > Submitters tend to expect their idea won't be rejected without a good deal > of thought and expert consideration. Our bar for becoming a triager is > somewhat low, so I don't think it makes sense to give the authority to > reject a PR or close an issue. Agreed. Closing an issue basically means having the authority to reject a proposal, which really is not different than accepting it. It's probably the second highest responsibility after being able to merge a PR. The risk is to potentially reject a good proposal without having the expertise and authority to properly evaluate it, which is why we have the core-dev role.
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@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/STV4WIJJ3LBTKQSOOWPLS6EAAUKWN75M/
