what it takes to gain commit access to hadoop?

On 21 November 2012 15:03, Radim Kolar <[EMAIL PROTECTED]> wrote:

> what it takes to gain commit access to hadoop?
>
good question.

I've put some of my thoughts on the topic into a presentation I gave last
month:
http://www.slideshare.net/steve_l/inside-hadoopdev

That isn't so much about commit/non-commit status, because it was more
focused about getting your code in -which is normally what matters.

Even committers have to go through RTC -you don't get any special
privileges from commit rights, the task of keeping patches up to date and
having to remind others to review it. The main "feature" is that when you
get the +1  vote you yourself get to deal with the grunge work of apply
patches to one or more svn branches, resyncing that with the git branches
you inevitably do your own work on.

And it also gives you more responsibilty to review and commit others'
works, which is something that some of (I point to myself here) are lax at.
I can't help wondering if we need to be a bit more formal about that too,
have one day a month "review sundays"(*) where we do go through and review
the outstanding works, so they don't fall by the wayside.

-steve

(*) Yes, a sunday. I know everyone  is too busy to dedicate a weekday to
this.

> The main "feature" is that when you get the +1  vote you yourself get to deal with the grunge work of apply
> patches to one or more svn branches, resyncing that with the git branches
> you inevitably do your own work on.
no, main feature is major speed advantage. It takes forever to get
something committed. I was annoyed with apache nutch last year and
forked it, here is snapshot from forked codebase
http://forum.lupa.cz/index.php?action=dlattach;topic=1674.0;attach=3439
now its 160k LOC on top of apache nutch 1.4. If i worked with these
guys, it would be never done because it took them 4 months to get 200
lines patch reviewed.

Hadoop has huge backlog of patches, you need way more committers then
you have today. I simply could not assign person to working on hadoop
fulltime because if he submits mere 5 patches per day, you will be never
able to process them.

Your current development process fail to scale. What are your plans for
moving development faster?