Re: [PEAR-DEV] Hosting PEAR's git repositories on git.php.net

>
> I also see a benefit in having using an "official" place instead of
> relying on github too much.
>
> TYPO3 uses Gerrit for code-review, has solutions for voting on a patch
> and given enough votes/karma patches can also easily be submitted from
> there. If interested I can elaborate a bit further on "Gerrit at typo3.org
> ".
>
>
> http://vimeo.com/20084957 does show a lot of the capabilities we've
talked about as wanting (a code review/pull request style flow, more @
http://source.android.com/source/life-of-a-patch.html); but it seems *
significantly* more complex that the pull request metaphor - at least where
it's pushing the complexity onto the end user.


If we were an enterprise (or the core php project), I'd say yes, put up
with it and train people, but for the casual contribution scenario we're
in... that's a big learning curve.


Is it as hard as the video portrays?
Are there "3 steps to get up and running with gerrit and patches"
instructions out there?

I'm not really familiar with the typo3 community, and after about 10
minutes of blundering around - http://wiki.typo3.org/Git_Gerrit /
http://wiki.typo3.org/Gerrit_Review_Workflow is all I found.

Looking at the ohloh stats, http://www.ohloh.net/p/pear vs
http://www.ohloh.net/p/typo3, we're probably about the same size in terms
of commits/contributors at this point in time.

Given the similarity, can you share with us the typical experience of a new
or existing contributor? Do they experience the learning curve I'm afraid
of, or is there enough support to eliminate that?
What type of contributions do you see most - sporadic patches from random
people, or the same group solving problems on behalf of a company?