content/legal/cpl2epl/faq/_index.md

+---
+title: CPL To EPL Transition Plan Frequently Asked Questions
+author: Mike Milinkovich
+is_deprecated: true
+keywords:
+  - cpl
+  - epl
+  - license
+  - transition
+  - faq
+---
+
+## For informational purposes only
+
+This FAQ provides answers to commonly asked questions related to the transition of Eclipse projects from the [Common Public License version 1.0](http://www.ibm.com/developerworks/library/os-cpl.html) to the [Eclipse Public License (EPL)](/org/documents/epl-v10.php). Details can be found in the [CPL to EPL Transition Plan](/legal/cpl2epl/cpl2epl-transition-plan.pdf) (.pdf).
+
+This FAQ is provided for informational purposes only. It is not part of, nor does it modify, amend, or supplement the terms of the CPL or EPL. The CPL and EPL are legal agreements that govern the rights granted to material licensed under it, so please read them carefully. This FAQ should not be regarded as legal advice. If you need legal advice, you must contact your own lawyer. This document was last updated on August 26, 2004.
+
+1. **Why is the Eclipse Foundation changing licenses?**  
+    The EPL was written specifically for the [Eclipse Foundation](/org/). First, it changes the Agreement Steward, formerly IBM for the CPL, to now be the Eclipse Foundation for the EPL. Second, it addresses concerns that some Eclipse Foundation members had with a clause in the CPL that deals with possible patent litigation. Many members and prospective members had concerns with this clause, and viewed it as overly broad. For more information on this please refer to the [EPL FAQ](/legal/epl/faq/).
+2. **Can you summarize the plan briefly?**  
+    The plan is to license the current release of each Eclipse project, together with any maintenance updates, under both the CPL and EPL for approximately 6-8 months. This transition period will be roughly aligned with major releases of the Eclipse Platform. This will give the community adequate time to adjust to the changes.
+  
+3. **What if a project can’t meet the timelines in the plan?**  
+    If any projects find the timeframes to be impractical or feel the plan imposes an unreasonable burden for other reasons, they should request an exception to the plan from the EMO. The EMO is prepared to work with projects, and with the Eclipse community generally, to mitigate the impact of the license transition process.
+  
+4. **How will inbound contributions be handled?**  
+    Under the plan, the [Web Site Terms of Use](/legal/terms-of-use/) will be changed to specify that by default, inbound contributions will be contributed under both EPL and CPL during the transition period. This is necessary to support dual licensed maintenance streams of current releases.
+  
+5. **What if I want to contribute code under only the EPL or CPL to a dual licensed stream?**  
+    Contributions under a single license will be possible but not encouraged and will be handled as special cases (similar to the process currently used by the PMCs and EMO to deal with third party code contributed under a license other than the CPL). Approval requires a strong technical argument for including the code, explaining what the functionality is, why it is needed, and why other options that fit the dual license framework are infeasible.
+  
+6. **What about previous releases like Eclipse Platform 2.x?**  
+    Past release streams that were licensed under CPL only and are still in use (e.g. Eclipse 2.x), will continue to be supported as CPL only.
+  
+7. **Will new development streams be dual licensed also?**  
+    No, all new development streams going forward (e.g. Eclipse 3.1) will operate under EPL only.
+  
+8. **When will the re-licensing process be completed and the transition period end?**  
+    This is a two-stage process, with two important dates. The plan for the re-licensing process is for it to be completed for all projects by December 31 2004. By that date, and for every project, CPL only development will cease, the current release will be offered under dual license, and new development will be EPL only. At some **switchover date** (currently expected to be in 1H05), all Eclipse development (including maintenance) will move to EPL only. The exact date of the switchover will depend on individual project schedules.
+  
+9. **When will we see EPL versions of major Eclipse projects?**  
+    For now, major projects will prepare dual licensed releases. The Eclipse Foundation will be contacting all contributors to obtain their agreement to publish under both EPL and CPL.
+  
+10. **What is the Re-Licensing Committee?**  
+    The Eclipse Foundation Board of Directors has created a committee called the Re-Licensing Committee to monitor the progress of the transition.
+  
+11. **I am a committer and I received an email asking me to identify contributors whose code I committed. Why am I getting this?**  
+    Contributors to an Eclipse project provided their contribution under the CPL. We are seeking their agreement to dual license their contribution under both the CPL and EPL. To facilitate this process Eclipse is asking all committers to identify the contributors they personally know about. We would like to get their contact information (employer, address, etc.), and also would like to know what they worked on and roughly how much code they contributed. All of this will help us to first, decide exactly who needs to be contacted and second, collect the required agreements.
+  
+12. **What is the Eclipse Foundation going to do with the personal data it is collecting?**  
+    We intend to build a contributor database so that in future we can do a better job of managing and recognizing contributions.
+  
+13. **What is an "individual committer"?**  
+    Most committers working on Eclipse projects currently are employed by an Eclipse Member Organization, and are working on Eclipse in the course of their regular employment. Individual committers are those who fall outside this category. If the individual committer personally owns his/her contributions, then he/she may simply agree to re-contribute under the EPL. If some other entity owns the contribution, such as their employer, then he/she must obtain the permission of that entity to re-license the contribution.
+  
+14. **Once all the required agreements are obtained, what options does a project have to actually implement the re-licensing for projects/builds that will be licensed under the EPL?**  
+    The Eclipse Foundation is currently suggesting projects use one of two options. Option #1 is to modify **all files including source files** to change all legal notices, abouts, feature licenses, feature update licenses, and the Software User Agreement, to refer to "EPL"; rather than "CPL" but only for those projects/builds that will be licensed under the EPL.  For those projects/builds that will be licensed under the CPL, no changes are required. Option #2 is similar to Option #1 except **source files will NOT BE UPDATED**. This means that the CVS repository and source builds for the stream will contain source files with effectively "incorrect" license notices that will be "overridden" by the Abouts, Software User Agreement and other legal documentation. The use of this mechanism and the status of each project will be well publicized and documented on the website
+  
+15. **What if I’m still confused about what my options are with respect to the re-licensing process?**  
+    Contact your PMC Lead or the EMO, they will help you sort things out.
+  
+16. **What if a project can’t get this all done by the December 31 deadline?**  
+    The Re-Licensing Committee has the authority to approve exceptions to the plan, on the recommendation of the EMO, that would allow a project more time. The criteria for considering an exception are: the size of the project; cost to completely change all source files; project schedules; available resources; and impact on the Eclipse community.

content/legal/cpl2epl/notice/_index.md

+---
+title: Eclipse.org Software User Agreement
+author: Mike Milinkovich
+is_deprecated: true
+keywords:
+  - legal
+  - about
+related:
+  links:
+    - text: CPL Software User Agreement in plain HTML
+      url: notice.html
+    - text: CPL to EPL conversion
+      url: /legal/cpl2epl
+    - text: Guide to legal documents
+      url: /projects/handbook/#legaldoc
+---
+
+ECLIPSE.ORG MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT"). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.
+
+### Applicable Licenses
+
+Unless otherwise indicated, all Content made available by Eclipse.org is provided to you under the terms and conditions of the Common Public License Version 1.0 ("CPL"). A copy of the CPL is provided with this Content and is also available at [http://www.eclipse.org/legal/cpl-v10.html](/legal/cpl/cpl-v10.html). For purposes of the CPL, "Program" will mean the Content.
+
+Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse.org CVS repository ("Repository") in CVS modules ("Modules") and made available as downloadable archives ("Downloads").
+
+Content may be apportioned into plug-ins ("Plug-ins"), plug-in fragments ("Fragments"), and features ("Features"). A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Files named "feature.xml" may contain a list of the names and version numbers of the Plug-ins and/or Fragments associated with a Feature. Plug-ins and Fragments are located in directories named "plugins" and Features are located in directories named "features".
+
+Features may also include other Features ("Included Features"). Files named "feature.xml" may contain a list of the names and version numbers of Included Features.
+
+The terms and conditions governing Plug-ins and Fragments should be contained in files named "about.html" ("Abouts"). The terms and conditions governing Features and Included Features should be contained in files named "license.html" ("Feature Licenses"). Abouts and Feature Licenses may be located in any directory of a Download or Module including, but not limited to the following locations:
+
+* The top-level (root) directory
+* Plug-in and Fragment directories
+* Subdirectories of the directory named "src" of certain Plug-ins
+* Feature directories
+
+Note: if a Feature made available by Eclipse.org is installed using the Eclipse Update Manager, you must agree to a license ("Feature Update License") during the installation process. If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or inform you where you can locate them. Feature Update Licenses may be found in the "license" property of files named "feature.properties". Such Abouts, Feature Licenses and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in that directory.
+
+THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER TO THE CPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):
+
+* Eclipse Public License Version 1.0 (available at [http://www.eclipse.org/legal/epl/epl-v10.html](/legal/epl/epl-v10.html))
+* Apache Software License 1.1 (available at [http://www.apache.org/licenses/LICENSE](http://www.apache.org/licenses/LICENSE))
+* Apache Software License 2.0 (available at [http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0))
+* IBM Public License 1.0 (available at [http://www-128.ibm.com/developerworks/opensource/library/os-ipl.html](http://www-128.ibm.com/developerworks/opensource/library/os-ipl.html))
+* Metro Link Public License 1.00 (available at [http://www.opengroup.org/openmotif/supporters/metrolink/license.html](http://www.opengroup.org/openmotif/supporters/metrolink/license.html))
+* Mozilla Public License Version 1.1 (available at [http://www.mozilla.org/MPL/MPL-1.1.html](http://www.mozilla.org/MPL/MPL-1.1.html))
+
+IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License or Feature Update License is provided, please contact Eclipse.org to determine what terms and conditions govern that particular Content.
+
+### Cryptography
+
+Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check the countrys laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted.

content/legal/dco/index.md

+---
+title: Developer Certificate of Origin
+author: Mike Milinkovich
+hide_page_title: true
+keywords:
+  - certificate
+  - Developer Certificate of Origin
+  - contributor
+  - legal
+  - eclipse
+related:
+  links:
+    - text: Eclipse Contributor Agreement [[html](/legal/eca/eca.html)]
+      url: /legal/eca
+    - text: ECA FAQ
+      url: /legal/eca/faq
+    - text: Developer Certificate of Origin [[html](/legal/dco/dco.html)]
+      url: /legal/dco
+    - text: Legal resources
+      url: /legal
+    - text: Guide to legal documents
+      url: /projects/handbook#legaldoc
+    - text: Committer Resources
+      url: /legal#Committers
+    - text: Contributing via git
+      url: http://wiki.eclipse.org/Development_Resources/Contributing_via_Git
+  content: |
+    <p>
+      To complete and submit a ECA, log into the <a href="/contribute/cla/">Eclipse projects forge</a> (you will need to create an account with the Eclipse Foundation if you have not already done so); click on "Eclipse Contributor Agreement"; and Complete the form. Be sure to use the same email address when you register for the account that you intend to use when you commit to Git.
+    </p>
+---
+
+{{< pages/legal/inject-content >}}

content/legal/eca/_index.md

+---
+title: "Eclipse Contributor Agreement"
+author: Mike Milinkovich
+layout: single
+hide_page_title: true
+keywords:
+    - certificate
+    - ECA
+    - contributor
+    - legal
+    - eclipse
+related:
+  links:
+    - text: Eclipse Contributor Agreement [[html](/legal/eca/eca.html)]
+      url: /legal/eca
+    - text: ECA FAQ
+      url: /legal/eca/faq
+    - text: Developer Certificate of Origin [[html](/legal/dco/dco.html)]
+      url: /legal/dco
+    - text: Legal resources
+      url: /legal
+    - text: Guide to legal documents
+      url: /projects/handbook#legaldoc
+    - text: Committer Resources
+      url: /legal#Committers
+    - text: Contributing via git
+      url: http://wiki.eclipse.org/Development_Resources/Contributing_via_Git
+  content: |
+    <p>
+      To complete and submit a ECA, log into the <a href="/contribute/cla/">Eclipse projects forge</a> (you will need to create an account with the Eclipse Foundation if you have not already done so); click on "Eclipse Contributor Agreement"; and Complete the form. Be sure to use the same email address when you register for the account that you intend to use when you commit to Git.
+    </p>
+---
+
+{{< pages/legal/inject-content >}}

content/legal/eca/faq/_index.md

+---
+title: Eclipse Contributor Agreement (ECA) FAQ
+author: Mike Milinkovich
+keywords:
+  - legal
+  - documents
+  - about
+  - contributor
+  - license
+  - agreement
+  - IP
+  - intellectual property
+  - ECA
+---
+
+{{< pages/legal/eca-faq >}}

content/legal/eclipse-foundation-quality-verification-suite-license/index.md

+---
+title: Eclipse Foundation Quality Verification Suite License - v 1.0
+author: Eclipse Foundation
+keywords:
+  - legal
+  - documents
+  - license
+  - quality verification
+---
+
+{{< pages/legal/eclipse-foundation-quality-verification-suite-license >}}

content/legal/efsl-1.1/index.md

+---
+title: Eclipse Foundation Specification License
+author: Eclipse Foundation
+keywords:
+    - legal
+    - Eclipse Foundation Specification License
+---
+
+**Do not modify the text of this license.**
+
+Specification project committers: include this text _verbatim_ in your specification document.
+
+An AsciiDoc version of this file is available [here](/legal/adoc/efsl-1.1.adoc). Plain HTML is [here](efsl.html).
+
+The Eclipse Foundation TCK License is [here](/legal/tck).
+
+↓ The actual licence text starts below this line. ↓
+
+***
+
+{{< pages/legal/inject-content >}}

content/legal/efsl/index.md

+---
+title: Eclipse Foundation Specification License
+author: Eclipse Foundation
+keywords:
+    - legal
+    - Eclipse Foundation Specification License
+---
+
+**Do not modify the text of this license.**
+
+Specification project committers: include this text _verbatim_ in your specification document.
+
+An AsciiDoc version of this file is available [here](/legal/adoc/efsl-2.0.adoc). Plain HTML is [here](efsl.html).
+
+The Eclipse Foundation Specification License version 1.1 is available [here](/legal/efsl-1.1).
+
+The Eclipse Foundation TCK License is [here](/legal/tck).
+
+↓ The actual licence text starts below this line. ↓
+
+***
+
+{{< pages/legal/inject-content >}}

content/legal/efsp-non-assert/index.md

+---
+title: Specification Non Assertion Covenant
+author: Wayne Beaton
+keywords:
+    - specifications
+    - non assert
+---
+
+April 13, 2020
+
+To the extent you submit or otherwise make available to an Eclipse Foundation Specification Project (as that term is defined by the Eclipse Intellectual Property Policy) any ideas, concepts, methods or other information, you agree that you will not assert, based on such submissions, any intellectual property rights that are essential to any implementation of the submission, against the Eclipse Foundation, its contributors, or its licensees, with respect to any implementation of such Specification (as that term is defined by the Eclipse Foundation Specification Process).
+To further clarify, such submissions include, but are not limited to, submissions made to any public communications channel such as an email list, forum, bug report, or GitHub issue submissions.

content/legal/epl-2.0/_index.md

+---
+title: Eclipse Public License 2.0 (EPL)
+layout: single
+author: Wayne Beaton
+hide_page_title: true
+keywords:
+  - epl
+  - epl-2.0
+  - legal
+  - foundation
+  - eclipse
+  - eclipse public license
+  - license
+  - licenses
+---
+
+{{< pages/legal/inject-content >}}

content/legal/epl-2.0/faq/_index.md

+---
+title: EPL-2.0 FAQ
+author: Wayne Beaton
+hide_page_title: true
+keywords:
+  - epl
+  - epl-2.0
+  - faq
+  - legal
+  - foundation
+  - eclipse
+  - eclipse public license
+  - license
+  - licenses
+---
+
+{{< pages/legal/inject-content >}}

content/legal/epl/about-file-templates/index.md

+---
+title: About File Templates
+author: Wayne Beaton
+keywords:
+  - about
+  - legal
+  - foundation
+page_css_file: public/css/legal/about-file-templates.css
+related:
+  links:
+    - text: EPL-2.0 - `about.html` in plain HTML
+      url: epl-2-about.html
+    - text: EPL-2.0 - Third-Party Content `about.html` in plain HTML
+      url: epl-2-longabout.html
+    - text: EPL-2.0 - Legal Documentation for Eclipse Platform Plug-ins and Fragments under the EPL-2.0
+      url: /projects/handbook/#legaldoc-plugins
+    - text: EPL-1.0 - `about.html` in plain HTML
+      url: epl-1-about.html
+    - text: EPL-1.0 - Third-Party Content `about.html` in plain HTML
+      url: epl-1-longabout.html
+    - text: EPL-1.0 - Legal Documentation for Eclipse Platform Plug-ins and Fragments under the EPL-2.0
+      url: /projects/handbook/#legaldoc-plugins
+---
+
+{{< pages/legal/about-file-templates >}}

content/legal/epl/faq/index.md

+---
+title: Eclipse Public License 1.0 (EPL) Frequently Asked Questions
+author: Mike Milinkovich
+keywords:
+  - epl
+  - cpl
+  - faq
+  - legal
+  - foundation
+  - eclipse
+  - license
+  - licenses
+related:
+  links:
+    - text: Eclipse Legal FAQ
+      url: /legal/faq
+    - text: Eclipse Software User Agreement
+      url: /legal/epl/notice
+---
+
+{{< pages/legal/epl-faq >}}

content/legal/epl/notice/index.md

+---
+title: Eclipse Foundation Software User Agreement
+author: Mike Milinkovich
+hide_page_title: true
+keywords:
+  - eclipse
+  - license
+  - user
+  - agreement
+  - sua
+related:
+  links:
+    - text: Software User Agreement in plain HTML
+      url: notice.html
+    - text: Software User Agreement in Java properties format
+      url: feature.properties.txt
+    - text: Guide to legal documents
+      url: http://www.eclipse.org/projects/handbook/#legaldoc
+---
+
+{{< pages/legal/inject-content >}}

content/legal/faq/index.md

+---
+title: "Eclipse Foundation Legal Frequently Asked Questions (FAQ)"
+author: Mike Milinkovich
+layout: single
+hide_page_title: true
+keywords:
+    - legal
+    - faq
+    - foundation
+---
+
+{{< pages/legal/inject-content >}}