Return-Path:
X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by minotaur.apache.org (Postfix) with SMTP id CCB6CC06D
for ;
Tue, 23 Jul 2013 05:28:46 +0000 (UTC)
Received: (qmail 4067 invoked by uid 500); 23 Jul 2013 05:28:44 -0000
Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org
Received: (qmail 3922 invoked by uid 500); 23 Jul 2013 05:28:39 -0000
Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: general@hadoop.apache.org
Delivered-To: mailing list general@hadoop.apache.org
Received: (qmail 3914 invoked by uid 99); 23 Jul 2013 05:28:38 -0000
Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 05:28:38 +0000
Received: from localhost (HELO mail-pb0-f41.google.com) (127.0.0.1)
(smtp-auth username cdouglas, mechanism plain)
by minotaur.apache.org (qpsmtpd/0.29) with ESMTP;
Tue, 23 Jul 2013 05:28:38 +0000
Received: by mail-pb0-f41.google.com with SMTP id rp16so8025627pbb.28
for ; Mon, 22 Jul 2013 22:28:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=GrKN9YwukF6mWuSW7Dh283C3pGXruOctnG7ln9zr47g=;
b=TXwftL/esl+SOSabZHhzwlhYKM3sTzhP2OPOF1nUvtMCKusOOkdJnXxZuY9BwzRTi0
L94/CAj9xHpx1aW9FVRZuilCHgw3DYRlScU3V5K0FxMbZTyRkQyDp6Hd0280E7KZiNOS
jPa/MwDOnBHBVrfPTq1DGAvyzlHB2s6ie6Am+j6bXpbW2/iS5CUf5+TGY4RtxQndT9Fu
2UXM0SZPsAUvO8MvbeKJckZf1F9dIllZrhKzqRHcTXRrcvJnQwLqh6Z21lDNAe2XFDOm
QMJVZhLSgWV2pMHSJbrkkd99fJwgpZqUsXsoqiKljlsFDnEzyXo7j0v82mO4q2QmZaJf
IZWw==
MIME-Version: 1.0
X-Received: by 10.68.170.227 with SMTP id ap3mr34219993pbc.194.1374557318260;
Mon, 22 Jul 2013 22:28:38 -0700 (PDT)
Received: by 10.68.74.40 with HTTP; Mon, 22 Jul 2013 22:28:38 -0700 (PDT)
In-Reply-To:
References:
Date: Mon, 22 Jul 2013 22:28:38 -0700
Message-ID:
Subject: Re: [DISCUSS] change bylaws to add "branch committers"
From: Chris Douglas
To: "general@hadoop.apache.org"
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Jul 16, 2013 at 11:31 AM, Luke Lu wrote:
> Are we going to enforce branch ACLs (mostly to prevent mistakes)?
On Mon, Jul 22, 2013 at 11:47 AM, Kihwal Lee wrote:
> When would a branch committer privilege terminate?
When the branch merges. If we used branch ACLs, that would be a
consequence, but it's a clear policy, either way. If a branch
contributor stays involved they're usually made into full committers,
so we probably don't need to manage ACLs too tightly.
I also agree with Chris and Eli's qualifications. The intent is to
support development of active features, not create a sandbox that will
never merge back.
I'll call a vote starting tomorrow on the following diff to the
bylaws, unless someone has modifications to the phrasing. -C
Index: main/author/src/documentation/
content/xdocs/bylaws.xml
===================================================================
--- main/author/src/documentation/content/xdocs/bylaws.xml
(revision 1505876)
+++ main/author/src/documentation/content/xdocs/bylaws.xml (working copy)
@@ -76,6 +76,13 @@
commit access from the PMC. Such reinstatement is subject to
consensus approval of active PMC members.
+ 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.
+
All Apache committers are required to have a signed Contributor
License Agreement (CLA) on file with the Apache Software
Foundation. There is a
+ Lazy Consensus -
+ Lazy consensus requires no -1 votes ('silence gives assent').
+
Lazy Majority -
A lazy majority vote requires 3 binding +1
votes and more binding +1 votes than -1 votes.
@@ -279,6 +289,12 @@
Lazy 2/3 majority of PMC members
+ New Branch Committer
+
+ When a branch committer is proposed for the PMC
+
+ Lazy consensus of active PMC members
+
New Committer
When a new committer is proposed for the project
@@ -291,6 +307,13 @@
Consensus approval of active PMC members
+ Branch Committer Removal
+
+ When removal of commit privileges is sought or
+ when the branch is merged to the mainline
+
+ Lazy 2/3 majority of active PMC members
+
Committer Removal
When removal of commit privileges is sought. Note: Such
On Mon, Jul 22, 2013 at 11:47 AM, Kihwal Lee wrote:
> When would a branch committer privilege terminate?
>
> -Kihwal
>
> On 7/18/13 11:31 AM, "Robert Evans" wrote:
>
>>I like the idea too. My only concern would be the load it would put on
>>INFRA to support this, but I don't see hundreds of new committers showing
>>up so I am +1 on it.
>>
>>--Bobby
>>
>>On 7/17/13 12:43 PM, "Eli Collins" wrote:
>>
>>>+1 sounds reasonable to me. There's an assumption that we won't
>>>release from feature branches, worth saying that explicitly.
>>>
>>>On Mon, Jul 15, 2013 at 4:10 PM, Chris Douglas
>>>wrote:
>>>> In some projects at the ASF, a PMC member can grant commit rights on a
>>>> feature branch to a contributor with minimal overhead. When developing
>>>> significant or pervasive features, collaboration across linked JIRAs
>>>> can be difficult for the contributors to maintain and for reviewers to
>>>> track. Since we already support this model of branched development for
>>>> Hadoop committers, extending it to newer members of the community
>>>> seems pretty natural.
>>>>
>>>> Given that many of the major feature branches in 2.1 included at least
>>>> one significant contributor without a write bit, this pattern is also
>>>> common enough to adjust our bylaws.
>>>>
>>>> In one possible protocol, a PMC member can propose a set of
>>>> contributors for a particular feature branch. If there is no NACK,
>>>> then those people are given a commit bit on the branch. Other
>>>> responsibilities for committers- such as reviewing patches, vetoing
>>>> changes in trunk, etc.- do not apply. The protocol on the branch
>>>> should not require explicit rules, but contributors should keep in
>>>> mind that our bylaws also require 3 +1s to merge the branch back;
>>>> creating a feature branch is not a promise to merge. One would also
>>>> expect proposed branch committers to have already written some code as
>>>> the base of the new branch.
>>>>
>>>> Thoughts? Modifications to the protocol? -C
>>
>