| layout | title | nav_order | description | permalink |
|---|---|---|---|---|
default |
home |
1 |
ZEP "A community feedback process for Zarr Specification" |
/ |
{: .fs-9}
Community Feedback Process for Zarr Specifications. {: .fs-6 .fw-300 }
Propose a new ZEP{: .btn .btn-primary .fs-5 .mb-4 .mb-md-0 .mr-2 } View it on GitHub{: .btn .fs-5 .mb-4 .mb-md-0 }
ZEP stands for Zarr Enhancement Proposal. A ZEP is a design document providing information to the Zarr community, describing a modification or enhancement of the Zarr specifications, a new feature for its processes or environment. The ZEP should provide specific proposed changes to the Zarr specification and a narrative rationale for the specification changes.
We intend ZEPs to be the primary mechanism for evolving the spec, collecting community input on major issues and documenting the design decision that has gone into Zarr.
We hold bi-weekly ZEPs meetings to propose, discuss, review and finalize discussions around current ZEPs and Zarr Specification. More info available here: https://zarr.dev/zeps/meetings/
If you wish to contribute to Zarr's codebase, propose a new ZEP(s), website, blog posts or in any way, please visit Zarr's GitHub here. You can discuss the change you want to see by opening an issue in the appropriate repository, or if the issue is already present, feel free to submit a pull request.
ZEPs are governed by Zarr Community's CODE OF CONDUCT.