The roles and responsibilities that people can assume in the project are based on merit. Everybody can help no matter what their role. Those who have been long term or valuable contributors to the project obtain the right to vote and commit directly to the source repository.
Users are the people who use the products of the Project. People in this role aren't contributing code, but they are using the products, reporting bugs, making feature requests, and such. This is by far the most important category of people as, without users, there is no reason for the Project.
When a user starts to contribute code or documentation patches, they become a Contributor.
Contributors are the people who write code or documentation patches or contribute positively to the project in other ways. A volunteer's contribution is always recognized. In source code, all volunteers who contribute to a source file may add their name to the list of authors for that file.
Contributors who give frequent and valuable contributions to a subproject of the Project can have their status promoted to that of a "Committer" for that subproject. A Committer has write access to the source code repository and gains voting rights allowing them to affect the future of the subproject.
In order for a Contributor to become a Committer, another Committer can nominate that Contributor or the Contributor can ask for it.
Once a Contributor is nominated, all of the Committers for a subproject will vote. If there are at least 3 positive votes and no negative votes, the Contributor is converted into a Committer and given write access to the source code repository for that subproject.
The first stage of the process is that the result of the vote thread should be
carbon copied to the pmc list by the existing committer who will be executing
the required process. An email should be sent to the prospected committer offering
them committership preferrable with the
This is an example offer letter:
Dear Contributor, The Jakarta project would like to offer you commit privileges. We have been impressed with your contributions up till now, and believe that your involvement will improve the quality of the libraries we produce. It is important that you realize that these commit privileges give you access to the specific Jakarta project repository for which you are involved with. They do not provide commit access to any other Apache based project. Those projects will have to grant you commit privileges themselves. If you are interested in having commit privileges, please just let us know, and we will setup an account on apache.org. It would expedite the process if you could provide your preferred account name and possibly a public SSH key. This process could take a few days once we get this information. We all hope that you accept this invitation. The Jakarta Project Management Committee.
Once a positive acknowledgement has been received, the new Committer should be sent an acknowledgement. This acknowledgement is a good time to ask for their preferred ASF user name. Here is an example acknowledgement letter.
Dear Committer, Thank you for accepting our invitation. If you have not already done so, please sure to submit the Contributor License Agreement to the Apache Software Foundation <http://www.apache.org/licenses/index.html#clas>. Once the Contributor License Agreement is submitted, please reply to me with the your preferred ASF login name. Please review the Newbie Committer FAQ <http://www.apache.org/dev/new-committers-guide.html> and the other materials on the website that describe your role as a Committer. We are honored that you have accepted our invitation and are sincerely grateful for your assistance. We look forward to working together. The Jakarta Project Management Committee.
Once the preferred ASF login name has been received from the new committer, and his or her Contributor License Agreement has been recorded by the Foundation, please follow the directions at the general Apache site for sending an email to initiate the account creation process on the infrastructure side. This may take a few days as infra is frequently swamped with tasks.
Please note that directions for related use-cases, such as an existing committer needing access to additional projects, are also available at the general Apache site.
Note 1: All Jakarta committers will be given access to the site module, located in the site subdirectory of the main Jakarta SVN tree. In other words, all Jakarta committers should be able to update the main Jakarta website.
Note 2: If the module that the committer needs access to is a sub module within a project (ie: turbine-tdk or avalon-logkit), it is up to the individual project to determine how to deal with giving out access. In other words, access may be granted by default to all sub modules or it can be granted by vote.
At times, Committers may go inactive for a variety of reasons. A Committer that has been inactive for 6 months or more may lose their status as a Committer. Getting access back is as simple as re-requesting it on the project's Developer mailing list.
A list of some of our current Committers can be found in our Project Credits.
Project Management Committee (PMC)Committers who frequently participate with valuable contributions may have their status promoted to that of a "Project Management Committee Member". This committee is the official managing body of the Jakarta Project and is responsible for setting overall project direction. In order to become a Member, someone on the PMC must nominate the Committer. The individual may then be approved with a 3/4 majority of the PMC.
To view the Project Management Committee bylaws, click here.
A list of our current PMC Members can be found in our Project Credits.