| # Contributing to Eclipse Common Build Infrastructure |
| |
| Thanks for your interest in this project. |
| |
| ## Project description |
| |
| The Eclipse Common Build Infrastructure (CBI) combines technologies and |
| practices for building Eclipse Software. |
| |
| * https://projects.eclipse.org/projects/technology.cbi |
| |
| ## Developer resources |
| |
| Information regarding source code management, builds, coding standards, and |
| more. |
| |
| * https://projects.eclipse.org/projects/technology.cbi/developer |
| |
| This project uses *GitHub issues* on the respective repositories to track ongoing development and issues. |
| |
| Be sure to search for existing bugs before you create another one. Remember that |
| contributions are always welcome! |
| |
| ## Eclipse Development Process |
| |
| This Eclipse Foundation open project is governed by the Eclipse Foundation |
| Development Process and operates under the terms of the Eclipse IP Policy. |
| |
| ## Eclipse Contributor Agreement |
| |
| Before your contribution can be accepted by the project team contributors must |
| electronically sign the Eclipse Contributor Agreement (ECA). |
| |
| * http://www.eclipse.org/legal/ECA.php |
| |
| Commits that are provided by non-committers must have a **Signed-off-by** field in |
| the footer indicating that the author is aware of the terms by which the |
| contribution has been provided to the project. The non-committer must |
| additionally have an Eclipse Foundation account and must have a signed Eclipse |
| Contributor Agreement (ECA) on file. |
| |
| For more information, please see the Eclipse Committer Handbook: |
| https://www.eclipse.org/projects/handbook/#resources-commit |
| |
| ## Contact |
| |
| Contact the project developers via. |
| |
| * mailto:mtaal@elver.org |
