document core dev off-boarding procedure

[jhamman]

closes #38

please review:

• @zarr-developers/steering-council
• @zarr-developers/python-core-devs

[martindurant]

+1

[rabernat]

It might make sense to separate the zarr-python governance from the overall zarr governance. Like, the steering council is really not about Python specifically. It's more about the spec, the ZEPs, etc.

Not a requirement for this to go forward, but something we also discussed at the last SC meeting.

[jhamman]

It might make sense to separate the zarr-python governance from the overall zarr governance. Like, the steering council is really not about Python specifically. It's more about the spec, the ZEPs, etc.

Not a requirement for this to go forward, but something we also discussed at the last SC meeting.

If the steering council wants to push on this, I'm happy to see it move this way. As it is written, the governance document does cover both the spec and the implementations in the zarr-developers organization.

[jhamman]

I have modified the core-dev membership votes to only require a majority vote.

Who needs to review / approve this? @zarr-developers/steering-council?

[joshmoore]

jhamman commented 2 days ago
If the steering council wants to push on this, I'm happy to see it move this way. As it is written, the governance document does cover both the spec and the implementations in the zarr-developers organization.

I'd suggest we handle that as a separate, follow-up item.

jhamman commented 15 hours ago
Who needs to review / approve this? @zarr-developers/steering-council?

The answer to that looks to need work itself.

[rabernat]

Looks like there are no objections to this change.