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

License is missing #11

Closed
jnnr opened this issue Sep 30, 2019 · 11 comments
Closed

License is missing #11

jnnr opened this issue Sep 30, 2019 · 11 comments
Assignees
Milestone

Comments

@jnnr
Copy link
Member

jnnr commented Sep 30, 2019

This repo needs a license. I suppose we take the same license as for most other repos in oemof, GPL-3.0?

@jnnr jnnr added this to the v0.0.1 milestone Sep 30, 2019
@p-snft
Copy link
Member

p-snft commented Sep 30, 2019

Pick the most permissive, every author agrees to. Re-licensing to a less permissive one is easy.

@uvchik
Copy link
Member

uvchik commented Oct 1, 2019

I would prefer MIT. See oemof/oemof#50.

@jnnr
Copy link
Member Author

jnnr commented Oct 5, 2019

I am ok with MIT.

@jnnr
Copy link
Member Author

jnnr commented Oct 5, 2019

@uvchik ✔️
@ckaldemeyer ✔️
@FranziPl
@jakob-wo ✔️
@jnnr ✔️
@Pyosch ✔️

[6] All
[5] MIT: @uvchik, @jnnr, @Pyosch, @ckaldemeyer, @jakob-wo

@uvchik
Copy link
Member

uvchik commented Oct 5, 2019

I edited the list and added @Pyosch because of the pending PR #7

@jakob-wo
Copy link
Contributor

jakob-wo commented Oct 7, 2019

Re-licensing to a less permissive one is easy.

Why is that?
I imagine it to be difficult to re-license a repo after having agreed on a permissive one. On one hand I expect heavy discussions if some contributers want a roll-back after some time. And on the other hand every one who starts including MIT-code now will be in trouble if later versions are released under a more restricted license. Don't you think so?

I am still not sure whether we should go along with MIT or GPL.

@p-snft
Copy link
Member

p-snft commented Oct 7, 2019

Re-licensing to a less permissive one is easy.

Why is that?

It is possible to license additional contributions to a MIT codebase under e.g. LGPL and then to (re)distribute the new collection (as a whole) under LGPL. However, a given license cannot be revoked. So, whoever got the MIT-Licensed code can continue to use it. A well-known example is Cedega: The software marketed a Software based on a MIT-licensed codebase without upstreaming the improvements. Consequently, the upstream project (Wine) changed to LGPL.

@uvchik
Copy link
Member

uvchik commented Oct 7, 2019

It is not allowed or at least a grey zone to use solph, feedinlib, windpowerlib in other programs that do have a more permissive licence than the GPLv3. Therefore it is not useful to have a restrictive licence in a basic library. The GPLv3 could be useful for program which is not intended to be integrated by others.

I is my goal that oemof can be used as easy as possible to create energy models and to publish these models under any licence and not only the GPLv3.

@p-snft
Copy link
Member

p-snft commented Oct 8, 2019

Adding to that: The Free Software Foundation, that authored the GPL, advices not to use it for libraries. Instead, they created the aforementioned LGPL, which allows free usage of the library (as a whole) also for e.g. MIT-licensed models. When you, @jakob-wo, dislike the idea that someone applies changes to oemof(-thermal) but does not grant the same freedoms as we do, the LGPL is what you want. However, while the use of oemof(-thermal) would be possible, this would still limit usability of oemof(-thermal) code fragments in other scientific projects.

@jakob-wo
Copy link
Contributor

Thank you both, @p-snft and @uvchik, for your statements and explanations.

I do support to license this repo under MIT.

@p-snft p-snft closed this as completed in 97eb8bf Oct 10, 2019
@p-snft
Copy link
Member

p-snft commented Oct 10, 2019

@FranziPl: I misinterpreted your consent in oemof/oemof#50 as one to thermal as well. I hope, this was Ok.

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

5 participants