Gourt Home::Gourt :: Eclipse Public License
The Eclipse Public License (EPL) is a license for free software. Its primary use is for the Eclipse software development tools.
Free Software Foundation lists EPL as an approved license, but note that it is not compatible with the GNU General Public License.
EPL is an Open Source Initiative (OSI) approved license.
__TOC__
Reason the license was written
The Eclipse Foundation wrote the license. It is used for all projects which use Eclipse. Also, it can be used for the change or addition to the Eclipse such as plug-in programs to the Eclipse. The goal of this license is to make agreement from users who change, improve, use, reproduce or distribute the EPL-licensed program.
Compatibility with the GPL
The Eclipse Public License (EPL) is not compatible with the GPL. The Eclipse foundation migrated from the Common Public License (CPL) to the EPL. So, EPL is similar to the CPL and not the GPL. In fact, GPL requires that if anyone distributes, improves, adds to the software code which is under the GPL license, then they must offer the new or improved software only under the GPL license. Therefore, all changes and additions become a part of the GPL-licensed software. However, the CPL allows commercial vendors to offer CPL licensed software including changes and addition to the software under their own license, if the new license meets the requirements in the CPL license. EPL has originated from CPL, and EPL follows this concept of CPL. Therefore, EPL is not compatible with the GPL.
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.(1)
Covered works
The contributor may choose to distribute the changed program I object code form under its own license agreement. In addition, when the program is made available in source code form, it must be made available under the EPL agreement, and a copy of the agreement must be included with each copy of the program. (1)
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. (1)
Including a copy of the license
About 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. (1)
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)
Distribution under the license
The recipient of EPL-licensed program will receive a non-exclusive, worldwide, royalty-free license under Licensed Patents to reproduce, make, use, and sell the contribution of contributors. (1)
Later Versions
EPL does not state this topic, because, in my opinion, the developers who use EPL-licensed program can make their own license about their own improvements or changes in the future. Therefore, the EPL did not mention about this topic.
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: (2) - The Eclipse Foundation replaces IBM as the Agreement Steward in the EPL - The EPL patent clause is revised by deleting the sentence from the section 7 of the CPL
References
(1) Eclipse Public License –v 1.0 (2) CPL to EPL Transition Plan
Reviewed By: Heejoon Jung, Carnegie Mellon University
See also
External links
"Eclipse Public License"