Community

Affiliated projects.

Affiliated Software Projects are part of the Zarr Project under its NumFOCUS fiscal sponsorship. Each one governs itself through its own Core Developers Group and publishes its own governance document. This page is the official registry of affiliated projects.

SpecificationZarr Format Working Group →

Stewards the Zarr Format Specification and the Zarr Extensions Registry.

statusapproved

ImplementationZarr-Python →

The reference Python implementation of chunked, compressed, N-dimensional Zarr arrays.

statuspending

ToolNumcodecs →

Buffer compression and transformation codecs for Python, used by Zarr-Python.

statuspending

Implementationzarr-java →

A Java implementation of the Zarr Specification.

statuspending

ToolVirtualiZarr →

Create virtual Zarr stores that reference existing archival files, using Xarray syntax.

statuspending

ConventionsZarr Conventions →

Community-maintained, domain-agnostic metadata conventions layered on top of Zarr.

statuspending

Approved projects meet all affiliation criteria. Pending projects have been affiliated by the ZSC but are still publishing their governance document.

Becoming an affiliated project

Affiliation is described in the Zarr governance framework. Projects are considered against these criteria:

1. Be open source.
2. Be directly related to Zarr (e.g. an implementation, tool, extension, or convention).
3. Demonstrate a critical mass of sustained development activity.
4. Have a publicly documented governance process (adopting the default template is fine).

The process is:

1. Publish a governance document in your project's own repository. Adopting the default template as-is is fine. You can change it later without ZSC approval.
2. Request affiliation. Open an issue on the governance repository describing the project and linking to its governance document. The Zarr Steering Council (ZSC) votes on affiliation.
3. Add your card. Once affiliation is approved, open a PR adding your project to .vitepress/data/affiliated.ts, with links to its repository and documentation. One approval from a ZSC member is enough to merge.