Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # general >> [VOTE] Hadoop Bylaws

Copy link to this message
Re: [VOTE] Hadoop Bylaws
+1 -C


Summary of protocol for major votes:
  Adding code: Lazy consensus (committers)
  Release plan: Lazy majority (committers)
  Releasing code: Lazy majority (PMC)
  New codebase/subproject: Lazy 2/3 majority (PMC)
  Adding contributor: Lazy consensus (PMC)
  Removing contributor: Lazy 2/3 majority (PMC)
  Change bylaws: Majority (PMC)
  7 day voting period

On Fri, Nov 19, 2010 at 10:45 PM, Owen O'Malley <[EMAIL PROTECTED]> wrote:
> All,
>   I've updated the proposed bylaws that I sent out a few weeks ago as
> suggested by making the vote for removal be a lazy 2/3, so now all of the
> votes are lazy. As before, by a recursive application of the bylaws let's
> let the vote last 7 days (11/26) and require a lazy majority of PMC members
> to pass.
> -- Owen
> Apache Hadoop Project Bylaws
> This document defines the bylaws under which the Apache Hadoop project
> operates. It defines the roles and responsibilities of the project,
> who may vote, how voting works, how conflicts are resolved, etc.
> Hadoop is a project of the <a
> href="http://www.apache.org/foundation/">Apache Software
> Foundation</a>.  The foundation holds the trademark on the name
> "Hadoop" and copyright on Apache code
> including the code in the Hadoop codebase. The <a
> href="http://www.apache.org/foundation/faq.html">foundation FAQ</a>
> explains the operation and background of the foundation.
> Hadoop is typical of Apache projects in that it operates under a set
> of principles, known collectively as the "Apache Way". If
> you are new to Apache development, please refer to the <a
> href="http://incubator.apache.org">Incubator project</a> for more
> information on how Apache projects operate.
> Roles and Responsibilities
> Apache projects define a set of roles with associated rights and
> responsibilities. These roles govern what tasks an individual may
> perform within the project. The roles are defined in the following
> sections
>   * Users
>        The most important participants in the project are people who
>        use our software. The majority of our developers start out as
>        users and guide their development efforts from the user's
>        perspective.
>       Users contribute to the Apache projects by providing feedback
>        to developers in the form of bug reports and feature
>        suggestions. As well, users participate in the Apache
>        community by helping other users on mailing lists and user
>        support forums.
>   * Contributors
>        All of the volunteers who are contributing time, code,
>        documentation, or resources to the Hadoop Project. A contributor
>        that makes sustained, welcome contributions to the project may
>        be invited to become a Committer, though the exact timing of
>        such invitations depends on many factors.
>    * Committers
>       The project's Committers are responsible for the project's
>        technical management. Committers have access to a specified
>        set of subprojects' subversion repositories. Committers on
>        subprojects may cast binding votes on any technical discussion
>        regarding that subproject.
>       Committer access is by invitation only and must be approved by
>        lazy consensus of the active PMC members. A Committer is
>        considered emeritus by their own declaration or by not
>        contributing in any form to the project for over six
>        months. An emeritus committer may request reinstatement of
>        commit access from the PMC. Such reinstatement is subject to
>        lazy consensus of active PMC members.
>      All Apache committers are required to have a signed Contributor
>        License Agreement (CLA) on file with the Apache Software
>        Foundation. There is a <a
>        href="http://www.apache.org/dev/committers.html">Committer
>        FAQ</a> which provides more details on the requirements for
>        Committers
>       A committer who makes a sustained contribution to the project