Hi All, A minor clarification on this GitHub vote. The Committers are holding this vote in a public forum (dspace-devel) so that community members (i.e. all of you) also have the opportunity to express your opinions.
So, whether you are a Committer or not, you are welcome to vote. This will help us to also gage community feedback for this possible codebase migration to GitHub. == A few notes on how a typical DSpace developer may be affected == As a DSpace developer, you may be directly affected by this migration if you currently checkout DSpace code from SVN. Obviously, should we migrate our codebase to GitHub, you will then need to checkout code via GitHub. If you still wish to use SVN locally, there will be ways you can continue to do so: * GitHub does have some basic SVN client support: https://github.com/blog/966-improved-subversion-client-support * Or, you could obviously download the Zipped up release packages and import them into your local SVN However, to receive some of the benefits of Git/GitHub (easier code sharing, ability to pull in others customizations or submit your customizations to DSpace), you may wish to also think about a local migration to Git/GitHub at some point. Obviously, should this migration to GitHub occur, the DSpace Committers & Developers will work on documenting some best practices for how individual developers may wish to fork the DSpace GitHub, manage your own local customizations, etc. So, please feel free to express your opinions of this possible migration to GitHub! - Tim On 2/29/2012 9:58 AM, Tim Donohue 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
