Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: pass (athena.apache.org: local policy)
Cc: infrastructure-dev@apache.org
Message-Id: <2ED80C73-B994-4204-BED6-0595085B06B4@atlassian.com>
From: Tim Moore <tmoore@atlassian.com>
To: shindig-dev@incubator.apache.org
In-Reply-To: <b71cdca90906111350h1e22aae5v8d7a87150cd72741@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: Gerrit@Apache call for interested comitters
Date: Thu, 11 Jun 2009 14:16:16 -0700
References: <4A311EB1.6090102@tuffmail.com>
 <1244744240.16230.2.camel@localhost>
 <aa285c160906111341h1acc3aa0wafdce8afebec0555@mail.gmail.com>
 <b71cdca90906111350h1e22aae5v8d7a87150cd72741@mail.gmail.com>

I would be highly enthusiastic about Shindig moving to git. I expect =20
that many companies that use Shindig maintain an internal fork of the =20=

code. I know we do. Git can make managing that kind of thing much nicer.

-- Tim

On Jun 11, 2009, at 1:50 PM, Paul Lindner wrote:

> When I moved over to my new job I started using git for everything,
> including shindig.  So far so good.  A bit of a learning curve, but =20=

> very
> satisfying once you get all the pieces working together.
> The git-cheatsheet =
http://ktown.kde.org/~zrusin/git/git-cheat-sheet.svg=20
>  has
> most of what you need to know.
>
> On Thu, Jun 11, 2009 at 1:41 PM, Kevin Brown <etnu@google.com> wrote:
>
>> On Thu, Jun 11, 2009 at 11:17 AM, Santiago Gala =
<santiago.gala@gmail.com
>>> wrote:
>>
>>> El jue, 11-06-2009 a las 17:11 +0200, Grzegorz Kossakowski escribi=F3:=

>>>> Hello,
>>>>
>>>> On 29th of June I'll start working on Gerrit[1] project for next =20=

>>>> three
>>> months. I think this would be a perfect
>>>> opportunity to introduce Gerrit as part of the experimental Git
>>> infrastructure.
>>>>
>>>> In order to make this effort practical I seek for a bunch of =20
>>>> interested
>>> committers willing to experiment with Gerrit as
>>>> a patch review tool. This implies that community of given project =20=

>>>> must
>> be
>>> enthusiastic on Git as whole as such
>>>> experiment will change project practices slightly and introduce Git
>> into
>>> development cycle as a tool for collaboration
>>>> between comitters and contributors.
>>>>
>>>> If you know any project fulfilling these requirements and willing =20=

>>>> to
>> play
>>> with Git a little bit more let me know here so
>>>> we can discuss some more details.
>>>>
>>>> [1] http://code.google.com/p/gerrit/
>>>>
>>>
>>> (incubator-)Shindig can be a reasonable candidate, out of several
>>> reasons:
>>> - there is extensive use of code review for patches already, so it =20=

>>> would
>>> be mostly a matter of switching URLs
>>> - I'm not so sure about effective git usage. Some people seems to be
>>> using it, but this would need to be checked.
>>
>>
>> I'm not terribly familiar with git beyond a presentation from Linus =20=

>> that I
>> saw a few years ago, but I'd be willing to give it a try if it =20
>> means better
>> integration for reviews than the current codereview.appspot.com -> =20=

>> patch
>> ugliness.
>>
>>
>>>
>>>
>>> I'm CCing shindig-dev, to see how people reacts to it.
>>>
>>> Regards
>>> Santiago
>>>
>>>
>>