The funny thing is that with github, you don't need 'committer' access to have your own 'branch'. Steve is hosting his version at
http://gist.github.com/sappling/gradle/tree/master, which is actually downstream from yours ;) (in case you didn't notice).
(I came over it while looking from which repo I could fork my own patches).
And would just like to congratulate the Gradle team on the how to contribute page. I didn't very often submit patches to OSS projects, usually because the things I have issues with are either tiny or I it's discussed in depth on the mailinglist. The ability to sport my own repository of Gradle in about 10 seconds, and have a patch uploaded a couple of minutes later help me personally a lot to lower the barrier for participation.
Cheers,
-Daniel
On Thu, May 28, 2009 at 9:11 PM, Russel Winder
<russel.winder@...> wrote:
On Thu, 2009-05-28 at 07:46 -0400, Steve Appling wrote:
> Our fork is intended to be temporary. We have discussed several of our concerns
> with Hans and I think all of our needs will be met in a future release
> (hopefully 0.7). We just couldn't get everything addressed in 0.6. The fork is
> a way for us to apply our own bug fixes in an timely manner and try out ideas
> for new features we need.
Sounds exactly like what branches are for :-)
The bug fixes perhaps should just be applied to trunk anyway, that would
leave this as a feature branch.
--
Russel.
=============================================================================
Dr Russel Winder Partner
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder