hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From asur...@apache.org
Subject svn commit: r1749608 [1/5] - in /hadoop/common/site/main: author/src/documentation/content/xdocs/ publish/ publish/skin/
Date Tue, 21 Jun 2016 21:31:16 GMT
Author: asuresh
Date: Tue Jun 21 21:31:16 2016
New Revision: 1749608

URL: http://svn.apache.org/viewvc?rev=1749608&view=rev
Log:
Added Subru Krishnan and Carlo Curino as Committer, Added Arun Suresh as PMC

Modified:
    hadoop/common/site/main/author/src/documentation/content/xdocs/who.xml
    hadoop/common/site/main/publish/broken-links.xml
    hadoop/common/site/main/publish/bylaws.html
    hadoop/common/site/main/publish/index.html
    hadoop/common/site/main/publish/linkmap.html
    hadoop/common/site/main/publish/mailing_lists.html
    hadoop/common/site/main/publish/privacy_policy.html
    hadoop/common/site/main/publish/skin/basic.css
    hadoop/common/site/main/publish/skin/print.css
    hadoop/common/site/main/publish/skin/profile.css
    hadoop/common/site/main/publish/skin/screen.css
    hadoop/common/site/main/publish/who.html

Modified: hadoop/common/site/main/author/src/documentation/content/xdocs/who.xml
URL: http://svn.apache.org/viewvc/hadoop/common/site/main/author/src/documentation/content/xdocs/who.xml?rev=1749608&r1=1749607&r2=1749608&view=diff
==============================================================================
--- hadoop/common/site/main/author/src/documentation/content/xdocs/who.xml (original)
+++ hadoop/common/site/main/author/src/documentation/content/xdocs/who.xml Tue Jun 21 21:31:16 2016
@@ -79,6 +79,14 @@
     <td>-8</td>
   </tr>
 
+       <tr>
+         <td>asuresh</td>
+         <td>Arun Suresh</td>
+         <td>Microsoft</td>
+         <td></td>
+         <td>-8</td>
+       </tr>
+
   <tr>
     <td>atm</td>
     <td><a href="http://people.apache.org/~atm">Aaron T. Myers</a></td>
@@ -661,7 +669,7 @@
        <tr>
          <td>asuresh</td>
          <td>Arun Suresh</td>
-         <td>Cloudera</td>
+         <td>Microsoft</td>
          <td></td>
          <td>-8</td>
        </tr>
@@ -763,6 +771,14 @@
        </tr>
 
        <tr>
+         <td>curino</td>
+         <td>Carlo Curino</td>
+         <td>Microsoft</td>
+         <td></td>
+         <td>-8</td>
+       </tr>
+
+       <tr>
          <td>cutting</td>
          <td><a href="http://blog.lucene.com/">Doug Cutting</a></td>
          <td>Cloudera</td>
@@ -1242,6 +1258,14 @@
      	  <td>0</td>
      	</tr>
 
+        <tr>
+         <td>subru</td>
+         <td>Subru Krishnan</td>
+         <td>Microsoft</td>
+         <td></td>
+         <td>-8</td>
+       </tr>
+
        <tr>
          <td>suresh</td>
          <td><a href="http://people.apache.org/~suresh">Suresh Srinivas</a></td>

Modified: hadoop/common/site/main/publish/broken-links.xml
URL: http://svn.apache.org/viewvc/hadoop/common/site/main/publish/broken-links.xml?rev=1749608&r1=1749607&r2=1749608&view=diff
==============================================================================
--- hadoop/common/site/main/publish/broken-links.xml (original)
+++ hadoop/common/site/main/publish/broken-links.xml Tue Jun 21 21:31:16 2016
@@ -1,2 +1,2 @@
-<broken-links>
-</broken-links>
+<broken-links>
+</broken-links>

Modified: hadoop/common/site/main/publish/bylaws.html
URL: http://svn.apache.org/viewvc/hadoop/common/site/main/publish/bylaws.html?rev=1749608&r1=1749607&r2=1749608&view=diff
==============================================================================
--- hadoop/common/site/main/publish/bylaws.html (original)
+++ hadoop/common/site/main/publish/bylaws.html Tue Jun 21 21:31:16 2016
@@ -1,762 +1,762 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.9">
-<meta name="Forrest-skin-name" content="hadoop-pelt">
-<title>Apache Hadoop Project Bylaws</title>
-<link type="text/css" href="skin/basic.css" rel="stylesheet">
-<link media="screen" type="text/css" href="skin/screen.css" rel="stylesheet">
-<link media="print" type="text/css" href="skin/print.css" rel="stylesheet">
-<link type="text/css" href="skin/profile.css" rel="stylesheet">
-<script src="skin/getBlank.js" language="javascript" type="text/javascript"></script><script src="skin/getMenu.js" language="javascript" type="text/javascript"></script><script src="skin/fontsize.js" language="javascript" type="text/javascript"></script>
-<link rel="shortcut icon" href="images/favicon.ico">
-<script type="text/javascript">
-
-  var _gaq = _gaq || [];
-  _gaq.push(['_setAccount', 'UA-7453027-1']);
-  _gaq.push(['_setDomainName', 'apache.org']);
-  _gaq.push(['_trackPageview']);
-
-  (function() {
-    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
-    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
-    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
-  })();
-
-        </script>
-</head>
-<body onload="init()">
-<script type="text/javascript">ndeSetTextSize();</script>
-<div id="top">
-<!--+
-    |breadtrail
-    +-->
-<div class="breadtrail">
-<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://hadoop.apache.org/">Hadoop</a><script src="skin/breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
-</div>
-<!--+
-    |header
-    +-->
-<div class="header">
-<!--+
-    |start group logo
-    +-->
-<div class="grouplogo">
-<a href="http://www.apache.org"><img class="logoImage" alt="Apache" src="images/apache_feather.gif" title="Apache Software Foundation"></a>
-</div>
-<!--+
-    |end group logo
-    +-->
-<!--+
-    |start Project Logo
-    +-->
-<div class="projectlogo">
-<a href="http://hadoop.apache.org/"><img class="logoImage" alt="Hadoop" src="images/hadoop-logo.jpg" title="Scalable Distributed Computing"></a>
-</div>
-<!--+
-    |end Project Logo
-    +-->
-<!--+
-    |start Search
-    +-->
-<div class="searchbox">
-<form action="http://search-hadoop.com/" method="get">
-<input onFocus="getBlank (this, 'Search with Apache Solr');" size="25" name="q" id="query" type="text" value="Search with Apache Solr">&nbsp;
-		  <input value="Search" type="submit">
-</form>
-</div>
-<!--+
-    |end search
-    +-->
-<!--+
-    |start Tabs
-    +-->
-<ul id="tabs">
-<li class="current">
-<a class="selected" href="index.html">Top</a>
-</li>
-<li>
-<a class="unselected" href="http://wiki.apache.org/hadoop">Wiki</a>
-</li>
-</ul>
-<!--+
-    |end Tabs
-    +-->
-</div>
-</div>
-<div id="main">
-<div id="publishedStrip">
-<!--+
-    |start Subtabs
-    +-->
-<div id="level2tabs"></div>
-<!--+
-    |end Endtabs
-    +-->
-<script type="text/javascript"><!--
-document.write("Last Published: " + document.lastModified);
-//  --></script>
-</div>
-<!--+
-    |breadtrail
-    +-->
-<div class="breadtrail">
-
-             &nbsp;
-           </div>
-<!--+
-    |start Menu, mainarea
-    +-->
-<!--+
-    |start Menu
-    +-->
-<div id="menu">
-<div onclick="SwitchMenu('menu_selected_1.1', 'skin/')" id="menu_selected_1.1Title" class="menutitle" style="background-image: url('skin/images/chapter_open.gif');">About</div>
-<div id="menu_selected_1.1" class="selectedmenuitemgroup" style="display: block;">
-<div class="menuitem">
-<a href="index.html">Welcome</a>
-</div>
-<div class="menuitem">
-<a href="releases.html">Releases</a>
-</div>
-<div class="menuitem">
-<a href="mailing_lists.html">Mailing Lists</a>
-</div>
-<div class="menuitem">
-<a href="issue_tracking.html">Issue Tracking</a>
-</div>
-<div class="menuitem">
-<a href="who.html">Who We Are?</a>
-</div>
-<div class="menuitem">
-<a href="http://wiki.apache.org/hadoop/PoweredBy">Who Uses Hadoop?</a>
-</div>
-<div class="menuitem">
-<a href="http://www.cafepress.com/hadoop/">Buy Stuff</a>
-</div>
-<div class="menuitem">
-<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
-</div>
-<div class="menuitem">
-<a href="http://www.apache.org/foundation/thanks.html">Thanks</a>
-</div>
-<div class="menuitem">
-<a href="privacy_policy.html">Privacy Policy</a>
-</div>
-<div class="menupage">
-<div class="menupagetitle">Bylaws</div>
-<div class="menupageitemgroup">
-<div class="menupageitem">
-<a href="#Introduction">Introduction</a>
-</div>
-<div class="menupageitem">
-<a title="Roles and Responsibilities" href="#Roles+and+Responsibilities">Roles and Responsib...</a>
-</div>
-<div class="menupageitem">
-<a href="#Decision+Making">Decision Making</a>
-</div>
-</div>
-</div>
-<div class="menuitem">
-<a href="http://www.apache.org/licenses/">License</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.2', 'skin/')" id="menu_1.2Title" class="menutitle">Documentation</div>
-<div id="menu_1.2" class="menuitemgroup">
-<div class="menuitem">
-<a href="http://hadoop.apache.org/docs/current/">Current</a>
-</div>
-<div class="menuitem">
-<a href="http://hadoop.apache.org/docs/stable/">Stable</a>
-</div>
-<div class="menuitem">
-<a href="http://hadoop.apache.org/docs/r1.2.1/">Release 1.2.1</a>
-</div>
-<div class="menuitem">
-<a href="http://hadoop.apache.org/docs/r2.5.2/">Release 2.5.2</a>
-</div>
-<div class="menuitem">
-<a href="http://hadoop.apache.org/docs/r2.6.4/">Release 2.6.4</a>
-</div>
-<div class="menuitem">
-<a href="http://hadoop.apache.org/docs/r0.23.11/">Release 0.23.11</a>
-</div>
-<div class="menuitem">
-<a href="http://hadoop.apache.org/docs/r2.7.2/">Release 2.7.2</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.3', 'skin/')" id="menu_1.3Title" class="menutitle">Related Projects</div>
-<div id="menu_1.3" class="menuitemgroup">
-<div class="menuitem">
-<a href="http://incubator.apache.org/ambari/">Ambari</a>
-</div>
-<div class="menuitem">
-<a href="http://avro.apache.org/">Avro</a>
-</div>
-<div class="menuitem">
-<a href="http://cassandra.apache.org/">Cassandra</a>
-</div>
-<div class="menuitem">
-<a href="http://incubator.apache.org/chukwa/">Chukwa</a>
-</div>
-<div class="menuitem">
-<a href="http://incubator.apache.org/hama/">Hama</a>
-</div>
-<div class="menuitem">
-<a href="http://hbase.apache.org/">HBase</a>
-</div>
-<div class="menuitem">
-<a href="http://hive.apache.org/">Hive</a>
-</div>
-<div class="menuitem">
-<a href="http://mahout.apache.org/">Mahout</a>
-</div>
-<div class="menuitem">
-<a href="http://pig.apache.org/">Pig</a>
-</div>
-<div class="menuitem">
-<a href="http://spark.incubator.apache.org/">Spark</a>
-</div>
-<div class="menuitem">
-<a href="http://tez.incubator.apache.org/">Tez</a>
-</div>
-<div class="menuitem">
-<a href="http://zookeeper.apache.org/">ZooKeeper</a>
-</div>
-</div>
-<div id="credit"></div>
-<div id="roundbottom">
-<img style="display: none" class="corner" height="15" width="15" alt="" src="skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
-<!--+
-  |alternative credits
-  +-->
-<div id="credit2"></div>
-</div>
-<!--+
-    |end Menu
-    +-->
-<!--+
-    |start content
-    +-->
-<div id="content">
-<div title="Portable Document Format" class="pdflink">
-<a class="dida" href="bylaws.pdf"><img alt="PDF -icon" src="skin/images/pdfdoc.gif" class="skin"><br>
-        PDF</a>
-</div>
-<h1>Apache Hadoop Project Bylaws</h1> 
-
-    
-<a name="N1000D"></a><a name="Introduction"></a>
-<h2 class="h3">Introduction</h2>
-<div class="section">
-<p>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.</p>
-<p>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.</p>
-<p>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.</p>
-</div>
-
-   
-<a name="N10028"></a><a name="Roles+and+Responsibilities"></a>
-<h2 class="h3">Roles and Responsibilities</h2>
-<div class="section">
-<p>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</p>
-<ul>
-   
-<li> 
-<strong>Users</strong>
-
-        
-<p>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.</p>
-
-        
-<p> 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.</p>
-</li>
-
-   
-<li> 
-<strong>Contributors</strong>
-
-        
-<p>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.</p>
-</li>
-
-   
-<li> 
-<strong>Committers</strong>
-
-        
-<p>The project's Committers are responsible for the project's
-        technical management. Committers have access to all subproject
-        subversion repositories. Committers may cast binding votes on
-        any technical discussion regarding any subproject.</p>
-
-        
-<p>Committer access is by invitation only and must be approved by
-        consensus approval 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
-        consensus approval of active PMC members.</p>
-
-        
-<p>Significant, pervasive features are often developed in a speculative
-        branch of the repository. The PMC may grant commit rights on the
-        branch to its consistent contributors, while the initiative is active.
-        Branch committers are responsible for shepherding their feature into
-        an active release and do not cast binding votes or vetoes in the
-        project.</p>
-
-        
-<p>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</p>
-
-        
-<p>A committer who makes a sustained contribution to the project
-        may be invited to become a member of the PMC. The form of
-        contribution is not limited to code. It can also include code
-        review, helping out users on the mailing lists, documentation,
-        testing, etc.</p>
-</li>
-
-   
-<li> 
-<strong>Release Manager</strong>
-
-        
-<p>A Release Manager (RM) is a committer who volunteers to produce 
-	a Release Candidate according to <a href="https://wiki.apache.org/hadoop/HowToRelease">HowToRelease</a>.
-	The RM shall publish a Release Plan on the <em>common-dev@</em> 
-	list stating the branch from which they intend to make a Release 
-	Candidate, at least one week before they do so. The RM is responsible 
-	for building consensus around the content of the Release Candidate, 
-	in order to achieve a successful Product Release vote.</p>
-</li>
-
-   
-<li> 
-<strong>Project Management Committee</strong>
-
-        
-<p>The Project Management Committee (PMC) for Apache Hadoop was
-        created by the Apache Board in January 2008 when Hadoop moved
-        out of Lucene and became a top level project at Apache. The
-        PMC is responsible to the board and the ASF for the management
-        and oversight of the Apache Hadoop codebase. The
-        responsibilities of the PMC include</p>
-
-        
-<ul>
-        
-<li> Deciding what is distributed as products of the Apache Hadoop
-        project.  In particular all releases must be approved by the
-        PMC</li>
-
-        
-<li> Maintaining the project's shared resources, including the codebase
-             repository, mailing lists, websites.</li>
-
-        
-<li> Speaking on behalf of the project.</li>
-
-        
-<li> Resolving license disputes regarding products of the project</li>
-
-        
-<li> Nominating new PMC members and committers</li>
-
-        
-<li> Maintaining these bylaws and other guidelines of the project</li>
-        
-</ul>
-
-        
-<p>Membership of the PMC is by invitation only and must be
-        approved by a consensus approval of active PMC members. A PMC
-        member is considered "emeritus" by their own
-        declaration or by not contributing in any form to the project
-        for over six months. An emeritus member may request
-        reinstatement to the PMC. Such reinstatement is subject to
-        consensus approval of the active PMC members.</p>
-
-        
-<p>The chair of the PMC is appointed by the ASF board. The chair
-        is an office holder of the Apache Software Foundation (Vice
-        President, Apache Hadoop) and has primary responsibility to
-        the board for the management of the projects within the scope
-        of the Hadoop PMC. The chair reports to the board quarterly on
-        developments within the Hadoop project.</p>
-
-	
-<p>The chair of the PMC is rotated annually. When the chair is
-	rotated or if the current chair of the PMC resigns, the PMC
-	votes to recommend a new chair using Single Transferable Vote
-	(STV) voting. See http://wiki.apache.org/general/BoardVoting
-	for specifics. The decision must be ratified by the Apache
-	board.</p>
-</li>
-   
-</ul>
-</div>
-
-
-<a name="N10094"></a><a name="Decision+Making"></a>
-<h2 class="h3">Decision Making</h2>
-<div class="section">
-<p>Within the Hadoop project, different types of decisions require
-      different forms of approval. For example, the 
-      <a href="#Roles+and+Responsibilities">previous section</a> 
-      describes several
-      decisions which require "consensus approval"
-      approval. This section defines how voting is performed, the
-      types of approvals, and which types of decision require which
-      type of approval.</p>
-<ul>
-      
-<li> 
-<strong>Voting</strong>
-
-      
-<p>Decisions regarding the project are made by votes on the
-      primary project development mailing list
-      (general@hadoop.apache.org).  Where necessary, PMC voting may
-      take place on the private Hadoop PMC mailing list.  Votes are
-      clearly indicated by subject line starting with [VOTE].  Votes
-      may contain multiple items for approval and these should be
-      clearly separated. Voting is carried out by replying to the
-      vote mail. Voting may take four flavors</p>
-
-        
-<ul>
-         
-<li> 
-<strong>+1</strong> "Yes," "Agree," or 
-              "the action 
-              should be performed." In general, this vote also indicates 
-              a willingness on the behalf of the voter in "making it 
-             happen"</li>
-
-         
-<li> 
-<strong>+0</strong> This vote indicates a willingness for the 
-              action under
-              consideration to go ahead. The voter, however will not be able
-              to help.</li>
-
-         
-<li> 
-<strong>-0</strong> This vote indicates that the voter does 
-              not, in general, 
-              agree with the proposed action but is not concerned enough to 
-              prevent the action going ahead.</li>
-
-         
-<li> 
-<strong>-1</strong> This is a negative vote. On issues where 
-              consensus is 
-              required, this vote counts as a <strong>veto</strong>. All 
-              vetoes must contain an explanation of why the veto is 
-              appropriate. Vetoes with no explanation are void. It may also 
-              be appropriate for a -1 vote to include an alternative course 
-              of action.</li>
-        
-</ul>
-
-        
-<p>All participants in the Hadoop project are encouraged to show their
-        agreement with or against a particular action by voting. For technical
-        decisions, only the votes of active committers are binding. Non binding
-        votes are still useful for those with binding votes to understand the
-        perception of an action in the wider Hadoop community. For PMC 
-        decisions, only the votes of PMC members are binding.</p>
-
-       
-<p>Voting can also be applied to changes made to the Hadoop codebase. 
-       These typically take the form of a veto (-1) in reply to the commit 
-       message sent when the commit is made.</p>
-</li>
-
-    
-<li> 
-<strong>Approvals</strong>
-
-        
-<p>These are the types of approvals that can be sought. Different 
-        actions require different types of approvals</p>
-
-        
-<ul>
-        
-<li> 
-<strong>Consensus Approval -</strong>
-             Consensus approval requires 3 binding +1 votes
-             and no binding vetoes.</li>
-
-        
-<li> 
-<strong>Lazy Consensus -</strong>
-             Lazy consensus requires no -1 votes ('silence gives assent').</li>
-
-        
-<li> 
-<strong>Lazy Majority - </strong>
-             A lazy majority vote requires 3 binding +1
-             votes and more binding +1 votes than -1 votes.</li>
-
-        
-<li> 
-<strong>Lazy 2/3 Majority -</strong>
-             Lazy 2/3 majority votes requires at
-             least 3 votes and twice as many +1 votes as -1 votes.</li>
-        
-</ul>
-</li>
-
-    
-<li> 
-<strong>Vetoes</strong>
-
-        
-<p>A valid, binding veto cannot be overruled. If a veto is cast,
-        it must be accompanied by a valid reason explaining the
-        reasons for the veto. The validity of a veto, if challenged,
-        can be confirmed by anyone who has a binding vote. This does
-        not necessarily signify agreement with the veto - merely that
-        the veto is valid.</p>
-
-        
-<p>If you disagree with a valid veto, you must lobby the person casting
-        the veto to withdraw their veto. If a veto is not withdrawn, any action
-        that has been vetoed must be reversed in a timely manner.</p>
-</li>
-
-    
-<li> 
-<strong>Actions</strong>
-
-        
-<p>This section describes the various actions which are undertaken 
-        within the project, the corresponding approval required for that 
-        action and those who have binding votes over the action.</p>
-
-         
-<ul>
-         
-<li> 
-<strong>Code Change</strong>
-
-            
-<p>A change made to a codebase of the project and committed
-            by a committer. This includes source code, documentation, website
-            content, etc.</p>
-
-            
-<p>Consensus approval of active committers, but with a minimum of
-            one +1. The code can be committed after the first +1, unless
-            the code change represents a merge from a branch, in which case
-            three +1s are required.</p>
-</li>
-
-         
-<li> 
-<strong>Product Release</strong>
-
-            
-<p>When a release of one of the project's products is ready, a 
-            vote is required to accept the release as an official release of
-            the project.</p>
-
-           
-<p>Lazy Majority of active PMC members</p>
-</li>
-
-         
-<li> 
-<strong>Adoption of New Codebase</strong>
-
-            
-<p>When the codebase for an existing, released product is to be
-            replaced with an alternative codebase. If such a vote fails to
-            gain approval, the existing code base will continue.</p>
-
-            
-<p>This also covers the creation of new sub-projects
-            within the project</p>
-
-            
-<p>Lazy 2/3 majority of PMC members</p>
-</li>
-
-         
-<li> 
-<strong>New Branch Committer</strong>
-
-            
-<p>When a branch committer is proposed for the PMC</p>
-
-            
-<p>Lazy consensus of active PMC members</p>
-</li>
-
-         
-<li> 
-<strong>New Committer</strong>
-
-            
-<p>When a new committer is proposed for the project</p>
-
-            
-<p>Consensus approval of active PMC members</p>
-</li>
-
-         
-<li> 
-<strong>New PMC Member</strong>
-
-            
-<p>When a committer is proposed for the PMC</p>
-
-            
-<p>Consensus approval of active PMC members</p>
-</li>
-
-         
-<li> 
-<strong>Branch Committer Removal</strong>
-
-            
-<p>When removal of commit privileges is sought <strong>or</strong>
-               when the branch is merged to the mainline</p>
-
-            
-<p>Lazy 2/3 majority of active PMC members</p>
-</li>
-
-         
-<li> 
-<strong>Committer Removal</strong>
-
-            
-<p>When removal of commit privileges is sought.  Note: Such
-            actions will also be referred to the ASF board by the PMC
-            chair</p>
-
-            
-<p>Lazy 2/3 majority of active PMC members (excluding the
-            committer in question if a member of the PMC).</p>
-</li>
-
-         
-<li> 
-<strong>PMC Member Removal</strong>
-
-            
-<p>When removal of a PMC member is sought.  Note: Such
-            actions will also be referred to the ASF board by the PMC
-            chair.</p>
-
-            
-<p>Lazy 2/3 majority of active PMC members (excluding the member
-            in question)</p>
-</li>
-
-         
-<li> 
-<strong>Modifying Bylaws</strong>
-
-            
-<p>Modifying this document.</p>
-
-            
-<p>Lazy majority of active PMC members</p>
-</li>
-         
-</ul>
-</li>
-
-   
-<li> 
-<strong>Voting Timeframes</strong>
-
-        
-<p>Votes are open for a period of 7 days to allow all active
-        voters time to consider the vote. Votes relating to code
-        changes are not subject to a strict timetable but should be
-        made as timely as possible.</p>
-    
-         
-<ul>
-         
-<li> 
-<strong>Product Release - Vote Timeframe</strong>
-           
-<p>Release votes, alone, run for a period of 5 days. All other 
-             votes are subject to the above timeframe of 7 days.</p>
-         
-</li>
-       
-</ul>
-   
-</li>
-
-   
-</ul>
-</div>
-
-</div>
-<!--+
-    |end content
-    +-->
-<div class="clearboth">&nbsp;</div>
-</div>
-<div id="footer">
-<!--+
-    |start bottomstrip
-    +-->
-<div class="lastmodified">
-<script type="text/javascript"><!--
-document.write("Last Published: " + document.lastModified);
-//  --></script>
-</div>
-<div class="copyright">
-        Copyright &copy;
-         2014 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
-<br>
-              Apache Hadoop, Hadoop, Apache, the Apache feather logo, and the Apache
-              Hadoop project logo are either registered trademarks or trademarks of
-              the Apache Software Foundation in the United States and other
-              countries.
-            </div>
-<!--+
-    |end bottomstrip
-    +-->
-</div>
-</body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<meta content="Apache Forrest" name="Generator">
+<meta name="Forrest-version" content="0.9">
+<meta name="Forrest-skin-name" content="hadoop-pelt">
+<title>Apache Hadoop Project Bylaws</title>
+<link type="text/css" href="skin/basic.css" rel="stylesheet">
+<link media="screen" type="text/css" href="skin/screen.css" rel="stylesheet">
+<link media="print" type="text/css" href="skin/print.css" rel="stylesheet">
+<link type="text/css" href="skin/profile.css" rel="stylesheet">
+<script src="skin/getBlank.js" language="javascript" type="text/javascript"></script><script src="skin/getMenu.js" language="javascript" type="text/javascript"></script><script src="skin/fontsize.js" language="javascript" type="text/javascript"></script>
+<link rel="shortcut icon" href="images/favicon.ico">
+<script type="text/javascript">
+
+  var _gaq = _gaq || [];
+  _gaq.push(['_setAccount', 'UA-7453027-1']);
+  _gaq.push(['_setDomainName', 'apache.org']);
+  _gaq.push(['_trackPageview']);
+
+  (function() {
+    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+  })();
+
+        </script>
+</head>
+<body onload="init()">
+<script type="text/javascript">ndeSetTextSize();</script>
+<div id="top">
+<!--+
+    |breadtrail
+    +-->
+<div class="breadtrail">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://hadoop.apache.org/">Hadoop</a><script src="skin/breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
+</div>
+<!--+
+    |header
+    +-->
+<div class="header">
+<!--+
+    |start group logo
+    +-->
+<div class="grouplogo">
+<a href="http://www.apache.org"><img class="logoImage" alt="Apache" src="images/apache_feather.gif" title="Apache Software Foundation"></a>
+</div>
+<!--+
+    |end group logo
+    +-->
+<!--+
+    |start Project Logo
+    +-->
+<div class="projectlogo">
+<a href="http://hadoop.apache.org/"><img class="logoImage" alt="Hadoop" src="images/hadoop-logo.jpg" title="Scalable Distributed Computing"></a>
+</div>
+<!--+
+    |end Project Logo
+    +-->
+<!--+
+    |start Search
+    +-->
+<div class="searchbox">
+<form action="http://search-hadoop.com/" method="get">
+<input onFocus="getBlank (this, 'Search with Apache Solr');" size="25" name="q" id="query" type="text" value="Search with Apache Solr">&nbsp;
+		  <input value="Search" type="submit">
+</form>
+</div>
+<!--+
+    |end search
+    +-->
+<!--+
+    |start Tabs
+    +-->
+<ul id="tabs">
+<li class="current">
+<a class="selected" href="index.html">Top</a>
+</li>
+<li>
+<a class="unselected" href="http://wiki.apache.org/hadoop">Wiki</a>
+</li>
+</ul>
+<!--+
+    |end Tabs
+    +-->
+</div>
+</div>
+<div id="main">
+<div id="publishedStrip">
+<!--+
+    |start Subtabs
+    +-->
+<div id="level2tabs"></div>
+<!--+
+    |end Endtabs
+    +-->
+<script type="text/javascript"><!--
+document.write("Last Published: " + document.lastModified);
+//  --></script>
+</div>
+<!--+
+    |breadtrail
+    +-->
+<div class="breadtrail">
+
+             &nbsp;
+           </div>
+<!--+
+    |start Menu, mainarea
+    +-->
+<!--+
+    |start Menu
+    +-->
+<div id="menu">
+<div onclick="SwitchMenu('menu_selected_1.1', 'skin/')" id="menu_selected_1.1Title" class="menutitle" style="background-image: url('skin/images/chapter_open.gif');">About</div>
+<div id="menu_selected_1.1" class="selectedmenuitemgroup" style="display: block;">
+<div class="menuitem">
+<a href="index.html">Welcome</a>
+</div>
+<div class="menuitem">
+<a href="releases.html">Releases</a>
+</div>
+<div class="menuitem">
+<a href="mailing_lists.html">Mailing Lists</a>
+</div>
+<div class="menuitem">
+<a href="issue_tracking.html">Issue Tracking</a>
+</div>
+<div class="menuitem">
+<a href="who.html">Who We Are?</a>
+</div>
+<div class="menuitem">
+<a href="http://wiki.apache.org/hadoop/PoweredBy">Who Uses Hadoop?</a>
+</div>
+<div class="menuitem">
+<a href="http://www.cafepress.com/hadoop/">Buy Stuff</a>
+</div>
+<div class="menuitem">
+<a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
+</div>
+<div class="menuitem">
+<a href="http://www.apache.org/foundation/thanks.html">Thanks</a>
+</div>
+<div class="menuitem">
+<a href="privacy_policy.html">Privacy Policy</a>
+</div>
+<div class="menupage">
+<div class="menupagetitle">Bylaws</div>
+<div class="menupageitemgroup">
+<div class="menupageitem">
+<a href="#Introduction">Introduction</a>
+</div>
+<div class="menupageitem">
+<a title="Roles and Responsibilities" href="#Roles+and+Responsibilities">Roles and Responsib...</a>
+</div>
+<div class="menupageitem">
+<a href="#Decision+Making">Decision Making</a>
+</div>
+</div>
+</div>
+<div class="menuitem">
+<a href="http://www.apache.org/licenses/">License</a>
+</div>
+</div>
+<div onclick="SwitchMenu('menu_1.2', 'skin/')" id="menu_1.2Title" class="menutitle">Documentation</div>
+<div id="menu_1.2" class="menuitemgroup">
+<div class="menuitem">
+<a href="http://hadoop.apache.org/docs/current/">Current</a>
+</div>
+<div class="menuitem">
+<a href="http://hadoop.apache.org/docs/stable/">Stable</a>
+</div>
+<div class="menuitem">
+<a href="http://hadoop.apache.org/docs/r1.2.1/">Release 1.2.1</a>
+</div>
+<div class="menuitem">
+<a href="http://hadoop.apache.org/docs/r2.5.2/">Release 2.5.2</a>
+</div>
+<div class="menuitem">
+<a href="http://hadoop.apache.org/docs/r2.6.4/">Release 2.6.4</a>
+</div>
+<div class="menuitem">
+<a href="http://hadoop.apache.org/docs/r0.23.11/">Release 0.23.11</a>
+</div>
+<div class="menuitem">
+<a href="http://hadoop.apache.org/docs/r2.7.2/">Release 2.7.2</a>
+</div>
+</div>
+<div onclick="SwitchMenu('menu_1.3', 'skin/')" id="menu_1.3Title" class="menutitle">Related Projects</div>
+<div id="menu_1.3" class="menuitemgroup">
+<div class="menuitem">
+<a href="http://incubator.apache.org/ambari/">Ambari</a>
+</div>
+<div class="menuitem">
+<a href="http://avro.apache.org/">Avro</a>
+</div>
+<div class="menuitem">
+<a href="http://cassandra.apache.org/">Cassandra</a>
+</div>
+<div class="menuitem">
+<a href="http://incubator.apache.org/chukwa/">Chukwa</a>
+</div>
+<div class="menuitem">
+<a href="http://incubator.apache.org/hama/">Hama</a>
+</div>
+<div class="menuitem">
+<a href="http://hbase.apache.org/">HBase</a>
+</div>
+<div class="menuitem">
+<a href="http://hive.apache.org/">Hive</a>
+</div>
+<div class="menuitem">
+<a href="http://mahout.apache.org/">Mahout</a>
+</div>
+<div class="menuitem">
+<a href="http://pig.apache.org/">Pig</a>
+</div>
+<div class="menuitem">
+<a href="http://spark.incubator.apache.org/">Spark</a>
+</div>
+<div class="menuitem">
+<a href="http://tez.incubator.apache.org/">Tez</a>
+</div>
+<div class="menuitem">
+<a href="http://zookeeper.apache.org/">ZooKeeper</a>
+</div>
+</div>
+<div id="credit"></div>
+<div id="roundbottom">
+<img style="display: none" class="corner" height="15" width="15" alt="" src="skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
+<!--+
+  |alternative credits
+  +-->
+<div id="credit2"></div>
+</div>
+<!--+
+    |end Menu
+    +-->
+<!--+
+    |start content
+    +-->
+<div id="content">
+<div title="Portable Document Format" class="pdflink">
+<a class="dida" href="bylaws.pdf"><img alt="PDF -icon" src="skin/images/pdfdoc.gif" class="skin"><br>
+        PDF</a>
+</div>
+<h1>Apache Hadoop Project Bylaws</h1> 
+
+    
+<a name="N1000D"></a><a name="Introduction"></a>
+<h2 class="h3">Introduction</h2>
+<div class="section">
+<p>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.</p>
+<p>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.</p>
+<p>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.</p>
+</div>
+
+   
+<a name="N10028"></a><a name="Roles+and+Responsibilities"></a>
+<h2 class="h3">Roles and Responsibilities</h2>
+<div class="section">
+<p>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</p>
+<ul>
+   
+<li> 
+<strong>Users</strong>
+
+        
+<p>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.</p>
+
+        
+<p> 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.</p>
+</li>
+
+   
+<li> 
+<strong>Contributors</strong>
+
+        
+<p>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.</p>
+</li>
+
+   
+<li> 
+<strong>Committers</strong>
+
+        
+<p>The project's Committers are responsible for the project's
+        technical management. Committers have access to all subproject
+        subversion repositories. Committers may cast binding votes on
+        any technical discussion regarding any subproject.</p>
+
+        
+<p>Committer access is by invitation only and must be approved by
+        consensus approval 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
+        consensus approval of active PMC members.</p>
+
+        
+<p>Significant, pervasive features are often developed in a speculative
+        branch of the repository. The PMC may grant commit rights on the
+        branch to its consistent contributors, while the initiative is active.
+        Branch committers are responsible for shepherding their feature into
+        an active release and do not cast binding votes or vetoes in the
+        project.</p>
+
+        
+<p>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</p>
+
+        
+<p>A committer who makes a sustained contribution to the project
+        may be invited to become a member of the PMC. The form of
+        contribution is not limited to code. It can also include code
+        review, helping out users on the mailing lists, documentation,
+        testing, etc.</p>
+</li>
+
+   
+<li> 
+<strong>Release Manager</strong>
+
+        
+<p>A Release Manager (RM) is a committer who volunteers to produce 
+	a Release Candidate according to <a href="https://wiki.apache.org/hadoop/HowToRelease">HowToRelease</a>.
+	The RM shall publish a Release Plan on the <em>common-dev@</em> 
+	list stating the branch from which they intend to make a Release 
+	Candidate, at least one week before they do so. The RM is responsible 
+	for building consensus around the content of the Release Candidate, 
+	in order to achieve a successful Product Release vote.</p>
+</li>
+
+   
+<li> 
+<strong>Project Management Committee</strong>
+
+        
+<p>The Project Management Committee (PMC) for Apache Hadoop was
+        created by the Apache Board in January 2008 when Hadoop moved
+        out of Lucene and became a top level project at Apache. The
+        PMC is responsible to the board and the ASF for the management
+        and oversight of the Apache Hadoop codebase. The
+        responsibilities of the PMC include</p>
+
+        
+<ul>
+        
+<li> Deciding what is distributed as products of the Apache Hadoop
+        project.  In particular all releases must be approved by the
+        PMC</li>
+
+        
+<li> Maintaining the project's shared resources, including the codebase
+             repository, mailing lists, websites.</li>
+
+        
+<li> Speaking on behalf of the project.</li>
+
+        
+<li> Resolving license disputes regarding products of the project</li>
+
+        
+<li> Nominating new PMC members and committers</li>
+
+        
+<li> Maintaining these bylaws and other guidelines of the project</li>
+        
+</ul>
+
+        
+<p>Membership of the PMC is by invitation only and must be
+        approved by a consensus approval of active PMC members. A PMC
+        member is considered "emeritus" by their own
+        declaration or by not contributing in any form to the project
+        for over six months. An emeritus member may request
+        reinstatement to the PMC. Such reinstatement is subject to
+        consensus approval of the active PMC members.</p>
+
+        
+<p>The chair of the PMC is appointed by the ASF board. The chair
+        is an office holder of the Apache Software Foundation (Vice
+        President, Apache Hadoop) and has primary responsibility to
+        the board for the management of the projects within the scope
+        of the Hadoop PMC. The chair reports to the board quarterly on
+        developments within the Hadoop project.</p>
+
+	
+<p>The chair of the PMC is rotated annually. When the chair is
+	rotated or if the current chair of the PMC resigns, the PMC
+	votes to recommend a new chair using Single Transferable Vote
+	(STV) voting. See http://wiki.apache.org/general/BoardVoting
+	for specifics. The decision must be ratified by the Apache
+	board.</p>
+</li>
+   
+</ul>
+</div>
+
+
+<a name="N10094"></a><a name="Decision+Making"></a>
+<h2 class="h3">Decision Making</h2>
+<div class="section">
+<p>Within the Hadoop project, different types of decisions require
+      different forms of approval. For example, the 
+      <a href="#Roles+and+Responsibilities">previous section</a> 
+      describes several
+      decisions which require "consensus approval"
+      approval. This section defines how voting is performed, the
+      types of approvals, and which types of decision require which
+      type of approval.</p>
+<ul>
+      
+<li> 
+<strong>Voting</strong>
+
+      
+<p>Decisions regarding the project are made by votes on the
+      primary project development mailing list
+      (general@hadoop.apache.org).  Where necessary, PMC voting may
+      take place on the private Hadoop PMC mailing list.  Votes are
+      clearly indicated by subject line starting with [VOTE].  Votes
+      may contain multiple items for approval and these should be
+      clearly separated. Voting is carried out by replying to the
+      vote mail. Voting may take four flavors</p>
+
+        
+<ul>
+         
+<li> 
+<strong>+1</strong> "Yes," "Agree," or 
+              "the action 
+              should be performed." In general, this vote also indicates 
+              a willingness on the behalf of the voter in "making it 
+             happen"</li>
+
+         
+<li> 
+<strong>+0</strong> This vote indicates a willingness for the 
+              action under
+              consideration to go ahead. The voter, however will not be able
+              to help.</li>
+
+         
+<li> 
+<strong>-0</strong> This vote indicates that the voter does 
+              not, in general, 
+              agree with the proposed action but is not concerned enough to 
+              prevent the action going ahead.</li>
+
+         
+<li> 
+<strong>-1</strong> This is a negative vote. On issues where 
+              consensus is 
+              required, this vote counts as a <strong>veto</strong>. All 
+              vetoes must contain an explanation of why the veto is 
+              appropriate. Vetoes with no explanation are void. It may also 
+              be appropriate for a -1 vote to include an alternative course 
+              of action.</li>
+        
+</ul>
+
+        
+<p>All participants in the Hadoop project are encouraged to show their
+        agreement with or against a particular action by voting. For technical
+        decisions, only the votes of active committers are binding. Non binding
+        votes are still useful for those with binding votes to understand the
+        perception of an action in the wider Hadoop community. For PMC 
+        decisions, only the votes of PMC members are binding.</p>
+
+       
+<p>Voting can also be applied to changes made to the Hadoop codebase. 
+       These typically take the form of a veto (-1) in reply to the commit 
+       message sent when the commit is made.</p>
+</li>
+
+    
+<li> 
+<strong>Approvals</strong>
+
+        
+<p>These are the types of approvals that can be sought. Different 
+        actions require different types of approvals</p>
+
+        
+<ul>
+        
+<li> 
+<strong>Consensus Approval -</strong>
+             Consensus approval requires 3 binding +1 votes
+             and no binding vetoes.</li>
+
+        
+<li> 
+<strong>Lazy Consensus -</strong>
+             Lazy consensus requires no -1 votes ('silence gives assent').</li>
+
+        
+<li> 
+<strong>Lazy Majority - </strong>
+             A lazy majority vote requires 3 binding +1
+             votes and more binding +1 votes than -1 votes.</li>
+
+        
+<li> 
+<strong>Lazy 2/3 Majority -</strong>
+             Lazy 2/3 majority votes requires at
+             least 3 votes and twice as many +1 votes as -1 votes.</li>
+        
+</ul>
+</li>
+
+    
+<li> 
+<strong>Vetoes</strong>
+
+        
+<p>A valid, binding veto cannot be overruled. If a veto is cast,
+        it must be accompanied by a valid reason explaining the
+        reasons for the veto. The validity of a veto, if challenged,
+        can be confirmed by anyone who has a binding vote. This does
+        not necessarily signify agreement with the veto - merely that
+        the veto is valid.</p>
+
+        
+<p>If you disagree with a valid veto, you must lobby the person casting
+        the veto to withdraw their veto. If a veto is not withdrawn, any action
+        that has been vetoed must be reversed in a timely manner.</p>
+</li>
+
+    
+<li> 
+<strong>Actions</strong>
+
+        
+<p>This section describes the various actions which are undertaken 
+        within the project, the corresponding approval required for that 
+        action and those who have binding votes over the action.</p>
+
+         
+<ul>
+         
+<li> 
+<strong>Code Change</strong>
+
+            
+<p>A change made to a codebase of the project and committed
+            by a committer. This includes source code, documentation, website
+            content, etc.</p>
+
+            
+<p>Consensus approval of active committers, but with a minimum of
+            one +1. The code can be committed after the first +1, unless
+            the code change represents a merge from a branch, in which case
+            three +1s are required.</p>
+</li>
+
+         
+<li> 
+<strong>Product Release</strong>
+
+            
+<p>When a release of one of the project's products is ready, a 
+            vote is required to accept the release as an official release of
+            the project.</p>
+
+           
+<p>Lazy Majority of active PMC members</p>
+</li>
+
+         
+<li> 
+<strong>Adoption of New Codebase</strong>
+
+            
+<p>When the codebase for an existing, released product is to be
+            replaced with an alternative codebase. If such a vote fails to
+            gain approval, the existing code base will continue.</p>
+
+            
+<p>This also covers the creation of new sub-projects
+            within the project</p>
+
+            
+<p>Lazy 2/3 majority of PMC members</p>
+</li>
+
+         
+<li> 
+<strong>New Branch Committer</strong>
+
+            
+<p>When a branch committer is proposed for the PMC</p>
+
+            
+<p>Lazy consensus of active PMC members</p>
+</li>
+
+         
+<li> 
+<strong>New Committer</strong>
+
+            
+<p>When a new committer is proposed for the project</p>
+
+            
+<p>Consensus approval of active PMC members</p>
+</li>
+
+         
+<li> 
+<strong>New PMC Member</strong>
+
+            
+<p>When a committer is proposed for the PMC</p>
+
+            
+<p>Consensus approval of active PMC members</p>
+</li>
+
+         
+<li> 
+<strong>Branch Committer Removal</strong>
+
+            
+<p>When removal of commit privileges is sought <strong>or</strong>
+               when the branch is merged to the mainline</p>
+
+            
+<p>Lazy 2/3 majority of active PMC members</p>
+</li>
+
+         
+<li> 
+<strong>Committer Removal</strong>
+
+            
+<p>When removal of commit privileges is sought.  Note: Such
+            actions will also be referred to the ASF board by the PMC
+            chair</p>
+
+            
+<p>Lazy 2/3 majority of active PMC members (excluding the
+            committer in question if a member of the PMC).</p>
+</li>
+
+         
+<li> 
+<strong>PMC Member Removal</strong>
+
+            
+<p>When removal of a PMC member is sought.  Note: Such
+            actions will also be referred to the ASF board by the PMC
+            chair.</p>
+
+            
+<p>Lazy 2/3 majority of active PMC members (excluding the member
+            in question)</p>
+</li>
+
+         
+<li> 
+<strong>Modifying Bylaws</strong>
+
+            
+<p>Modifying this document.</p>
+
+            
+<p>Lazy majority of active PMC members</p>
+</li>
+         
+</ul>
+</li>
+
+   
+<li> 
+<strong>Voting Timeframes</strong>
+
+        
+<p>Votes are open for a period of 7 days to allow all active
+        voters time to consider the vote. Votes relating to code
+        changes are not subject to a strict timetable but should be
+        made as timely as possible.</p>
+    
+         
+<ul>
+         
+<li> 
+<strong>Product Release - Vote Timeframe</strong>
+           
+<p>Release votes, alone, run for a period of 5 days. All other 
+             votes are subject to the above timeframe of 7 days.</p>
+         
+</li>
+       
+</ul>
+   
+</li>
+
+   
+</ul>
+</div>
+
+</div>
+<!--+
+    |end content
+    +-->
+<div class="clearboth">&nbsp;</div>
+</div>
+<div id="footer">
+<!--+
+    |start bottomstrip
+    +-->
+<div class="lastmodified">
+<script type="text/javascript"><!--
+document.write("Last Published: " + document.lastModified);
+//  --></script>
+</div>
+<div class="copyright">
+        Copyright &copy;
+         2014 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+<br>
+              Apache Hadoop, Hadoop, Apache, the Apache feather logo, and the Apache
+              Hadoop project logo are either registered trademarks or trademarks of
+              the Apache Software Foundation in the United States and other
+              countries.
+            </div>
+<!--+
+    |end bottomstrip
+    +-->
+</div>
+</body>
+</html>



---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-commits-help@hadoop.apache.org


Mime
View raw message