...
Stuff to do to get a new committer set up
TODO: Rewrite for VIVO
- Add to the 'dspacevivo-commit@googlegroups.com' email list: https://groups.google.com/forum/#!forum/dspacevivo-commit
- (Needs to be done by Tim or a Committer who knows the 'dspace-commit' listserv admin pwd)Add to 'jira-developers' and 'dspacevivo-committer' groups so they can administer JIRA issues & Confluence Wiki pages: (Needs to be done by Tim Graham or send request to "sysadmin at duraspace dot org")
- Assign Add their GitHub username appropriate access to the VIVO Committers team in our DSpace GitHub Organization (Can be done by any Committer)
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 their username to both the "Owners" and "Committers" teams: https://github.com/organizations/DSpace/teams
- VIVO GitHub Organization
- Move them up to list of committers on DSpaceContributorsVIVO Committers (Can be done by any Committer)
- Announce (see template) to dspacevivo-community, dspace-devel, and dspacevivo-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)
...