Policies on Adding New Committers
Committer Group Overview
The DSpace Committers Group – named because they are authorized to "commit" change to the code repository – have ultimate responsibility for the shape of the DSpace software, as well as its architecture and design going forward. They can apply code changes contributed by the larger DSpace development community to the open source platform.
A list of the current members of the committers group can be seen at DSpaceContributors
How to Nominate a new Committer
New committers may be nominated by anyone in the DSpace Community at anytime. You can even nominate yourself.
For more hints/tips on nominating someone (or yourself) for Committership, please see Committer Nominations
- Duration: 1 week or once an overall majority is achieved, whichever comes first
- Votes: 1 vote per current member
- Vote options: +1 = YES, -1 = NO, 0 = DON'T MIND
- Vote counting: For a vote to pass, there must be at least 3 '+1' votes, and more '+1' votes than '-1' votes.
The standard invitation email reads:
Stuff to do to get a new committer set up
- Add to the 'firstname.lastname@example.org' email list: https://groups.google.com/forum/#!forum/dspace-commit (Needs to be done by Tim or a Committer who knows the 'dspace-commit' listserv admin pwd)
- Add to 'jira-developers' and 'dspace-committer' groups so they can administer JIRA issues & Confluence Wiki pages: (Needs to be done by Tim or send request to "sysadmin at duraspace dot org")
- Assign their GitHub username "owner" access to our DSpace GitHub Organization and DSpace-Labs GitHub Organization (Can be done by any Committer)
- Add their username to the "Committers" teams: https://github.com/organizations/DSpace/teams
- Make sure the new committer is aware of the 'dspace-changelog' and 'dspace-tickets' listservs. It's a very useful way to keep in touch with changes in GitHub and JIRA respectively. (Can be done by any Committer)
- Add them to list of committers on DSpace Committers (Can be done by any Committer)
- Announce (see template) to dspace-community, dspace-devel, and dspace-tech email lists. If several committers are joining the group at once, consider sending one email for all, rather than separate emails. (Can be done by any Committer)
- Refer them to the Tips for New Committers (Though you should first double-check that content to ensure it is still up-to-date) (Can be done by any Committer)