hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@apache.org>
Subject Re: [VOTE] Proposed bylaws for the Hadoop project
Date Thu, 05 Nov 2009 11:07:03 GMT
Owen O'Malley wrote:
> On Tue, Nov 3, 2009 at 12:12 AM, Hemanth Yamijala <yhemanth@yahoo-inc.com>wrote:
>> Owen
>> Some clarifications:
>> In the section on "Code Change" when you mention approval as "Lazy approval
>> and then lazy consensus", did you mean the consensus will need to come into
>> play if a veto is received ?
> Hmm... I copied that section from Ant's bylaws. Our current practice is
> probably actually lazy consensus since we require a +1 before it can be
> committed.

Ant works with commit-then-discuss, nobody works on it for a living, 
it's all voluntary, and the rate of change of the codebase is fairly 
low. There's little bureaucracy overhead to encourage code contribs -and 
every deverloper is expected to look at the commit log to see what is 
going on.

what's not spelled out in Ant's docs are that the architecture of the 
system is very compartmentalised, where it's obvious from  the source 
files what's going to break, so just by looking at the source filenames 
you can guess what the issues will be

-optional obscure SCM tasks: any changes here are welcome
-other optional stuff: those classes and subclasses may break, if they 
are used a lot review carefully
-junit : all the CI servers, lots of hate mail
-java, exec, : how code runs, lots of CI builds fail, many complaints, 
the IDE teams stop sending you xmas cards.
-<fileset> et al. complex, discuss first, tread carefully and worry 
about memory consumption
-IntrospectionHelper, TaskAdapter, the code that maps from XML to java; 
you have to really know what you are doing before going near this code, 
and unless the rest of the team trusts you, you won't get a lookin. 
Nobody touches this stuff without lots of discussion, more tests etc as 
it breaks everything
-Classpath work. Everyone worries about this, nobody really understands 
it. Anyone who says they do is probably misguided.

Because of that hierarchy, you can get a vague idea of where trouble 
will be without even reading the diffs, just looking at the subject 
lines, and if you get people with problems on optional tasks to start 
providing tests then patches, you get them fixing the problem and sucked 
into the task of codebase maintenance.


View raw message