Eclipse Committers play a very important role in the operation of the Eclipse Foundation open source projects. This document outlines the responsibilities and explains some of the basic concepts Eclipse Committers need to understand in their role as a committer. If you are an Eclipse Committer, should you have any questions after reading this document, your questions should be submitted to your [Project Management Committee](/projects/handbook/#roles-pmc)(PMC) or the [Eclipse Management Organization](/projects/handbook/#roles-emo)(EMO).
# Contributors and Committers {#contributors}
## Contributors and Committers {#contributors}
Anyone who makes contributions to the Eclipse Foundation website and to Eclipse Foundation projects are considered to be [Contributors](/projects/handbook/#contributing-contributors). These Contributors submit contributions such as code, documentation, and other materials which must be received as [Git commits](/projects/handbook/#resources-commit) (e.g., merge or pull requests) using infrastructure provided by the Eclipse Foundation.
...
...
@@ -33,19 +31,19 @@ Committers receive write-access to Eclipse Foundation [resources and services](/
Committers are usually contributors as well. In addition to incorporating and releasing content contributed by others, Committers may commit (often significant) contributions which they have developed themselves. Some Committers may never commit any content other than what they have authored themselves. Even though they may be more confident in the pedigree of their own contributions, they still need to ensure that their content is appropriate.
## How Content is Received {#content-received}
### How Content is Received {#content-received}
All content must be received as Git commits via infrastructure provided by the Eclipse Foundation. All content submitted through any channel other than the Eclipse Foundation infrastructure must be approved by the PMC, and submitted to the EMO for _IP due diligence review_ prior to being committed to the source code repository. It is highly recommended that each Committer review and understand Intellectual Property Management at the Eclipse Foundation and the Eclipse Foundation’s [IP Due Diligence Process](/projects/handbook/#ip) in particular.
## How Content is Distributed {#content-distributed}
### How Content is Distributed {#content-distributed}
Users and recipients of content distributed by the Eclipse Foundation are granted rights to the content by the declared project licence(s). The project licence(s) are described on the each project’s website, the [licence](/projects/handbook/#legaldoc-license) and [notice](/projects/handbook/#legaldoc-notice) files in the project’s software repositories, and in the [copyright headers](/projects/handbook/#ip-copyright-headers) of individual source files.
# Due Diligence Procedures {#procedures}
## Due Diligence Procedures {#procedures}
The Eclipse Foundation Project Handbook describes the [IP Due Diligence Process](/projects/handbook/#ip).
## Receiving contributions {#contributions}
### Receiving contributions {#contributions}
**IMPORTANT NOTE:** Committers should never accept a contribution received via a private communication such as email. It is important that all contributions are received through one of the channels described above to ensure that all necessary licences are granted and that there is a public, timestamped, and archived record of the submission.
...
...
@@ -58,7 +56,7 @@ Before accepting every contribution, the Committer must check the following:
It is the responsibility of the Committer to verify that there is a valid ECA on file for the author(s) of each contribution.
## Appropriateness of Contributions {#appropriateness}
### Appropriateness of Contributions {#appropriateness}
A Committer cannot always assume that contributed content can be freely used or redistributed. Committers are obligated to ensure the appropriate due diligence has been completed before incorporating and redistributing content received from others. The process for performing due diligence depends on whether the contribution is deemed to be a "significant" one. A "significant" contribution is a substantial amount of code or content that introduces major new functionality, or any code, module, or content which will be distributed under any licence other than the project licence(s).
...
...
@@ -72,7 +70,7 @@ If the contribution has any "legal" terms or conditions associated with it whats
Given the amount of time required to complete the due diligence process, the Committer should allow sufficient time for the appropriate review process to complete.
## Cryptography {#cryptography}
### Cryptography {#cryptography}
If the contribution is known or is believed to contain any type of encryption or decryption software, the contribution must be approved by the appropriate PMC before being utilised.
...
...
@@ -82,31 +80,31 @@ Any modifications, additions, or removal of cryptographic code, should be brough
Any Contributions containing Cryptography should have information regarding the Cryptography documented in [notices](/projects/handbook/#legaldoc-notice) for the source code repository and distribution forms that contain the Contribution. The Committer should work with the EMO to ensure the notices file has the appropriate documentation before the contribution is committed to the source code repository.
## Code Quality and Style {#quality}
### Code Quality and Style {#quality}
Each project may have its own standards for quality and style. However, any profanity found in the code or its comments are considered unacceptable and should be removed before the content is contributed. For more details on a specific project’s quality or style standards, please connect directly with the project team, or consult with the PMC.
## Legal Documentation {#legaldoc}
### Legal Documentation {#legaldoc}
It is very important that all content contains the correct legal documentation. Please read the [Legal Documentation Requirements](/projects/handbook/#legaldoc).
If you require assistance in preparing any of this documentation, contact your PMC or the EMO. All legal documentation should be approved by the EMO prior to committing the content.
## Third-Party Content {#third-party}
### Third-Party Content {#third-party}
There are cases where content redistributed at the Eclipse Foundation is not received as a contribution under the the project licence(s). The most common case is a Committer who wishes to redistribute content maintained by another open source project, outside of the Eclipse Foundation. Some examples of such packages currently being redistributed by the Eclipse Foundation are projects maintained by [The Apache Software Foundation](https://www.apache.org/), [Mozilla](https://www.mozilla.org/), [GTK+](https://www.gtk.org/), [JUnit](https://www.junit.org/), [JCraft](https://www.jcraft.com/), and others.
Before any such package can be redistributed by the Eclipse Foundation, the Committer must engage in the [IP Due Diligence Process for Third Party Content](/projects/handbook/#ip-third-party).
## Tracking Contributions {#tracking}
### Tracking Contributions {#tracking}
Tracking of each contribution within a project is very important from a legal point of view. As well, it allows for the appropriate acknowledgement of each contributor. This information about each contribution is typically maintained within [Git commit records](/projects/handbook/#resources-commit), and the standard [copyright headers](/projects/handbook/#ip-copyright-headers) contained within individual source files.
Each project team must take steps to ensure that intellectual property is [properly received](/projects/handbook/#resources-commit), so that it can be tracked.
# Summary {#summary}
## Summary {#summary}
To help support downstream adoption of Eclipse Foundation projects, it is a necessity to exercise the appropriate due diligence. In addition to these specific standards, the community relies on Committers to exercise their own judgment with respect to other factors that may deem the contribution to be inappropriate for use. If a Committer has doubts about the appropriateness of the contribution for any reason, then that Committer should investigate and consult with the applicable PMC, who will call on or direct you to EMO resources if necessary.
Wayne Beaton <wayne.beaton@eclipse-foundation.org>