-
Notifications
You must be signed in to change notification settings - Fork 0
ODD PI 26.3 Objective 2: 🌳 Evolve the Zarr Ecosystem #347
Copy link
Copy link
Closed
6 / 146 of 14 issues completedClosed
6 / 146 of 14 issues completed
Copy link
Labels
pi-26.3-objectiverepo:zarr-conventions/multiscalesrepo:zarr-conventions/projrepo:zarr-conventions/spatialrepo:zarr/geozarr-siterepo:zarr/geozarr-specrepo:zarr/geozarr-toolkitrepo:zarr/numcodecsrepo:zarr/zarr-bookrepo:zarr/zarr-developers.github.iorepo:zarr/zarr-extensionsrepo:zarr/zarr-pythonrepo:zarr/zarr-specs
Description
Activity
Metadata
Metadata
Assignees
Labels
pi-26.3-objectiverepo:zarr-conventions/multiscalesrepo:zarr-conventions/projrepo:zarr-conventions/spatialrepo:zarr/geozarr-siterepo:zarr/geozarr-specrepo:zarr/geozarr-toolkitrepo:zarr/numcodecsrepo:zarr/zarr-bookrepo:zarr/zarr-developers.github.iorepo:zarr/zarr-extensionsrepo:zarr/zarr-pythonrepo:zarr/zarr-specs
Motivation
We need to ensure a strong foundation for developers building tools on top of the Zarr format. Together, documenting the Zarr ecosystem and zarr-python roadmap will anchor zarr-python within the broader Zarr ecosystem.
Description
During this PI, we will evolve the Zarr ecosystem by:
To develop the roadmap, we will have:
We will also onboard a new team member to zarr-python work and mentor them towards becoming a zarr-python core developer. This will reduce the dependency on the 2 existing zarr-python developers for development and review to make progress on current features and roadmap featues.
Acceptance Criteria
Detailed in sub-issues:
LOE
1 FTE (for non-stretch tasks)
Dependencies
External dependency on zarr-python stakeholders
Related issues and PRs
zarr-developers/zarr-python#3925
developmentseed/datacube-guide#35
developmentseed/datacube-guide#30
pydata/xarray#11279