-
Notifications
You must be signed in to change notification settings - Fork 0
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
license considerations #1
Comments
Until we relicense there's no choice, has to be GPL, once we've relicensed I have no issues what license this should be. Indeed if we consider this to be "an example of how to use MDA", then it really should eventually become MIT or BSD so we don't accidentally block users from doing things. edit: obviously Cedric should have the real call on what the license should be here. |
Oh right, forgot about that! Is there an opened issue about this on the mdanalysis repo? Once the relicensing is done I don't really have a strong preference between MIT or BSD or Apache |
The code imports MDAnalysis
RDKitConverter-benchmark/scripts/utils.py
Lines 6 to 7 in 7cc1da5
Because MDAnalysis is currently licensed under GPL v2+, any code importing MDAnalysis inherits the copyleft. Therefore, the code cannot be licensed under MIT.
We are currently considering relicensing of MDAnalysis to a more permissive license but until this is done, at least my opinion is that at least the benchmark python code (anything that directly or indirectly imports MDAnalysis) should be GPL v2+.
@MDAnalysis/coredevs please feel free to chime in.
The text was updated successfully, but these errors were encountered: