Why does the Eclipse Foundation redistribute some content under licenses other than the Eclipse Public License?
Sometimes the Project Management Committee (“PMC”) for an Eclipse Foundation project may make a decision to include some content from another open source project. If that content cannot be contributed to an Eclipse Foundation project under the Eclipse.org Terms of Use and the content is not already licensed under the CPL and/or EPL, the PMC may decide to use and redistribute the content under the terms and conditions of another license which would usually be the license that the content was received under. The Eclipse Foundation will only use non-CPL and/or non-EPL licensed content if the other license is an open source license approved by the Open Source Initiative and it permits commercial products to be built on the software without requiring any form of royalty or other payment. In some cases the Eclipse Foundation redistributes unmodified non-CPL and non-EPL content and in other cases it redistributes derivative works of non-CPL and non-EPL content. Unmodified non-CPL and non-EPL
Related Questions
- How will the Apache Public License and Eclipse Public Licenses affect "patent portfolio management" for software patents?
- Why is the Eclipse Public License used to license most of the content made available by the Eclipse Foundation?
- What other licenses (besides the Eclipse Public License) may be used by the Eclipse Foundation?