On 21Aug2019 1626, Jeremy Kloth wrote:
On Wed, Aug 21, 2019 at 2:43 PM Steve Dower wrote:
https://github.com/python/cpython/commit/75e064962ee0e31ec19a8081e9d9cc957baf6415
commit: 75e064962ee0e31ec19a8081e9d9cc957baf6415
branch: master
author: Steve Dower
committer: GitHub
date: 2019-08-21T1
On Wed, Aug 21, 2019 at 2:43 PM Steve Dower wrote:
>
> https://github.com/python/cpython/commit/75e064962ee0e31ec19a8081e9d9cc957baf6415
> commit: 75e064962ee0e31ec19a8081e9d9cc957baf6415
> branch: master
> author: Steve Dower
> committer: GitHub
> date: 2019-08-21T13:43:06-07:00
> summary:
>
>
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
anoth
We have a new Python triage team on GitHub to help improve our workflow.
GitHub has a nice table that shows what a triager can or cannot do in
general:
https://help.github.com/en/articles/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level
More specific ro
That's perfect! Thank you for clarifying this.
On Tuesday, August 20, 2019, 5:09:43 PM GMT+2, Guido van Rossum
wrote:
The LICENSE file at the top is all you need. There is no need to contact
inidividual contributors. That's the whole point of how Python licensing is set
up.
On Tue,
