Zarr's governance structure is being updated (see blog post), and the changes will be formalized via ZEP-11. IMO these are great and helpful changes that essentially just try to clarify and simplify relationships and responsibilities.
Under the new structure, VirtualiZarr is considered a "Zarr Affiliated Software Project". There are governance requirements expected of an affiliated software project. There is a draft template for the governance requirements, and projects can tweak these themselves, but the blog post summarizes them as:
This governance initially consists of the following key elements:
- Each project has a group called the Core Developers Group (CDG) which makes decisions, e.g. about accepting PRs. (A group of one is fine for small projects.)
- Projects aim for consensus, falling back on majority vote of Core Developers when necessary.
- Any contributor is eligible to join the CDG. Existing Core Developers can nominate new members.
Nominations should be based on evidence of sustained, quality contribution to the project. Nominations are accepted by majority vote of existing Core Developers.
- Core Developers who become inactive can and should be removed, via a majority vote.
- Larger groups should have a chair, who acts as a facilitator / coordinator.
- Projects must adhere to the Zarr code of conduct, which is a requirement for NumFocus fiscal sponsorship.
VirtualiZarr essentially already does all this, but informally.
- We technically have a Core Developers Group (see our core team guide, but I'm not totally sure who's in it - I consider it to be mostly but not quite the same as the set of people who currently have merge access to this repo.
- We generally do things through discussion and consensus, though I don't think we've ever had to actually vote on anything.
- We do technically have a nomination process as part of our core team guide, though I don't think we've ever used it.
- Our chair has effectively been me, sometimes @maxrjones.
- We have a code of conduct - it's the Zarr one, and its listed in our contributing guide.
This issue is in case there is anything we have to do. Maybe nothing?
Zarr's governance structure is being updated (see blog post), and the changes will be formalized via ZEP-11. IMO these are great and helpful changes that essentially just try to clarify and simplify relationships and responsibilities.
Under the new structure, VirtualiZarr is considered a "Zarr Affiliated Software Project". There are governance requirements expected of an affiliated software project. There is a draft template for the governance requirements, and projects can tweak these themselves, but the blog post summarizes them as:
VirtualiZarr essentially already does all this, but informally.
This issue is in case there is anything we have to do. Maybe nothing?