hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Fondermann <bernd.fonderm...@googlemail.com>
Subject Re: [VOTE] Abandon hdfsproxy HDFS contrib
Date Fri, 18 Feb 2011 10:11:58 GMT
On Thu, Feb 17, 2011 at 19:43, Roy T. Fielding <fielding@gbiv.com> wrote:
> On Feb 17, 2011, at 4:43 AM, Bernd Fondermann wrote:
>> We have the very unfortunate situation here at Hadoop where Apache
>> Hadoop is not the primary and foremost place of Hadoop development.
>> Instead, code is developed internally at Yahoo and then contributed in
>> (smaller or larger) chunks to Hadoop.
>> This is open source development upside down.
> It is not open development.  The development community can do better,
> but it has to make up for past mistakes first.
>> It is not ok for people to diff ASF svn against their internal code
>> and provide the diff as a patch without reviewing IP first for every
>> line of code changed.
> That is simply untrue.  If the code came from one company's employees
> and they all signed an employment agreement with their employer and
> the employer approves of the contribution and the committer knows that
> when they commit (and logs the authors of the patch when committed),
> then all necessary IP clearance has been done.

I don't know how many Y-employees are working on H internally. Only
the contributors can sort that out.

> Committers are responsible
> for ensuring that they have permission to commit under their own CLA.

I just wanted to point that out, not stop someone from contributing.
Of course, your words are much more precise than mine.

>> For larger chunks I'd suggest to even go via the Incubator IP clearance process.
> Nonsense (with director hat on).
>> Only then will we force committers to primarily work here in the open
>> and return to what I'd consider a healthy project.
> No, you'll force people to work on the open by actually collaborating
> with them as they work and veto a patch for any technical faults it
> may contain.  Pestering them about your personal view of the Apache Way
> of development is not a contribution.

Getting personal is not a valuable contribution either.


View raw message