Page History
...
- 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' 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 by emailing send request to "sysadmin at duraspace .dot org")
- 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 rights in our SourceForge project)
- 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 Committer)
- Move them up to list of committers on DSpaceContributors (Can be done by any CommiterCommitter)
- 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) (Can be done by any Committer)
Overview
Content Tools