Subject: Exported From Confluence
Content-Type: text/html; charset=UTF-8
The Jikes RVM project aims to provide a high-quality state-of-th=
e-art open-source infrastructure for programming language research. Of cour=
se, this requires a significant investment in system maintenance and enhanc=
ement, to keep the system running on new environments and to keep up with t=
he latest innovations in language design and implementation practice.
Feedback and contributions from the research community are the indispens=
able, invaluable resource that will ensure the project's continued success.=
Please help to improve some aspect of the system; no improvement is too sm=
all or too simple! The more volunteers can contribute, the better the syste=
m will serve the research community, resulting in faster and more solid res=
earch results. It is also a great help to the community if you contribute y=
our code to the research archive<=
How can you help Jikes RVM?
Jikes RVM is a fairly large, complex, and perhaps intimidating system. H=
owever, there are many to-do items which don't require extensive Jikes RVM =
This page highlights a selection of low-hanging fruit for potential cont=
ributions. This list is of course nowhere near comprehensive, but exists ju=
st as a sampling of potential activities.
Note that most of the tasks on this page are related to code in some way=
or another: we currently do not have any tasks for people interested in ma=
rketing, translations or graphic design. If you think that the project woul=
d benefit from a contribution in this area (or any other area that is not n=
amed here), do not hesitate to contact us on the mailing lists.
Additional ideas that require code contributions are listed on a separate page.
All contributions to Jikes RVM are managed in our JIRA-based issue tracker.
Please let us know if the list below is out-of-date by entering a bug ag=
ainst the website.
ng fruit in no particular order
- Contribute sanity and performance tests: The system's =
test infrastructure is set up =
to test and run standard benchmarks and sanity tests in a uniform framework=
. This functionality helps foster reproducible performance results, and exe=
rcises the system nightly to shake out bugs. If you're adding new code to t=
he system, please consider contributing tests for it.
- Contribute unit tests: Support for unit tests was recently added to the Jikes RVM by=
João Reys Santos for Google Summer of Code 2012. There is an initia=
l set of tests but it is not very extensive. In the long term, we should ha=
ve a unit test for almost every class.
- Contribute missing sections or clarifications to the <=
strong>User Guide: If you =
run across some problem or area that is not well-documented in the User Guide, please write a short section f=
or inclusion. Also, please help us improve the installation section to cove=
r any installation problems you run into that are not documented. If you ar=
e interested in contributing to the User Guide, or to other pieces of onlin=
e documentation maintained in our wiki, we're quite willing to give you wri=
te access to the wiki pages. Please contact a Steering Committee member.
- Update the Publications=
a> and Dissertations pages: The lists of publications and dissertations are incom=
plete. You can inform members of the core team about missing publications o=
r contact a Steering Committee member to request wiki access so that you can edit the pages yourself.
- Improve Javadoc comments in system code: We realize th=
at the quality of Javadoc =E2=84=A2 comments is haphazard; please help us i=
- Confirm, triage or fix bugs: The issue tracker contain=
s a lot of open bugs. If a bug interests you, try to reproduce and fix it. =
If you can't fix the bug but can provide a test case that reliably reproduc=
es the bug, that is also very helpful. If you provide a fix, please conside=
r providing test cases for the bug. Patches with test cases require less ef=
fort from the commiters and will reach the mainline sooner.
- Review commits and patches: You can review commits (su=
bscribe to the commit mailing list=
a> to receive commit notifications) and patches on the issue tracker to imp=
rove code quality and catch bugs.