Repository: impala
Updated Branches:
  refs/heads/asf-site 92dc30a60 -> 7df35849a


Remove inactivity and emeritus requirements.

http://www.apache.org/foundation/records/minutes/2013/board_minutes_2013_06_19.txt
notes:

"removal of a member of a PMC, except due to their death or
resignation, can be requested of the Board of Directors by the PMC
chairman or by formal decision of the PMC, but requires a decision by
the Board of Directors"

This patch removes the distinction between active and inactive,
removes the notion of emeritus status (which the ASF's official tools
do not support anyway), and notes that removing PMC members required
ASF board approval.

Impala welcomes contributions from community members, including ones
who have been inactive for a while.

Change-Id: Ie78780eff062c2a2e3acb5e1e2c78d5b6a13e5b4
Reviewed-on: http://gerrit.cloudera.org:8080/11407
Reviewed-by: Jim Apple <jbapple-imp...@apache.org>
Tested-by: Jim Apple <jbapple-imp...@apache.org>


Project: http://git-wip-us.apache.org/repos/asf/impala/repo
Commit: http://git-wip-us.apache.org/repos/asf/impala/commit/7df35849
Tree: http://git-wip-us.apache.org/repos/asf/impala/tree/7df35849
Diff: http://git-wip-us.apache.org/repos/asf/impala/diff/7df35849

Branch: refs/heads/asf-site
Commit: 7df35849af1b58911bb4b5f1b9bba844b74b6e2e
Parents: 92dc30a
Author: Jim Apple <jbapple-imp...@apache.org>
Authored: Fri Aug 31 17:43:24 2018 -0700
Committer: Jim Apple <jbapple-imp...@apache.org>
Committed: Tue Sep 25 11:31:30 2018 +0000

----------------------------------------------------------------------
 bylaws.html | 52 ++++++++++++++++++++++------------------------------
 1 file changed, 22 insertions(+), 30 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/impala/blob/7df35849/bylaws.html
----------------------------------------------------------------------
diff --git a/bylaws.html b/bylaws.html
index dfc1d2b..1eecd08 100644
--- a/bylaws.html
+++ b/bylaws.html
@@ -185,11 +185,7 @@ body {
             discussion.</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>
+            approval of the PMC members.</p>
 
             <p>Significant, pervasive features may be developed in a 
speculative branch
             of the repository. The PMC may grant commit rights on the branch 
to its
@@ -243,11 +239,7 @@ body {
             </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>
+            consensus approval of 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 
Impala) and
@@ -322,10 +314,10 @@ body {
 
             <p>All participants in the Impala 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 Impala community. For PMC decisions, only 
the votes of
-            PMC members are binding.</p>
+            decisions, only the votes of committers are binding. Non binding 
votes are
+            still useful for those with binding votes to understand the 
perception of an
+            action in the wider Impala community. For PMC decisions, only the 
votes of PMC
+            members are binding.</p>
           </li>
 
           <li>
@@ -387,7 +379,7 @@ body {
                 <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>
+                <p>Lazy Majority of PMC members</p>
               </li>
 
               <li>
@@ -397,7 +389,7 @@ body {
                 or release managers may create branches to test and stabilize 
release
                 candidates.</p>
 
-                <p>Lazy consensus of active PMC members</p>
+                <p>Lazy consensus of PMC members</p>
               </li>
 
               <li>
@@ -405,7 +397,7 @@ body {
 
                 <p>When a branch committer is proposed for the PMC</p>
 
-                <p>Lazy consensus of active PMC members</p>
+                <p>Lazy consensus of PMC members</p>
               </li>
 
               <li>
@@ -413,7 +405,7 @@ body {
 
                 <p>When a new committer is proposed for the project</p>
 
-                <p>Consensus approval of active PMC members</p>
+                <p>Consensus approval of PMC members</p>
               </li>
 
               <li>
@@ -421,7 +413,7 @@ body {
 
                 <p>When a committer is proposed for the PMC</p>
 
-                <p>Consensus approval of active PMC members</p>
+                <p>Consensus approval of PMC members</p>
               </li>
 
               <li>
@@ -430,7 +422,7 @@ body {
                 <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>
+                <p>Lazy 2/3 majority of PMC members</p>
               </li>
 
               <li>
@@ -439,17 +431,17 @@ body {
                 <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>
+                <p>Lazy 2/3 majority of 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>When removal of a PMC member is sought. Note: Such actions 
require
+                approval from the ASF board of directors.</p>
 
-                <p>Lazy 2/3 majority of active PMC members (excluding the 
member in
+                <p>Lazy 2/3 majority of PMC members (excluding the PMC member 
in
                 question)</p>
               </li>
 
@@ -458,7 +450,7 @@ body {
 
                 <p>Modifying this document.</p>
 
-                <p>Lazy majority of active PMC members</p>
+                <p>Lazy majority of PMC members</p>
               </li>
             </ul>
           </li>
@@ -466,10 +458,10 @@ body {
           <li>
             <strong>Voting Timeframes</strong>
 
-            <p>Votes are open for a period of 72 hours (excluding weekends in 
the
-            timezone of the person who called the vote) 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>
+            <p>Votes are open for a period of 72 hours (excluding weekends in 
the timezone
+            of the person who called the vote) to allow all 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>
           </li>
         </ul>
       </div>

Reply via email to