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

Add secondary licenses? #243

Closed
cmichelenstrofer opened this issue Nov 27, 2023 · 2 comments
Closed

Add secondary licenses? #243

cmichelenstrofer opened this issue Nov 27, 2023 · 2 comments

Comments

@cmichelenstrofer
Copy link

cmichelenstrofer commented Nov 27, 2023

Would you consider adding GPL v2.0 and higher as secondary licenses? It would require adding it to this section of the license:

"This Source Code may also be made available under the following
Secondary Licenses when the conditions for such availability set forth
in the Eclipse Public License, v. 2.0 are satisfied: {name license(s),
version(s), and exceptions or additional permissions here}
."

More info about the EPL secondary licenses clause here.

We want to use cyipopt in our GPL-3 licensed code.

Thanks!

@moorepants
Copy link
Collaborator

The copyright to the code contributed to the cyipopt repo belongs to each of the individual authors. When they contributed the code, they licensed it under EPL 1.0 (or more recently EPL 2.0). I changed the license of all the code to EPL 2.0 for the authors without their permission based on the the notice from Eclipse that this is allowed power the EPL 1.0 license, see #165. I don't think we can license the code under any other license, for example the GPL, without the consent of all authors of this software. I do not intend to pursue that consent. This wikipedia article https://en.wikipedia.org/wiki/Eclipse_Public_License seems to explain the incompatibility of GPL with EPL 1.0 and then a mechanism to opt into GPL compatibility in EPL 2.0 if authors consent.

@cmichelenstrofer
Copy link
Author

a mechanism to opt into GPL compatibility in EPL 2.0 if authors consent.

The mechanism is simply adding "GPL-2.0+" or similar to the current license where the place holder is. But yes, I believe that would require consent from all authors and I understand why you wouldn't want to pursue that.

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

2 participants