Message-ID: <1946158395.407.1425300270820.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_406_1201439127.1425300270820" ------=_Part_406_1201439127.1425300270820 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
If you want to help us improve our User Guide and other online documenta= tion, please contact a Steering Committee Member and ask for editing permis= sions for our wiki space.
If you have extended Jikes RVM and would like to contribute your extensi= on back to the community, please use the patch tracker to submit your contribution. Pl= ease 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 c= ertified open source license. If your contribution is included in the syste= m, you will be acknowledged on the contributors web page, along with getting the satisfaction of making t= he world a better place.
You should make it easy for members of the Jikes RVM team to merge your = code contribution.
At minimum, you must do the following:
The Jikes RVM team will check for those points.
You can do the following things to further increase the chances that you= r contribution will be merged:
Write useful commit messages. Use the first sentence to give a summa= ry of the issue. If you are fixing a JIRA issue, please mention it in the d= escription.=20
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 ens=
ures that your patch can always be applied easily. You can use
g export to create patch files from your commits.
If you contribute your changes in the form of mercurial bundles, you mus=
t make sure that the parent changeset of your first changeset is in the mai=
n repository. If it is not,
hg unbundle will fail and you=
r bundles cannot be imported.
All contributions must include one of the Statements of Origin below. In= sert your name(s) in the first blank(s) and a high-level summary in the bla= nk in a (i) . Examples of a high-level summary are "Fixed bug in sched= uler", "Extended type propagation in optimizing compiler", o= r "Added new garbage collector".
If your contribution is owned by your employer, someone authorized by yo= ur employer to make such a decision must add a comment to the patch in the = tracker stating that you have permission to contribute it.