pypsa-meets-earth/pypsa-earth

Request to dual license OSM scripts with MIT

fneum opened this issue Β· 10 comments

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/

Thanks @fneum for the issue, we'll notify that to the community and report here.
I'm clearly totally fine with it for what concerns my contributions

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)
Ok with both AGPL or MIT πŸ†, Ok with only AGPL 🦺, Ok with MIT Ⓜ️.
@GbotemiB πŸ†
@pz-max πŸ†
@DeniseGiub
@virio-andreyana πŸ†
@davide-f πŸ†
@Ekaterina-Vo
@pitmonticone πŸ†
@carlosfv92 πŸ†
@ekatef πŸ†
@Tomkourou πŸ†
@mnm-matin

For me, both AGPL or MIT are ok πŸ†

Also for me both are fine πŸ†

Both are ok πŸ†

Ok with both πŸ†

Ok with both πŸ†

Ok with both πŸ†

ok with APGL and MIT for {download,clean,build}_osm_data.py scripts πŸ†

Ok with bothπŸ†