The basic governance of the Eclipse Foundation is laid out in the following
Eclipse Foundation Documents
The Bylaws lay out the basic rules of governance of the Eclipse Foundation.
- Membership Agreement:
The Membership Agreement describes
the rights and responsibilities for each class of member in the Eclipse
- Intellectual Property Policy:
The IP Policy describes the
policies and mechanisms that the Eclipse Foundation uses for accepting and
licensing the intellectual property developed by Eclipse projects.
- Anti-Trust Policy: The Anti-Trust Compliance Policy describes
the code of conduct required by all Eclipse Foundation Members to ensure
compliance with anti-trust laws.
- EPL (Eclipse Public License): The Eclipse Public License is the software license
used by all Eclipse projects. You can also read it in
- Development Process:
This document describes the fundamental rules for creating and governing
projects at the Eclipse community.
- Quick and Fun Process Prose:
A quick overview of the development and IP processes in cartoons and other forms.
Eclipse Board Directives and Resolutions
- Community Code of Conduct: The Eclipse community
has a culture that embraces and respects diversity.
- Third-Party Dependencies: This document contains
the guidelines for the review of third-party dependencies.
- Implementing the IP Policy:
This is a Board approved policy on how the EMO seeks Board approval for the use of open source
licenses, or can seek special approval for a third party component which has failed the normal
IP due diligence.
- Use of GPL+Classpath Exception by Eclipse Projects
This policy governs the use of prerequisites licensed under the GPL+Classpath Exception by
- Licensing Example Code:
This is a Board approved policy on how projects may license their example code.
- Standards and Specifications Policy:
This document describes how the Eclipse Foundation and Eclipse projects
interact with standards and specifications organizations.
- Project Requirements:
This document is a Board Resolution about the user interface and project data
guidelines for Eclipse projects.
- Using Proprietary Tools: This is a Board Resolution outlining
the policies and procedures for projects using proprietary tools in their development process.
- Project Usability:
This is a Board Resolution about requirements to improve project usability,
initial user experience, and extensibility.
- Usage of LGPL APIs in Eclipse Projects:
This is a Board approved policy on how Eclipse projects may make limited use of APIs
licensed under the LGPL.