-
Notifications
You must be signed in to change notification settings - Fork 210
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
Request to dual license OSM scripts with MIT #971
Comments
Thanks @fneum for the issue, we'll notify that to the community and report here. |
As discussed during the developers meeting, it could make sense to re-license OSM-related part of PyPSA-Earth with a more liberal MIT license instead of the current AGPL to make possible re-using this part in PyPSA-Eur. To do so, we need consent of every contributor to relicense their code to MIT from the current AGPL, as has been done in #693 when re-licensing PyPSA-Earth (thanks @pz-max for establishing a way to do so!) to AGPL. We attach a list to this Issue such that every contributor is informed and can vote. Current contributors that needs to decide (please comment below with any of these emoji's) |
For me, both AGPL or MIT are ok 🏆 |
Also for me both are fine 🏆 |
Both are ok 🏆 |
Ok with both 🏆 |
2 similar comments
Ok with both 🏆 |
Ok with both 🏆 |
ok with APGL and MIT for {download,clean,build}_osm_data.py scripts 🏆 |
Ok with both🏆 |
Describe the feature you'd like to see
Please give a clear and concise description and provide context why the feature would be useful.
Also, we'd appreciate any implementation ideas and references you already have.
Dual licensing the scripts {download,clean,build}_osm_data.py with an MIT license would allow inbound use in MIT-licensed PyPSA-Eur.
https://fossa.com/blog/dual-licensing-models-explained/
The text was updated successfully, but these errors were encountered: