Page History

...

Stuff to do to get a new committer set up

•  Add to the 'dspace-commitcommit@googlegroups.com' email list:  https://listsgroups.sourceforgegoogle.netcom/listsforum/admin#!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")
  
  • 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 DSpace SourceForge "Admin" group  (Can be done by any Committer with Admin rights in our SourceForge project)
  
  • https://sourceforge.net/p/dspace/admin/groups/
•  Make sure the new committer is aware of the 'dspace-changelog' listserv' 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)
•  Move them up to list of committers on DSpaceContributors  (Can be done by any Committer)
•  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)