Skip to content
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

Transfer this package back from JuliaGeo to meggart #197

Open
meggart opened this issue Jan 3, 2025 · 8 comments
Open

Transfer this package back from JuliaGeo to meggart #197

meggart opened this issue Jan 3, 2025 · 8 comments

Comments

@meggart
Copy link
Member

meggart commented Jan 3, 2025

I think the only remaining reason for users wanting to use this package instead of NCDatasets.jl was the DiskArrays.jl support. Since DiskArrays has arrived now in NCDatasets, I think it would be good to give NetCDF.jl a bit less visibility by removing it from JuliaGeo.

Are there any opinions/objections? @rafaqz @visr

@visr
Copy link
Member

visr commented Jan 6, 2025

I'd be fine with this. What's most important in my opinion is a clear message on top of the readme that indicates the status of the package. We could also archive it here, just like https://github.com/JuliaGeo?q=&type=archived?

@Alexander-Barth it's been a while, but would you still be interested in moving NCDatasets into JuliaGeo like you mentioned in JuliaGeo/NCDatasets.jl#57 (comment)?

@Alexander-Barth
Copy link
Member

This is surprising, but yes I would be fine with that :-)
I would like to also improve the integration of DiskArrays in particular, making the CFVariables a subtype of DiskArrays as mentioned by @rafaqz (help either in form of PR or just explanation is always welcome).

@meggart
Copy link
Member Author

meggart commented Jan 7, 2025

I'd be fine with this. What's most important in my opinion is a clear message on top of the readme that indicates the status of the package. We could also archive it here, just like https://github.com/JuliaGeo?q=&type=archived?

Yes, a message explaining the status of the package is a good idea. I just don't have the time and energy to actively work on it and to reply to bug reports/feature requests of users in due time, which is what I would clarify in the message.

Regarding archiving the package, a large part of my personal code base still depends on NetCDF.jl and I might want to apply some changes in the future so I don't think I want to completely stop development of the package, I just think that especially new users coming to JuliaGeo are better off using NCDatasets.jl with more features (CF stuff), more accessible documentation etc.

So I am fine with both, either having both NetCDF.jl and NCDatasets.jl in JuliaGeo with a message in the Readme that advises people to use the latter or to move NetCDF.jl to some other namespace and have only a single NetCDF package here.

@visr
Copy link
Member

visr commented Jan 7, 2025

Yeah then it makes sense to not archive it. Your call on what you prefer. I'm also fine with leaving it here indicating it as superseded by NCDatasets.

@Alexander-Barth
Copy link
Member

Here is it: https://github.com/JuliaGeo/NCDatasets.jl

@rafaqz
Copy link
Member

rafaqz commented Jan 7, 2025

I think this is a really good development for clarity to users and new contributors

@visr
Copy link
Member

visr commented Jan 7, 2025

I put a PR up to update the URL of NCDatasets in the registry: JuliaRegistries/General#122548
NetCDF would also need it if it moved. Nothing breaks without it though since GitHub redirects.

@meggart
Copy link
Member Author

meggart commented Jan 8, 2025

I made a PR to add a notice in the NetCDF.jl readme, feel free to suggest a different text if you like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants