search

dask / governance

The governance process and model for Dask
Creative Commons Zero v1.0 Universal
7 stars 10 forks source link

Issue Triage Rights #17

Open mrocklin opened 3 years ago

mrocklin commented 3 years ago

Hi all,

We have a process for granting membership to the org, commit access to a repository, and ownership over the org. We don't have a process for granting triage rights (the ability to close issues, manage labels, etc.).

I think that this should be fairly light weight. I propose one of the following:

  1. Get permission from one other owner working at a different company
  2. Any owner can do this for anyone

Any thoughts?

mrocklin commented 3 years ago

For context we currently have a Triage team with triage rights. That's the system that we would be using here.

jrbourbeau commented 3 years ago

Sure, those steps seem fine to me. For reference, @jsignell and I have just been running it by each other before adding people to the triage team, which would satisfy the proposed criteria.

Note that in order for someone to be added to a GitHub org team, they need to be a member of the org. Since any owner admin can already add members, this shouldn't be a big deal. Just a heads up for when someone goes to add someone to the triage team.

jakirkham commented 3 years ago

AIUI one requires write permission on a repo to do these things (unless GH has changed something). So this also grants the ability to merge PRs and push commits to the repo. Not sure if that’s what is intended here

jrbourbeau commented 3 years ago

GitHub now has triage permissions which let people add labels and close issues and PRs without having write permissions. The current triage team in the Dask org grants triage permissions to dask/dask and dask/distributed.

EDIT: So I think we should be okay to grant folks triage permissions which are independent of commit privileges

jsignell commented 3 years ago

This approach works for me.