Seeking to be a uPortal Committer
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 not formally adopted this rule, but it's as much of a rule as we've got.
~jayshao is the current point of contact for the logistics of creating a new committer, obtaining access to CVS, etc.
A new committer should:
- Be welcomed as a new committer on jasig-dev@
- Acquire jasig-dev@ list membership if he or she does not already have it.
- Introduce himself or herself to the jasig-dev@ list (again if previously introduced) in the context of a new committer
- Acquire JA-SIG source control box shell account (note this is no longer required when code moves into SVN)
- Acquire JA-SIG source control CVS account (parallel activity required under SVN)
- 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.)
+1 votes imply willingness to help, so while a new committer can look to the entire JA-SIG community for support in his or her new role, the existing committers who voted for the offer of committership should be especially available to assist.
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.