Skip to content
This repository has been archived by the owner on Jul 13, 2022. It is now read-only.

Latest commit

 

History

History
42 lines (36 loc) · 2.31 KB

CONTRIBUTING.adoc

File metadata and controls

42 lines (36 loc) · 2.31 KB
Raw

Contributing to Eclipse Integration Commons

Eclipse Integration Commons is released under the Eclipse Public License 1.0 (EPL). If you would like to contribute something, or simply want to hack on the code this document should help you get started.

Code of Conduct

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to spring-code-of-conduct@pivotal.io.

Using GitHub issues

We use GitHub issues to track bugs and enhancements. If you have a general usage question please ask on Stack Overflow. The Spring Tools team and the broader community monitor the spring-tool-suite tag.

Sign the Contributor License Agreement

Before we accept a non-trivial patch or pull request we will need you to sign the Contributor License Agreement. Signing the contributor’s agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests.

Code Conventions and Housekeeping

None of these is essential for a pull request, but they will all help. They can also be added after the original pull request but before a merge.

  • Make sure all new source files to have a simple class comment with at least an @author tag identifying you, and preferably at least a paragraph on what the class is for.

  • Add the EPL license header comment to all new source files (copy from existing files in the project)

  • Add yourself as an @author to the source files that you modify substantially (more than cosmetic changes).

  • Add some docs.

  • A few unit tests would help a lot as well — someone has to do it.

  • If no-one else is using your branch, please rebase it against the current master (or other target branch in the main project).

  • When writing a commit message please follow these conventions, if you are fixing an existing issue please add Fixes gh-XXXX at the end of the commit message (where XXXX is the issue number).