EUPL compatibility

From TechnologicalWiki

EUPL

[edit] EUPL & GPLv2

If you consider to modify or dinamically link a code released under GPLv2 and include it on you project that will be released under EUPL, you should know that those licenses are NOT COMPATIBLE.

EUPL has a copyleft comparable to the GPL's. However, it allows recipients to distribute the work under the terms of other selected licenses, and some of those—the Mozilla Public License and the Common Public License in particular—only provide a weaker copyleft. Thus, developers can't rely on this license to provide a strong copyleft. The EUPL is incompatible with GPLv3, because recipients are not given permission to use GPLv3's terms, and the EUPL's copyleft conflicts with GPLv3's.

[edit] EUPL & GPLv3

If you consider to modify or dinamically link a code released under GPLv3 and include it on you project that will be released under EUPL, you should know that those licenses are NOT COMPATIBLE.

EUPL has a copyleft comparable to the GPL's. However, it allows recipients to distribute the work under the terms of other selected licenses, and some of those—the Mozilla Public License and the Common Public License in particular—only provide a weaker copyleft. Thus, developers can't rely on this license to provide a strong copyleft. The EUPL is incompatible with GPLv3, because recipients are not given permission to use GPLv3's terms, and the EUPL's copyleft conflicts with GPLv3's.

[edit] EUPL & LGPLv2

If you consider to modify a code released under LGPLv2 and include it on you project that will be released under EUPL, you should know that those licenses are NOT COMPATIBLE.

EUPL has a copyleft comparable to the GPL's. However, it allows recipients to distribute the work under the terms of other selected licenses, and some of those—the Mozilla Public License and the Common Public License in particular—only provide a weaker copyleft. Thus, developers can't rely on this license to provide a strong copyleft. The EUPL is incompatible with GPLv3, because recipients are not given permission to use GPLv3's terms, and the EUPL's copyleft conflicts with GPLv3's.

If you consider to dinamically link a code released under LGPLv2 with you project that will be released under EUPL, you should know that those licenses are COMPATIBLE.

[edit] EUPL & LGPLv3

If you consider to modify a code released under LGPLv3 and include it on you project that will be released under EUPL, you should know that those licenses are NOT COMPATIBLE.

EUPL has a copyleft comparable to the GPL's. However, it allows recipients to distribute the work under the terms of other selected licenses, and some of those—the Mozilla Public License and the Common Public License in particular—only provide a weaker copyleft. Thus, developers can't rely on this license to provide a strong copyleft. The EUPL is incompatible with GPLv3, because recipients are not given permission to use GPLv3's terms, and the EUPL's copyleft conflicts with GPLv3's.

If you consider to dinamically link a code released under LGPLv3 with you project that will be released under EUPL, you should know that those licenses are COMPATIBLE.

[edit] EUPL & EPL

If you consider to modify a code released under EPL and include it on you project that will be released under EUPL, you should know that those licenses are NOT COMPATIBLE.

Only the owner of software can decide whether and how to license it to others. Contributors to a Program licensed under the EPL understand that source code for the Program will be made available under the terms of the EPL. Unless you are the owner of the software or have received permission from the owner, you are not authorized to apply the terms of another license to the Program by including it in a program licensed under another Open Source license.

If you consider to dinamically link a code released under EPL with you project that will be released under EUPL, you should know that those licenses are COMPATIBLE.

The Eclipse Foundation interprets the term "derivative work" in a way that is consistent with the definition in the U.S. Copyright Act, as applicable to computer software. Therefore, linking to Eclipse code might or might not create a derivative work, depending on all of the other facts and circumstances.

[edit] EUPL & Apachev2

If you consider to modify or dinamically link a code released under Apachev2 and include it on you project that will be released under EUPL, you should know that those licenses are COMPATIBLE.

Software under several F/OSS licences can be combined with EUPL software. It is the case with all components that are licensed under licences that do not impose restrictions on future licensing (all the “permissive licences").