Page History

...

Main

...

Codebases

• Primary DSpace Codebase - Migrate (perform final sync) Main Trunk/Branches/Tags to https://github.com/DSpace/DSpace  (Make sure that sync include mapping to github authors (see below) where possible)
•  dspace-api-lang - migrated to GitHub:DSpace/dspace-api-lang
  • perhaps migrate to a single 'dspace-lang' GitHub project?
•  dspace-xmlui-lang - migrated to GitHub:DSpace/dspace-xmlui-lang
  • perhaps migrate to a single 'dspace-lang' GitHub project?
• dspace-services - migrate to ???

Dependencies of Primary Codebase

• The "Licenses" repository - This License/License Header may just need to be moved into https://github.com/DSpace/DSpace somewhere?

The following codebases are also standalone. Do we want to keep them that way? (i.e. do they all merit their own repository in GitHub)?

• dspace-services - migrate to 'dspace-services' GitHub Projectdspace-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 ???

Dependency Codebases

The following codebases are strictly releases of DSpace dependencies. Some of these dependencies just needed to be pushed to Maven Central (i.e. we don't "own" any of the code – all we did was release it to Maven Central because we needed it available there). Others need minor tweaks for DSpace.

Question: Should we just combine all of these into a single 'dspace-dependences' GitHub project? Is there a reason to maintain these as separate repositories?

• dspace-solr (dependency of 'modules/solr') - migrate to 'dspace-dependencies' GitHub project???
• 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/), which is used for PPT text extraction (but also looks to work for Word docs)?
• 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???

...

Additional Active

...

DSpace projects

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

Inactive projects (won't be moved to GitHub)

Projects that seem to be "inactive" at this time include:

• DSpace 2.0 SVN codebase (This is the code from the 2009 DSpace 2.0 prototype)
• Modules directly related to the 2.0 Prototype, including:
  • The 'dspace-storage' modules and all "storage-*" modules listed at: http://scm.dspace.org/svn/repo/modules/^{Image Added}
• All Sandbox projects at: http://scm.dspace.org/svn/repo/sandbox/^{Image Added}
• All old DSpace Maven Tools at: http://scm.dspace.org/svn/repo/tools/maven/^{Image Added} (EXCEPT the 'dspace-assembly-plugin' which is listed above)
• The following 'demo/experimental' modules:
  • dspace-core module
  • dspace-database module
  • Old copy of 'dspace-discovery' at: http://scm.dspace.org/svn/repo/modules/dspace-discovery/^{Image Added}
  • dspace-imscp module
  • dspace-schedule module
  • Old copy of 'dspace-stats' at: http://scm.dspace.org/svn/repo/modules/dspace-stats/^{Image Added}
  • dspace-sync module
• Any other SVN projects we haven't explicitly listed in another section as one we are planning to move to GitHub.

Archive old SVN (for posterity)

...