If you want to help us improve our User Guide and other online documentation, please contact a Steering Committee Member and ask for editing permissions for our wiki space.
If you have extended Jikes RVM and would like to contribute your extension back to the community, please use the patch tracker to submit your contribution. Please include the following:
Your contribution will be licensed under the EPL (Eclipse Public License), the license used for Jikes RVM. The license has been approved by the OSI (Open Source Initiative) as a fully certified open source license. If your contribution is included in the system, you will be acknowledged on the contributors web page, along with getting the satisfaction of making the world a better place.
At minimum, you must do the following before submitting your code contribution:
The Jikes RVM team will check for those points. You will make it easier to merge your contribution if you ensure that there are no problems in that regard.
You can do the following things to increase the chances that your contribution will be merged:
Write useful commit messages. Use the first sentence to give a summary of the issue. If you are fixing a JIRA issue, please mention it in the description.
RVM-XXXX : Fixed a bug in foo.
Longer description of the change, the reasons for the change and the consequences. This part can span multiple paragraphs and is optional: you will need to decide what's important for people looking at the commit.
Consider providing a README if your chosen patch format does not support commit messages.
Patches should apply against a revision of the main repository. This ensures that your patch can always be applied easily. You can use
hg export to create patch files from your commits.
If you contribute your changes in the form of mercurial bundles, you must make sure that the parent changeset of your first changeset is in the main repository. If it is not,
hg unbundle will fail and your bundles cannot be imported.
All contributions must include one of the Statements of Origin below. Insert your name(s) in the first blank(s) and a high-level summary in the blank in a (i) . Examples of a high-level summary are "Fixed bug in scheduler", "Extended type propagation in optimizing compiler", or "Added new garbage collector".
If your contribution is owned by your employer, someone authorized by your employer to make such a decision must add a comment to the patch in the tracker stating that you have permission to contribute it.
Statement of Origin: Single Contributor Single Contributor for all Contributions Multiple Contributors