Repository navigation
Update core-dev repo permissions - #41
Conversation
|
@zarr-developers/steering-council - what is needed to advance this? |
rabernat
left a comment
rabernat
left a comment
There was a problem hiding this comment.
This change seems necessary to allow sub teams to function independently.
This is a minor change to our governance document. If this change constitutes a "change to the Zarr governance model", then it is a heavy lift
It seems like massive overkill to make a ZEP here. It also feels like getting unanimous agreement from 38 @zarr-developers/core-devs is overkill. I do not interpret this PR as any change to the governance model. It's a technical clarification about what permissions core devs should have in GitHub, designed to help us operate more effectively. I see it more as a "Minor documentation change". I'd say that a few approvals and no disagreement is sufficient to merge. Does anyone disagree with that interpretation? |
|
I agree with your POV @rabernat. As this has been open for nearly a month with no objections, should we try to merge it by the end of the week? |
|
Sorry all. I think this mostly fell through the cracks because the last ZSC meeting got cancelled. Thanks, @jhamman, for opening. I assume as well that it's a clarification and that everyone has time to object. But of course, it can always be reevaluated if need be. Merging tomorrow if no last minute objections appear. |
|
+1 |
Small change to specify what permissions core-dev sub-teams will be granted in the repositories that they manage.
See zarr-developers/zarr-python#1905 and https://github.com/orgs/zarr-developers/discussions/70 for more discussion on the topic.