| [Edit]
The Eclipse Public License (EPL) is a free software/open source license with weak copyleft approved by both the Free Software Foundation (FSF) and the Open Source Initiative (OSI).
__TOC__
top
Introduction
The Eclipse Public License is a business friendly free software license used by the Eclipse Foundation for its software. It replaces the Common Public License (CPL) and removes certain terms relating to patent litigation. Similar to other free software licenses the receiver of EPL-licensed programs can use, modify, copy and distribute the work and the modified versions.•
top
Compatibility with the GNU Public License (GPL)
The EPL 1.0 is not compatible with the GPL v2 and earlier due to additional restrictions concerning patent retaliation found in the EPL.• Such restrictions are not valid from the viewpoint of the GPL v2 to protect the freedoms of the users (even to sue somebody for patent infringement) and thus it is not possible to take software licensed under the EPL 1.0 and include it in a project licensed under the GPL v2.
The reverse case is also not allowed: It is not possible to take software licensed under the GPL v2 and include it in a combined work licensed under the EPL 1.0 since the GPL v2 has a strong copyleft clause you are not allowed to remove but which the EPL does not have.
During the drafting process of the GPL version 3 • Richard Stallman and Eben Moglen from the Free Software Foundation have stated repeatedly•• that compatibility with the Apache Software Foundation's software license and the Eclipse Public license will be one of the goals of the new version of the GPL, so it might be possible to combine EPL and GPL software in the future.
top
Derivative works
EPL allows the developers of changes and additions of EPL-licensed code to
make their own license under any type of license they choose about the changes and additions separately. However, the EPL-licensed part of their derivative software product should be licensed under EPL license, but the developers can have private right about the portions of changes and additions. •
top
Charging money for the programs under the license
In EPL, the contributor can charge money for programs which the contributor changed and added to the program. Also, there are no restrictions on providing source code. The contributor can make, use, sell, offer to sell, import and transfer the contribution.
top
Including a copy of the license
The EPL-licensed portions of the derivative software product must be licensed under a EPL-license, but the improvements and additions could be written separately as their own license.
top
Adding to the license
If we add or change some portions to the Eclipse, we can make our own license to the added or changed portions under the condition of EPL, and distribute with payments, but they should inform the available location about source code which are licensed under EPL.
top
Later Versions
If a new version of the EPL is published the user/contributor can choose to distribute the software under the version he received it with or upgrade to the new version.
top
Other Relevant Aspects
The significant difference between the GPL and EPL is that EPL allows the developers make their own license about the portions of their improvements or additions separately from the EPL-licensed code, if the EPL-licensed portions of their derivative software product are licensed under the EPL license agreements. In other words, the developers can keep the improvements or additions as proprietary. In addition, EPL was based on the CPL, • but there are some differences between the two licenses as followings:
The Eclipse Foundation replaces IBM as the Agreement Steward in the EPL
The EPL patent clause is revised by deleting the sentence from section 7 of the CPL
top
See also
|
|
