Hi Tim, ASF has a lot of projects, including Shindig, using GIT (read-only) http://git.apache.org/
Cheers, Vincent 2009/6/11 Tim Moore <tmo...@atlassian.com>: > I would be highly enthusiastic about Shindig moving to git. I expect that > many companies that use Shindig maintain an internal fork of the 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 very >> satisfying once you get all the pieces working together. >> The git-cheatsheet >> http://ktown.kde.org/~zrusin/git/git-cheat-sheet.svg has >> most of what you need to know. >> >> On Thu, Jun 11, 2009 at 1:41 PM, Kevin Brown <e...@google.com> wrote: >> >>> On Thu, Jun 11, 2009 at 11:17 AM, Santiago Gala <santiago.g...@gmail.com >>>> >>>> wrote: >>> >>>> El jue, 11-06-2009 a las 17:11 +0200, Grzegorz Kossakowski escribió: >>>>> >>>>> Hello, >>>>> >>>>> On 29th of June I'll start working on Gerrit[1] project for next 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 interested >>>> >>>> committers willing to experiment with Gerrit as >>>>> >>>>> a patch review tool. This implies that community of given project 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 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 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 that >>> I >>> saw a few years ago, but I'd be willing to give it a try if it means >>> better >>> integration for reviews than the current codereview.appspot.com -> patch >>> ugliness. >>> >>> >>>> >>>> >>>> I'm CCing shindig-dev, to see how people reacts to it. >>>> >>>> Regards >>>> Santiago >>>> >>>> >>> > >
