hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Foley <mfo...@hortonworks.com>
Subject Re: [VOTE] introduce Python as build-time and run-time dependency for Hadoop and throughout Hadoop stack
Date Mon, 03 Dec 2012 22:08:41 GMT
Hi Doug,
The apache voting process contradicts the Hadoop bylaws:
http://www.apache.org/foundation/voting.html says that only PMC members can
make binding votes on code modification issues, but
http://hadoop.apache.org/bylaws.html says that Committers can make binding
votes on them.  Does that mean the Hadoop bylaws have to change?


On Mon, Dec 3, 2012 at 11:37 AM, Doug Cutting <cutting@apache.org> wrote:

> On Mon, Dec 3, 2012 at 11:21 AM, Matt Foley <mfoley@hortonworks.com>
> wrote:
> > It is intended to be a "technical discussion", in the sense of the bylaws
> > statement (in section "Roles and Responsibilities: Committers"),
> "Committers
> > may cast binding votes on any technical discussion regarding any
> > subproject."  I therefore intended it to be a majority vote of
> Committers.
> I'm not sure how you conclude that technical discussions are resolved
> with majority votes.
> http://www.apache.org/foundation/voting.html
> > Interestingly, this need to discuss tooling and other issues that go
> beyond
> > a simple "code change" is not addressed in the "Decision Making: Actions"
> > section of the bylaws.  That need seems to have been overlooked in the
> > current rev of that section.  But I do not agree that such issues are
> "code
> > changes"; it relates to the tools we depend on to make code changes,
> which
> > is clearly qualitatively different.
> I don't see a striking difference between this and a proposed code
> change.  How is a -1 here fundamentally different than a veto on a
> patch submitted to HADOOP-9082?
> Doug

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message