+1 for moving DSpace development to GitHub

--
HARDY POTTINGER <pottinge...@umsystem.edu>
University of Missouri Library Systems
http://lso.umsystem.edu/~pottingerhj/
https://MOspace.umsystem.edu/
"And remember, also" added the Princesss of Sweet Rhyme, "that many places
you would like to see are just off the Map and many things you want to
know are just out of sight or a little beyond your reach. But someday
you'll reach them after all, for what you learn today, for no reason at
all, will help you discover all the wonderful secrets of tomorrow."

--Norton Juster, The Phantom Tollbooth






On 2/29/12 9:58 AM, "Tim Donohue" <tdono...@duraspace.org> wrote:

>Hi All,
>
>As I've previously stated, today we are opening the vote for whether
>DSpace should move its codebase from SVN to GitHub. More information on
>what this means is below (see "What does this Migration to GitHub Mean?"
>section)
>
>You may vote by responding to this email thread with one of the following:
>
>+1  = I vote to migrate to GitHub
>0   = I'm neutral (I don't really care one way or the other)
>-1  = I'd rather DSpace codebase stay on SVN
>
>Based on our Voting for Procedural/Policy Changes, this vote will pass
>if we receive more positive (+1) than negative (-1) votes.
>https://wiki.duraspace.org/display/DSPACE/Developer+Voting+Procedures
>
>VOTING WILL BE OPEN FOR ONE WEEK, UNTIL 20:00UTC ON WEDNESDAY, MARCH 7.
>
>
>= What Does this Migration to GitHub Mean? =
>
>Essentially, if we vote to migrate the DSpace Codebase to GitHub, the
>following changes will occur:
>
>1. All DSpace projects/modules/codebases that are still in active
>development will be migrated to https://github.com/DSpace/
>
>2. The existing SVN codebases will be "archived" and made READ-ONLY (no
>more changes or future releases will occur in SVN).  This SVN archive
>will likely also be moved to: https://svn.duraspace.org/  (we can setup
>a redirect such that scm.dspace.org will redirect to the archived
>location).
>
>3. All future development, releases (tags) & branches will occur in the
>DSpace GitHub projects. This means that any active DSpace developers
>will need to begin using this codebase instead of SVN.
>
>--------------------------------------------------------------------------
>----
>Virtualization & Cloud Management Using Capacity Planning
>Cloud computing makes use of virtualization - but cloud computing
>also focuses on allowing computing to be delivered as a service.
>http://www.accelacomm.com/jaw/sfnl/114/51521223/
>_______________________________________________
>Dspace-devel mailing list
>Dspace-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/dspace-devel


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to