Have something to contribute? Get involved. Create patches for existing JIRA issues. Post new Jira issues. Answer questions on the list. Contribute to the wiki documentation. Demonstrate interest and having something to contribute.
Explain what it is that you would do for the project if you were a committer.
Adding New Committers
Offers of committership are extended by the existing uPortal committer community by vote on the email list for discussion of uPortal developers. Under apache tradition, 3 "+1" votes and more "+1" votes than committer vetoes are required for a committership vote to pass. The uPortal community has formally adopted this rule, but it's as much of a rule as we've got. While there is this voting process, there's a preference for operating by consensus: a present committer seeking to veto the granting of committership to a new committer would be a serious moment for discussion to understand the disagreement in expectations of readiness of the new committer for commiter responsibilities. It is by far preferable that the issue be resolved and new committership be granted by unanimous agreement than by a contested vote.
~jayshao is the current point of contact for the logistics of creating a new committer, obtaining access to SVN, etc.
A new committer should:
- Be welcomed as a new committer on jasig-dev@
- Acquire uportal-dev list membership if he or she does not already have it:
- Introduce himself or herself to the uportal-dev list (again if previously introduced) in the context of a new committer
- Acquire JA-SIG source control SVN account
- Update the list of uPortal committers in the wiki
- Be granted membership into groups in Jira and Confluence conferring the additional privileges necessary to efficiently work on the project (ability to assign, resolve, schedule Jira issues, e.g.)
In addition it is highly preferred for an existing committer to volunteer to mentor the initial contributions of the new committer to more easily spread existing conventions, culture, and context.