Contributions
Contributing Documentation
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.
Contributing Code
If you have extended Jikes RVM and would like to contribute your extension back to the community, please use the patch tracker to submit a patch. When submitting a patch, please include the following:
- The patch file for your contribution
- The appropriate Statement of Origin
- A description of the functionality you are contributing
- The version of Jikes RVM used to create your patch
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.
Statement of origin
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
. 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