Page History

...

Main Codebases

• Primary DSpace Codebase - Migrate (perform final sync) Main Trunk/Branches/Tags to https://github.com/DSpace/DSpace. REBUILD the "DSpace/DSpace" GitHub repository by performing the following steps:
  1. Rename the existing "DSpace/DSpace" GitHub repository to something like "DSpace/DSpace-pre-migration"
  2. Do a fresh migration of SVN to GitHub, with SVN author mapping using the #Author File below. This migration should happen to a BRAND NEW "DSpace/DSpace" GitHub repository
  3. Post a WARNING message to the "DSpace/DSpace-pre-migration" GitHub project. Everyone should migrate as-soon as possible to the new GitHub repo, as the old one will not be maintained any further.
  4. Once everyone has migrated (no more forks exist), we will delete the "DSpace/DSpace-pre-migration" repo
  WARNING - WILL NOT PERFORM AUTHOR MAPPING: At this time, we do not plan to perform the "SVN author mapping" (See #Author File) for this primary codebase. The reason why is that it can only be performed by essentially "destroying" the existing GitHub repository and rebuilding/recreating it. If we were to recreate this codebase, it would be detrimental to all people/institutions who have already forked it. Since "recreating this repository with author mappings" doesn't seem to give us much benefit in GitHub, the attendees of the Developers Meeting on March 14,2 012 decided it doesn't seem worth the hassle
  1. .
•  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.)
•  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.)

...