Versions Compared

Old Version 54

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 55

changes.mady.by.user Mark Diggory

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • (tick) Primary DSpace Codebase - The Offical DSpace/DSpace GitHub repository is now active! All DSpace development is now occurring in GitHub instead of SVN.
    1. The "DSpace/DSpace" GitHub is a BRAND NEW copy of SVN, with SVN author mapping using the #Author File below.
    2. WARNING: The old, "unofficial" "DSpace/DSpace" GitHub repository was renamed to DSpace-SVN-Deprecated
      • Anyone who had forked the "unofficial" GitHub migrate as-soon as possible to the new GitHub repo, as the old one will not be maintained any further.
      • Once everyone has migrated (no more forks exist), we will delete the "DSpace/DSpace-SVN-Deprecated" repo.
  • (tick)  dspace-api-lang - migrated to GitHub:DSpace/dspace-api-lang 
    • perhaps migrate to a single 'dspace-lang' GitHub project?  (Mark: I think move back into DSpace API and use minor releases to update languages.)
  • (tick)  dspace-xmlui-lang - migrated to GitHub:DSpace/dspace-xmlui-lang
    • perhaps migrate to a single 'dspace-lang' GitHub project? (Mark: I think move back into DSpace-xmlui and use minor releases to manage.)
  • (tick) dspace-services - migrated to GitHub:DSpace/dspace-services

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

  • (tick)  dspace-pom (parent POM of 'dspace-parent' & other DSpace maven projects) - migrate to a 'dspace-pom' GitHub project? (Mark: separate repo) - consolidated into Offical DSpace/DSpace GitHub repository
  • (tick)  The License/License Header files (used by 'dspace-pom') - This License/License Header may just need to be moved into the same location as 'dspace-pom' (as that is where it is used) ( mark: yes) consolidated into Offical DSpace/DSpace GitHub repository
  • (tick)  dspacedspace-assembly-plugin (used by 'dspace-parent' to assembly DSpace)- migrate to ??? (Mark: We started to shift to putting these assembly files into the parent src directory, maybe that's the best place and will eliminate the need for the plugin.) consolidated into Offical DSpace/DSpace GitHub repository

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

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.

...