incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Omar Gonzalez <>
Subject Re: Rushing into Git
Date Thu, 22 Nov 2012 09:06:21 GMT
On Thu, Nov 22, 2012 at 12:56 AM, Erik de Bruin <> wrote:

> I'm not convinced at all this will work out well for the project, with
> the graduation coming up soon (which will mean moving and changing a
> lot of stuff in SVN and elsewhere) and all. But I'll shut up about
> this (for now).

Like I said earlier, I don't think this will affect graduation. We could
have used the graduation as an opportunity to request from Apache INFRA
that the move to Git happen now to avoid having to go through the process
again. However, I don't think its wise to complicate the graduation further
by making that request now. In my talks with Apache INFRA they made it
clear they would like more Python devs to help facilitate the bug fixing in
the Apache Git admin tool and to support projects moving to Git.

> Maybe you can do me (and other doubters and SVN aficionados) and write
> up the current status of the move, the planned actions for the move
> and the implications of the move for contributors, committers and the
> project in general?
> Thanks,
> EdB

The status of the move is that we need someone proficient in Python to
volunteer so that we may submit a request for our read/write Apache Git
repo. I purchased a Python book last week and will have two weeks off in
December during which I plan on going through that book some more and start
looking at trying to start to submit patches for the git admin tool. If we
could find another Python dev before I can become useful on this front then
that would be great.

Once we have someone positioned for that we can start the discussion with
Apache INFRA, at which point we can learn more about the planning and
effects of the move on the rest of the committers. I would suggest that at
that point we would examine the workflows that other Apache projects are
already using with their read/write Git repos to apply the workflow we
voted for on Git.

This is why I said this is not going to be rushed into. It is still going
to take some time to get all our ducks lined up, so to speak.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message