Current Situation

Where does each project publish?

Project	Snapshots (groupId)	Third Party Libraries (groupId)	Releases (groupId)
Akubra	fc-snapshots (org.akubraproject)	-	fc-releases (org.akubraproject)
DSpace	dspace-snapshots (org.dspace) [4]	dspace-repo (org.dspace) [4]	dspace-repo (org.dspace) [4]
DuraCloud	-	fc-thirdparty (org.duracloud)	-
Fedora	-	fc-thirdparty (org.fcrepo) fc-releases (org.fcrepo) [1]	fc-releases (org.fcrepo)
Mulgara	-	-	-
Topaz	topaz-repo (org.topazproject)	topaz-repo ([2])	topaz-repo (org.topazproject)

[1] Currently, libraries that are "third party" to the FCRepo project are split between the fc-thirdparty repository (for libs authored by projects outside DuraSpace) and the fc-releases repository (for libs authored by other DuraSpace projects). The current FCRepo groupId/artifactId naming convention is further documented here.

[2] The Topaz project has historically put all third-party libs under separate groupIds within their repository.

[4] DSpace release artifacts are not exposed via local dspace-repo, all release builds use the central repo at http://repo1.maven.org/maven2/org/dspace/ unless the developer configures maven to behave differently. All third party requirements not already in the central repo or other popular repository such as java.net or codehaus (excluding oracle JDBC drivers) are published under the org.dspace groupId so they will be properly rynced to the central repository after release.

Repository details

Repository	Hosted At	Browsable?	Write Access?	GroupIds Published to Central	Repository Platform	Deployment
dspace-repo	OSU OSL	Yes	Manually granted by mdiggory	org.dspace , org.duraspace [3], org.fedora-commons [3]	Apache HTTPD Filesystem, WEB-DAV can be made available	SCP Wagon
dspace-snapshots	OSU OSL	Yes	"	None	"	"
fc-releases	Cornell	Yes	Manually granted by cwilper	None
fc-snapshots	Cornell	Yes	"	None
fc-thirdparty	Cornell	Yes	"	None
topaz-repo	PLoS	Yes	Manually granted by Ronald?	None

[3] These groupIds are not used. Generally, groupIds of projects within DuraSpace are tied to the project, not the overarching organization. Also, the Fedora Repository project has now standardized on using org.fcrepo as its groupId. (MRD: I agree)

What Repository Platform might be utilized

Currently OSL is working on implementing java based services for deploying webapplication driven services. At this time they are not announcing any timeline for this.

What Merged Repositories Might Look Like

Repository	Hosted At	Browsable?	Write Access?	Published to Central?
duraspace-repo	OSU OSL	Yes	Granted by admin(s) for each project, under that project's groupId	Yes
duraspace-snapshots	OSU OSL	Yes	"	No

Participating Projects:

Should:

Comply with central requirements; all artifacts published by each project (third-party or not):
1. Need to be under the groupId of the project responsible for authoring/publishing the POM.
2. Need to be freely distributable.
Designate admin(s) who can delegate write access to the portion of the repository under that project's control.