Hi All,
Since we're now ready to migrate all of the remainder code to GitHub, two
questions have popped up.
1) Should we stick with the existing Github.com/dspace/dspace repository,
or should we reimport (a fresh git svn clone) so that we can use the author
mapping to make old commits point to a user's GitHub profile? By pushing
that change, it would make the current repo incompatible with anyone who
has forked it, as the reimport would have completely different commitID's.
2) What should we do about languages? We have
dspace-xmlui-lang<http://scm.dspace.org/svn/repo/modules/dspace-xmlui-lang/trunk/src/main/webapp/i18n/>
and
dspace-api-lang<http://scm.dspace.org/svn/repo/modules/dspace-api-lang/trunk/src/main/resources/>
I
don't imagine that people like having to manage two separate language
files. So would we want to consolidate that into a single project? If so,
anyone up to doing the work for that refactoring? Where would
messages/language extensions for modules fit?
Peter Dietz
On Thu, Mar 8, 2012 at 5:14 PM, Tim Donohue <tdono...@duraspace.org> wrote:
> Hello developers,
>
> By a unanimous decision on 'dspace-devel', the DSpace codebase will be
> moving to GitHub in the near future.
>
> By my tally, the results were:
>
> 20 developers/committers in favor of migrating (+1 vote)
> 0 developers/committers unsure about migrating (0 vote)
> 0 developers/committers against migrating (-1 vote)
>
> I will now be working with the Committer team to begin this migration
> process. The migration will likely happen in a series of stages in the
> coming weeks.
>
> I've started a wiki page to begin tracking the migration process:
> https://wiki.duraspace.org/display/DSPACE/Migration+to+GitHub
>
> (Others are encouraged to add to / enhance this page, as I'm sure there
> are things I've forgotten. Right now, just some initial steps are listed
> there)
>
> The vast majority of this migration process should happen "behind the
> scenes" (most developers won't notice anything until the end). But, once
> we get closer to completion, we will announce the date at which all
> development is now taking place on GitHub. We will also create some
> developer documentation around using the new DSpace GitHub.
>
> If anyone has any questions, or wants to help out in any way (especially
> with creating eventual DSpace GitHub documentation), please let us know!
>
> - Tim (on behalf of the Committers Team)
>
>
> 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-commit mailing list
> dspace-com...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-commit
>
------------------------------------------------------------------------------
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
