Page History

...

To perform a release, you must have all of the following:

Write access to the DSpace subversion repository hosted at http://scm.dspace.org/svn/repo; This requires an administrator to add you to the svn repository permissions via the TRAC user group.
Write access to the org.dspace groupId in the snapshot and staging repositories hosted at oss.sonatype.org. If you don't already have this, you will need to:
- Sign up for a Sonatype JIRA account. This account will also serve as your login to the Sonatype OSS system
- Ask the previous release manager to request authorization for this account via the Sonatype JIRA system in the Open Source Project Repository Hosting project. Once Sonatype gives you the proper authorization, you should be able to login to the Sonatype OSS system using the same login/password you setup in Sonatype JIRA.
- The full details of signing up and getting access to Sonatype are also posted online here: Sonatype Maven Repository Usage Guide

...

You must generate and publish your own personal Code Signing Key (required by Sonatype). Here are two sites that give hints on how to do that:
- Creating a Code Signing Key
- How to Generate PGP Signatures with Maven (required for all Sonatype releases)
Write access to projects.dspace.org (which is where the DSpace Projects website is hosted)
- Ask the previous release manager for access to this server.
- Include your proposed username
- Include a local SSH Public Key (which will be used for authentication).

Here's notes from Mark Diggory on how to give someone else access to the OSUOSL server (projects.dspace.org):

adduser -m <user-name>
Add authorized key to ~/.ssh/authorizedkeys (make sure permissions are correct on file)

Add user to /etc/groups

Code Block
maven:x:4002:peterdietz,esm,mdiggory,tdonohue,ben,kim,apache

Make sure umask 002 is in the users ~/.bash_profile so maven permissions are written correctly.

Update Maven settings.xml

...