-
-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Place to list all zarr implementations in the docs. #585
Comments
In case it's helpful for you, feel free to reuse any of the code datasets in there. I would also not mind transfering ownership of this repository to the zarr organisation if anyone wants to build on this. |
@constantinpape : 👍 |
It would be very helpful to update the main Zarr docs with a link to the various implementations. |
@rabernat : agreed. NB: From the above, zarr_implementations has now been migrated to the org, and I think we're working toward having a generated page showing which features are implemented in each. |
Do we perhaps want to consider reorganizing our web presence more broadly. Perhaps a high-level landing page (e.g. zarr-format.org) that links out to the spec and the various implementation doc pages? |
Happy to help with this if there is interest. |
Great @manzt! Do we like zarr-format.org as the domain for the high-level page? If so I will buy it. |
Really unfortunate we can't get zarr.org. (The only other suggestion I have this evening is |
zarr.ar? 🙄 |
During today's call we mentioned a couple of zarr implementation, it would be good to have a place that list all of them (even incomplete) as well as version of zarr they support and languages written in, order to show that Zarr is not Python specific and avoid duplication of work.
We were pointed at https://github.com/constantinpape/zarr_implementations
But I think it would be nice to have that in the same main docs.
Having a number of test datasets of increasing complexity would also be good to test implementations.
The text was updated successfully, but these errors were encountered: