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

EPL licensing issues #328

Open
aschrijver opened this issue Aug 14, 2017 · 4 comments
Open

EPL licensing issues #328

aschrijver opened this issue Aug 14, 2017 · 4 comments

Comments

@aschrijver
Copy link

There are a couple of issues with the licensing of this project.

Most importantly there is the use of "All rights reserved" in combination with the Eclipse Public License (or any major open source license). While this term has become obsolete in terms of claiming copyright, it still has meaning that can conflict with the EPL license and lead to ambiguity.

This is best explained in this stackexchange answer: https://opensource.stackexchange.com/questions/2121/mit-license-and-all-rights-reserved

Conclusion of the article:

Stop Trying to Justify All rights reserved.

All rights reserved is a historic relic that is not relevant today for establishing copyright (the ownership part). In terms of licensing, it is detrimental to modern software licensing. The phrase has very specific, absolute meaning in the English language and can open up ambiguity in software licensing if it contradicts the rest of a license.

Personally, I suggest using the actual MIT License or my personal favorite, the ISC License, as is used by the OpenBSD project and others. All rights reserved should have never made it into a major open source license and rather than continuing its use, we need to break from the now-incorrect tradition.

Second, small issue, is that there should be a LICENSE file at root level.

I would be willing to go through the project files and code, fix the licensing issues and PR.

@matiwinnetou
Copy link
Contributor

Very possibly @irbull might have his hands tied here, this is IBM Open Source project so I would suspect he would need to escalate this. For IBM changing it's eclipse license could be possible but due to the size of the company may not happen tomorrow (if at all).

Nevertheless thanks for pointing things out, developers are not lawyers so generally there are many traps for us here.

@aschrijver
Copy link
Author

I can't imagine IBM wanting ambiguity, confusion with their license, unless it would be for nefarious reasons. "All rights reserved" does not belong in EPL.

But the article has an option for more commercial settings:

Commercial software often has phrases to the effect of "all rights reserved except as delineated below" to reserve all rights except those expressly provided in a license.

@irbull
Copy link
Member

irbull commented Aug 14, 2017

We considered (and sometimes still do) moving J2V8 to the Eclipse Foundation. That's the reason for the EPL. I also just used the standard copyright header that was used in other Eclipse projects for the same reason. I am happy to re-evaluate that, but I will need to get some outside council as I am not a lawyer.

@aschrijver
Copy link
Author

Like Vert.x did 😄
See #201 (comment)

I am also not a lawyer 👍

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

3 participants