The advantages of Git for development on a team is primarily in terms
of fast, cheap (and even local) branching and merging. Overall
advantages are flexible workflow and having full history at all times.

Basically, I've been working on some client and personal projects
(using Git) and I now dread moving back to SVN to start up the next
phase of T5 development.

Git represents a much more community based approach, and having a
sharable Git repository makes getting useful patches from the
community that much easier.

I'm not totally adverse to having an external Git repository (even at
GitHub) and cross-committing updates to an "official" SVN repository
... especially if this could be done in an automatic way.

The reality is that regardless of whether code comes in as patches in
JIRA or as Git pull requests on GitHub, there is still a committer
making the change and committing it to the "master" repository. Using
Git instead of SVN does not affect the underlying process, especially
as it concerns CLA.


On Mon, Nov 30, 2009 at 1:43 AM, Greg Stein <[email protected]> wrote:
> Jukka was working through the hosting issues. Last I heard, while at
> ApacheCon a few weeks ago, was that it wasn't really possible for Git
> to meet all the requirements. I don't recall what it is, but you're
> talking things like recovery, authentication/authorization,
> intercontinental replication/failover, etc.
>
> Personally, I find the notion of Apache developers working on private
> git repositories (rather than the central svn repository) to be
> anti-community. But I understand you can *make* git work in a more
> communal and open fashion. But my opinion is neither here nor there.
> The technical issues need to be solved first.
>
> Cheers,
> -g
>
> On Sun, Nov 29, 2009 at 18:23, Howard Lewis Ship <[email protected]> wrote:
>> Ok, what will it take to go beyond simple mirroring to full-fledged
>> project hosting?
>>
>> On Sat, Nov 28, 2009 at 9:53 PM, Philip M. Gollucci
>> <[email protected]> wrote:
>>> Howard Lewis Ship wrote:
>>>>>From what I can tell, Git at Apache is limited to clones of Subversion
>>>> repositories.
>>>>
>>>> The members of the Tapestry project are all very interested in using
>>>> Git for day-to-day work on Tapestry. Are there any plans to set up
>>>> read/write Git repositories at Apache?  I haven't seen any useful
>>>> information about this here, or on the Apache Board mailing list.
>>>
>>> There are no current plans to expand beyond what is available at
>>> git.apache.org.
>>>
>>>
>>>
>>>
>>> --
>>> ------------------------------------------------------------------------
>>> 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C
>>> Philip M. Gollucci ([email protected]) c: 703.336.9354
>>> VP Apache Infrastructure; Member, Apache Software Foundation
>>> Committer,                        FreeBSD Foundation
>>> Sr. System Admin,                 Ridecharge Inc.
>>> Consultant,                       P6M7G8 Inc.
>>>
>>> Work like you don't need the money,
>>> love like you'll never get hurt,
>>> and dance like nobody's watching.
>>>
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to