-
Notifications
You must be signed in to change notification settings - Fork 24
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
Finding an org for Zarr.jl #25
Comments
I think something can be said for each of JuliaIO, JuliaGeo and JuliaClimate. I'm happy with any of those. |
I agree with @visr here. The three org can be a natural choice fo this package. Having Zarr in JuliaClimate would be a major addition to the org, but it's up to you! I do not have experience with the format so I don't know if Zarr is mostly climate related or is it used widely elsewhere? Integrating Zarr format is definitely on my radar. |
FYI Zarr is being actively worked on in the bio-imaging community: https://forum.image.sc/t/next-generation-file-formats-for-bioimaging/31361/ |
👍 for Zarr.jl wherever it may live, and a heads up that some Outreachy applicants may be headed this way re: zarr-developers/zarr_implementations#42 |
I think JuliaIO would nake the most sense for this. |
Thanks for the suggestion @mkitti Yes, probably it is good to host the package in a place where not only geo-related people are assembled to also give a voice to people from Bio-Imaging and similar fields. So I would be open for moving the package there. |
Yes, I received the invite. Have you moved a Julia package before? I am not really sure about the steps needed to not mess up the registry. Do you have any suggestions, or is it as simple as hitting the "move repository" button in the package settings and Github redirects will do the rest... |
Welcome to JuliaIO, Zarr.jl! Can this issue be closed now that the transition is complete: |
In the discussion at JuliaClimate JuliaClimate/meta#1 it was suggested to move Zarr.jl to the JuliaClimate org and there were a few thumbs-ups for this. Do we see this as a consensus to move the package there? Or is additional discussion necessary. @visr @Balinus
The text was updated successfully, but these errors were encountered: