The project welcomes contributions. JTS is a mature, widely-used library, so contributions will be reviewed carefully to ensure they do not compromise the quality of the codebase.
To start, it helps to announce what you are working on ahead of time to confirm that it is an acceptable contribution. To do this post to the JTS Mailing List.
The following sections outline workflows involved with contributions.
In order to have code contributions accepted, the submitter must:
- Sign the Eclipse Contributor Agreement (ECA) with the Eclipse Foundation. Use the registered email with the Git commits associated to the GitHub pull request.
Code contributions must include a license header at the top of each file. A sample header for Java files is here.
Code contributions should include the following:
- Javadoc on classes and methods
- Unit Tests to demonstrate code correctness and allow this to be maintained going forward. In the case of bug fixes the unit test should demonstrate the bug in the absence of the fix (if any). Unit Tests are usually JUnit classes, or in some cases may be JTS TestRunner test cases
- License information on all provided source files. An example license header can be found here.
The easiest and most visible way to make a contribution is to submit a Pull Request (PR) to the GitHub repo.
When preparing a PR please do the following:
-
Acknowledge that the code contribution is IP clean by 'signing off' the commits in the pull request with the '-s' option to 'git commit'.
-
Labeling the PR helps to track and prioritize the contribution. Use the following labels:
- The contribution type: enhancement, bug, api
- The module being contributed to: jts-core, jst-io, jts-app, jts-doc, jts-build
-
When a PR is submitted Travis CI will run to check the commiter Eclipse status and the build correctness.
Please check the PR status, and fix any reported problems
If you have questions about this, please ask on the jts-dev list.