Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

This page provides notes on the DSpace SVN to GitHub Migration that took place in April/May 2012.  It has now all been completed.  The final announcement of this migrate is at: http://www.mail-archive.com/dspace-general@lists.sourceforge.net/msg01268.html

GitHub Migration Steps

Codebases to migrate to GitHub

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.

GitHub import hints

http://help.github.com/import-from-subversion/

Main Codebases

(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.

The below dependencies may no longer be needed, as it seems like we have a valid way to replace them in the future.

Additional Active DSpace projects

Mark: separate repo because they have separate releases cycles, though it might be time to put rest into the main DSpace repo.

Inactive projects (won't be moved to GitHub)

No Inactive Projects will be migrated to GitHub at this time

At this time, we do not plan to migrate any inactive projects to the central DSpace GitHub. Instead they will all be archived in a READ-ONLY SVN. They can always be migrated at a later time, as necessary.

Individual developers/committers are welcome to move any of these projects into their own personal GitHub account. They just won't be moved into the central DSpace GitHub.

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

Mark: Some of these can be considered for future, I want to take back those that I put considerable work into and will put these up in my repo or in our atmire repo. DSpace-imscp was an example of a crosswalk/packager addon, it could stand to be in the DSpace repo. Stats and discovery can remain behind.

Archive old SVN (for posterity)

  • (tick) Make existing SVN READ-ONLY
  • (tick) Archive the existing SVN (scm.dspace.org hosted by OSUOSL) to http://svn.duraspace.orgfor posterity.
  • (tick) Post a notice in the archived SVN (at svn.duraspace.org) that codebase is now at GitHub

Additional Cleanup tasks

  • (tick)Turn off any syncing between SVN and GitHub
    • Notify the Committers before making this change!!
  • (tick)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'
  • (tick)Ensure Maven Release Procedure still works - likely will require a POM update or two.

Mark: I've run a few releases via sonatype and github, it might be good to run a test release or two just to verify.  We just need to update the source management section of the maven parent Pom. I have examplespf these settings in my repo.

Final Steps

  • (tick) Notify community when development has moved completely to GitHub.
  • (tick)Redirect old SVN URLs:
    • (tick) Redirect scm.dspace.org to svn.duraspace.org (if possible, setup this redirect so that old URLs just go directly to that SVN archive)
  • (tick) Contact OSUOSL and let them know we no longer need to use the old SVN server.
  • (In process/ongoing) Build some "GitHub Best Practices" documentation @ Development with Git

Author File

The Author File provides a mapping of SVN users to GitHub users.

Format:

svnuser = gituser_full_name <gituser_email>
KevinVandeVelde = Kevin Van de Velde <kevin@mire.be>
ScottPhillips = Scott Phillips <scott@scottphillips.com>
StuartLewis = Stuart Lewis <stuart@stuartlewis.com>
ahkim = Austin Kim <ahkim@users.sourceforge.net>
aschweer = Andrea Schweer <schweer@waikato.ac.nz>
azeckoski = Aaron Zeckoski <azeckoski@gmail.com>
benbosman = Ben Bosman <ben@atmire.com>
bollini = Andrea Bollini <bollini@cilea.it>
bradmc = Brad McLean <bmclean@duraspace.org>
cjuergen = Claudia Juergen <claudia.juergen@tu-dortmund.de>
dchud = Dan Chudnov <daniel.chudnov@gmail.com>
dstuve = David Stuve <david.stuve@hp.com>
gam = Greg McClellan? <gam@users.sourceforge.net>
gam5 = Greg McClellan <gam5@users.sourceforge.net>
gcarpent = Grace Carpenter <gcarpent@users.sourceforge.net>
grahamtriggs = Graham Triggs <grahamtriggs@gmail.com>
jimdowning = Jim Downing <jim.downing@gmail.com>
jrutherford = James Rutherford <jrutherford@users.sourceforge.net>
jtrimble = Jeffrey Trimble <jatrimble@ysu.edu>
keithg = Keith Gilbertson <keith.gilbertson@library.gatech.edu>
kshepherd = Kim Shepherd <kim.shepherd@gmail.com>
lcs = Larry Stone <lcs@users.sourceforge.net>
mdiggory = Mark Diggory <mdiggory@atmire.com>
mirceag = Gabriela Mircea <gabriela.mircea@utoronto.ca>
mwoodiupui = Mark Wood <mwood@IUPUI.Edu>
pbreton = Peter Breton <pbreton@users.sourceforge.net>
peterdietz = Peter Dietz <dietz.72@osu.edu>
pottingerhj = Hardy Pottinger <pottingerhj@umsystem.edu>
pvillega = Pere Villega <pere.villega@gmail.com>
richard-jones = Richard Jones <richard@cottagelabs.com>
robintaylor = Robin Taylor <robin.taylor@ed.ac.uk>
rrodgers = Richard Rodgers <rrodgers@mit.edu>
rtansley = Robert Tansley <roberttansley@google.com>
sands = Sands Fish <sands@mit.edu>
scottphillips = Scott Phillips <scott@scottphillips.com>
stuartlewis = Stuart Lewis <stuart@stuartlewis.com>
syeadon = Scott Yeadon <scott.yeadon@anu.edu.au>
tdonohue = Tim Donohue <tdonohue@duraspace.org>
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.