Message-ID: <404954227.33587.1408751834481.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_33586_1898094516.1408751834481" ------=_Part_33586_1898094516.1408751834481 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Jikes=E2=84=A2 RVM project is a collaborative software devel= opment project dedicated to providing an open source state-of-the-art infra= structure, freely available for performing research on virtual machine tech= nologies for the Java=E2=84=A2 programming language. This document describe= s the composition of the project and the roles and responsibilities of the = participants.
There are various roles people play in the Jikes RVM project. The more y= ou contribute, and the higher the quality of your contribution, the more re= sponsibility you can obtain.
Users are the people who use Jikes RVM, without contributing co= de or documentation to the project. Users are encouraged to participate thr= ough the mailing lists, asking questions, providing suggestions, and helpin= g other users. Users are also encouraged to report problems using the bug tracking system.= Anyone can be a user.
A user who contributes code o= r documentation becomes a contributor. Contributors are the people= who contribute enhancements, bug fixes, documentation, or other work that = is incorporated into the system. Anyone can be a contributor.
The most efficient way to make non-trivial contributions to the project'= s documentation (User Guide and other online material) is to edit the wiki = pages yourself. If you are interested in contributing in this fashion, plea= se contact one of the Steering Committee members to ask for edit permission= s to our wiki space.
A contributor who gives frequent and valuable contributions can be promo= ted to a Jikes RVM team member. Team members have write access to = the source code repository, and voting rights allowing them to affect the f= uture of the project. The members of the Jikes RVM team are responsible for= virtually all of the day-to-day technical decisions associated with the pr= oject. They are the gatekeepers, deciding what new code is added to the sys= tem. All contributions will be processed by one or more team members before= potential inclusion into the Mercurial repository.
A contributor can become a Jikes RVM team member by the following sequen= tial process:
Becoming a team member is a privilege that is earned by contributing and= showing good judgment. It is a responsibility that should be neither given= nor taken lightly. Active participation on the mailing lists is a responsi= bility of all team members, and is critical to the success of the project. = Team members are responsible for proactively reporting problems in the bug = tracking system, and annotating problem reports with status information, ex= planations, clarifications, or requests for more information from the submi= tter. The team also ensures that nightly regression tests are run on all su= pported platforms, monitors the results of the tests, and opens defects to = track regression test failures. A subset of the team does most of this moni= toring, however all team members are expected to investigate regression tes= t failures that might have been caused by a source code change they committ= ed.
At times, team members may go inactive for a variety of reasons. The pro= ject relies on active team members who respond to discussions in a construc= tive and timely manner. A team member that is disruptive, does not particip= ate actively, or has been inactive for an extended period may have his or h= er commit status removed by the Jikes RVM Steering Committee.
The Jikes RVM Steering Committee (SC) is a small group that is responsib= le for the strategic direction and success of the project. This governing a= nd advisory body is expected to ensure the project's welfare and guide its = overall direction.
The initial Jikes RVM SC was selected by the Jikes RVM team. Thereafter,= to become a member of the SC, an individual must be nominated by a member = of the SC, and unanimously approved by all SC members. The goal is to keep = the membership of the SC very small. In the unlikely event that a member of= the SC becomes disruptive to the process or ceases to contribute for an ex= tended period, the member may be removed by unanimous vote of remaining SC = members.