Invitation to Zarr Implementation Council (tensorstore)

attn: @jbms @google

Introduction

Changes to the Zarr specification impact all implementors. In order to manage that burden, the Zarr project has formed an implementation council. Each implementation community selects one person to sit on the council to help shape changes to the Zarr spec.

Rights & Responsibilities

The hope is that sitting on the council is itself a minimal additional burden. Each decision to be made will be encapsulated as a "ZEP" (Zarr Enhancement Process) which will need to be voted on. Each community can state that they intend to actively implement ("YES") that they might eventually implement ("ABSTRAIN") or that they will never implement ("VETO").

Members of the Implementation Council will be added to the similarly named team on GitHub which has privileges on the zarr-specs and zep repos.

Next steps

First, if you would like to read more on the council and the process surrounding it, please see the Governance document as well as the ZEP itself for more information.

Then, please use this issue to let the steering council know either:

that you are not interested or perhaps do not have the capacity at this time
or whom you will be assigning as your council representative.

If any help or discussion is needed, feel free to do so here or link to other issues/threads as necessary.

Finally, we invite any implementation that has joined the Implementation Council to also host their implementation's repositories in the zarr-developers GitHub organization. This is not mandatory and has no impact on voting rights. Most importantly, we would like to show the vibrancy of the Zarr community and the strength that comes from a larger number of implementations.

Thanks to all of you!

If joining:
- [x] Create a dedicated core-devs team and assign all members
- [x] Add representative to the implementation-council team
- [x] Update GOVERNANCE.md
- [ ] Accept transfer of repository if desired

zarr-developers / governance