Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
MIME-Version: 1.0
In-Reply-To: <011a01d04786$6eefe670$4ccfb350$@acm.org>
References: 
 <CAK2iWdTZdQgzZQvB6qtuyjo+=3KnEG9mzcjS1YAwT4pbfdYr3w@mail.gmail.com>
	<011a01d04786$6eefe670$4ccfb350$@acm.org>
Date: Fri, 13 Feb 2015 13:41:03 +0100
Message-ID: 
 <CAK2iWdQ_yHDno2ifDGLHxETYP+w8x2n9eCotcJ2=mAviKwTWNQ@mail.gmail.com>
Subject: Re: [PROPOSAL] move repo to Git.
From: jan i <jani@apache.org>
To: dev <dev@openoffice.apache.org>, Dennis Hamilton <dennis.hamilton@acm.org>
Content-Type: multipart/alternative; boundary=001a11c34daeb213f6050ef78cf6

--001a11c34daeb213f6050ef78cf6
Content-Type: text/plain; charset=UTF-8

On 13 February 2015 at 13:13, Dennis E. Hamilton <dennis.hamilton@acm.org>
wrote:

> Isn't having the mirror on GitHub an effective way to push changes to the
> SVN, especially for Apache committers who have project rights to the GitHub
> repo?  Non-committer pull requests are as complicated either way, it seems
> to me, and the GitHub mirror might be superior for that.
>
no it is not. You cannot push from github to either git or svn at apache.

Please be aware that I wrote git, not github. ASF has its own git server,
which is mandatory to use.


>
> I assume the proposal is do-able, but I wonder what kind of disruption
> cost there is for current work.
>
Well it is not only do-able, at the moment about half of all ASF projects
work that way. The disruption cost is an infra ticket, and about 3-4 hours
downtime.

We have today more git commits than svn commits.

rgds
jan i.


>
>  - Dennis
>
> Below, I have no opinion, just wonder if these are also relevant
> considerations?
>
> PS: Our current SVN repo is also used for source control of openoffice.org,
> So I assume it is not a total give-up.  Also, we have SVN tags and branches
> that might be problematic, I think.
>
> PPS: The AOO repo is also a bit larger than what Linus apparently thinks
> is cool.  This gets back to how could the AOO repo be refactored in order
> to modularize the software and simplify (re-)building and staged evolution
> of features.
>
> -----Original Message-----
> From: jan i [mailto:jani@apache.org]
> Sent: Friday, February 13, 2015 03:44
> To: dev
> Subject: [PROPOSAL] move repo to Git.
>
> Hi.
>
> We have now for a while had a readonly Git copy of our svn repo.
>
> Should we move to a full git repo, making it easier for new developers to
> participate (although it is in no way a guarantee, that it will attract new
> people) by lowering the barrier.
>
> For more documentation on Git at Apache see https://git-wip-us.apache.org/
>
> Moving to a full git repo (see http://git.apache.org/), would mean giving
> up our current SVN repo, but history etc. will be available in Git instead.
>
> The choice is there, and it is just a matter of how people want to work.
>
> thoughts ?
>
> rgds
> jan I.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>

--001a11c34daeb213f6050ef78cf6--