Page History

...

Stuff to do to get a new committer set up

Add to the 'dspace-commit' email list: https://lists.sourceforge.net/lists/admin/dspace-commit (Needs to be done by Tim or a Committer who knows the 'dspace-commit

...

' 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 by emailing "sysadmin at duraspace.org")
- https://jira.duraspace.org/secure/admin/user/BulkEditUserGroups!default.jspa?selectedGroupsStr=dspace-committer&selectedGroupsStr=jira-developers
Assign their GitHub username appropriate access to our DSpace GitHub Organization (Can be done by any Committer)
- Add their username to both the "Owners" and "Committers" teams: https://github.com/organizations/DSpace/teams
Add to SourceForge project members page (Subversion access = No, Shell Access = Yes, Release Tech = Yes, Tracker Manager: A) (Can be done by any Committer with Admin access in SourceForge)
- https://sourceforge.net/project/admin/project_membership.php?group_id=19984
Make sure the new committer is aware of the 'dspace-changelog' listserv. It's a very useful way to keep in touch with changes in GitHub.

...

...

(Can be done by any Commiter)
Announce (see template) to dspace-general, 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)

...