Page History

...

At this time, we will only migrate codebases which are currently under active development (we can always move others later on, as we will keep an archive of SVN). If any are missing from the below list, feel free to add them.

Main Codebase(s)

• Primary Codebase - Migrate (perform final sync) Main Trunk/Branches/Tags to https://github.com/DSpace/DSpace
• dspace-api-lang - perhaps migrate to a single 'dspace-lang' GitHub project?
• dspace-xmlui-lang - perhaps migrate to a single 'dspace-lang' GitHub project?
• dspace-services - migrate to ???

Dependencies of Primary Codebase

• dspace-solr (dependency of 'modules/solr') - migrate to ???
• dspace-pom (parent POM of 'dspace-parent' & other DSpace maven projects) - migrate to a 'dspace-pom' GitHub project?
• dspace-assembly-plugin (used by 'dspace-parent' to assembly DSpace) - migrate to ???
• dspace-geoip (dependency of 'dspace-stats') - migrate to a general 'dspace-dependencies' GitHub project???
• dspace-tm-extractors (used by dspace-api to do text extraction of Word docs?) - Can we just replace this with POI (http://poi.apache.org/)?^{Image Added}
• dspace-jmockit (dependency of dspace-parent) - migrate to a general 'dspace-dependencies' GitHub project???
• dspace-cocoon-servlet-service-impl (dependency of dspace-xmlui-wing) - migrate to a general 'dspace-dependencies' GitHub project???

Other Active Projects

• dspace-replicate - Already migrated to https://github.com/DSpace/dspace-replicate
• dspace-rest - Already migrated to https://github.com/DSpace/dspace-rest

...

• The existing SVN (hosted by OSUOSL) will be archived to http://svn.duraspace.org and made READ-ONLY.
• Redirect scm.dspace.org to svn.duraspace.org (or similar)
• Post a notice in the archived SVN (at svn.duraspace.org) that codebase is now at GitHub
• Contact OSUOSL and let them know we no longer need that SVN server.

Additional Cleanup tasks

• Turn off any syncing between SVN and GitHub
  • Notify the Committers before making this change!!
• Ensure Maven 'License Header' check still works when running 'mvn install' (this is setup in 'dspace-pom')
  • Likely will need to move LICENSE_HEADER to GitHub, maybe into same project as 'dspace-pom'?
  • Also will likely require a new release of 'dspace-pom'
• Ensure Maven Release Procedure still works - likely will require a POM update or two.

Final Steps

• Notify community when development has moved completely to GitHub.
• Build some "GitHub Best Practices" documentation:
• Need to also update Tracking your source code with Git