-
Notifications
You must be signed in to change notification settings - Fork 13
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
Comments
Pick the most permissive, every author agrees to. Re-licensing to a less permissive one is easy. |
I would prefer MIT. See oemof/oemof#50. |
I am ok with MIT. |
Why is that? I am still not sure whether we should go along with MIT or GPL. |
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. |
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. |
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. |
@FranziPl: I misinterpreted your consent in oemof/oemof#50 as one to thermal as well. I hope, this was Ok. |
This repo needs a license. I suppose we take the same license as for most other repos in oemof, GPL-3.0?
The text was updated successfully, but these errors were encountered: