Become a Contributor

Being a contributor means you get to work on the Terracotta source code. This is an excellent way to help us make the product even better, or to influence what types of features or bugs are worked on.

Read below to find out more about being a contributor.

How To Start

The basic steps to becoming a contributor or committer to Terracotta are as follows:

 

After that, there's a committer acceptance process that includes submitting the first few contributions as patches, then, based on those contributions, a community vote.

Contact Us if you would like more information on becoming a Terracotta contributor.

Contributor / Committer Agreements

After you get in touch with us, you'll be asked to sign and return one of:

Documentation

User Documentation
Developer Documentation

Source Repository

All information on accessing our source code is here:

Contribute Patches

Create the patches using svn or diff. Make sure that you turn on the -u option and that you give the patch a meaningful name. Diffs should be run from the top-level directory.

For example:

svn diff -x -u path/to/Foo.java > foo-fix.patch

or

diff -u Foo.java.orig path/to/Foo.java > foo-fix.patch

Then create an issue on the JIRA issue tracking system, provide a detailed description about what the patch does and add the patch file to the issue as an attachment. If you did not run the diff from the top-level directory, please specify what subdirectory you ran it from so the patch can be properly applied.

Community Code of Conduct

Principles:

  1. Always treat people involved in the project with respect.
  2. If you are a committer you are expected to show excellent judgement and communicate appropriately with the other developers before making changes.
  3. We encourage committers to strive for quality.
  4. New committers are expected to ease themselves in with small commits to start, and greater free-will may be assumed later.
  5. Terracotta encourages people to be brief in email and to honor internet etiquette.