Eclipse Public License

From Wikipedia, the free encyclopedia

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).

 

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.^[1]

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.^[2] 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 ^[3] Richard Stallman and Eben Moglen from the Free Software Foundation have stated repeatedly^[4][5] 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.

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. ^[6]

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. ^[6]

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.^[6]

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.^[1]

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.^[1]

Other Relevant Aspects

The significant difference between the GPL and EPL is that EPL allows the developers to make their own license for 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, ^[7] 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

References

1. ^ ^{a b c} Eclipse Public License - v 1.0. Retrieved on 2006-09-12.
2. ^ Various Licenses and Comments about Them. Retrieved on 2006-09-20.
3. ^ GPLv3 Process Definition. Retrieved on 2006-09-20.
4. ^ Eben Moglen speaking at the GPLv3 launch, January 16th 2006. Retrieved on 2006-09-20.
5. ^ Transcript of Richard Stallman at the 3nd international GPLv3 conference; 22nd June 2006 - Q2: What might GPLv3 be compatible with?. Retrieved on 2006-09-20.
6. ^ ^{a b c} Eclipse Public License (EPL) Frequently Asked Questions. Retrieved on 2006-09-12.
7. ^ CPL to EPL Transition Plan (2006-09-12).

---

See also

• Free software licenses

External links

• The Eclipse Public License, version 1.0
• Eclipse Public License FAQ
• FSF's license list
• EPL on OSI