Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of cnauroth@hortonworks.com
 designates 209.85.212.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAAD07OJ1q-c5eQBHRd=x1O+pp=260hCAj673jZWOdu7wfEzjTA@mail.gmail.com>
References: 
 <CACO5Y4z8UHhiBBkwCCbLawj2o0oe8iU0y9=bOwdqvWzcr+jojA@mail.gmail.com>
	<CABFz-zh_8QiCHprVjf7PBoZ7rZtZH-EYpf_QkkRvpv14WBaSxw@mail.gmail.com>
	<CAAD07OJ1q-c5eQBHRd=x1O+pp=260hCAj673jZWOdu7wfEzjTA@mail.gmail.com>
Date: Wed, 17 Jul 2013 10:31:16 -0700
Message-ID: 
 <CABCYYb9cBj1R6P3c523=FvJSoMFzGjY5O7MTmxHScAPP+b2jKA@mail.gmail.com>
Subject: Re: [DISCUSS] change bylaws to add "branch committers"
From: Chris Nauroth <cnauroth@hortonworks.com>
To: general@hadoop.apache.org
Content-Type: multipart/alternative; boundary=047d7b3a9016fd498204e1b8757f

--047d7b3a9016fd498204e1b8757f
Content-Type: text/plain; charset=ISO-8859-1

+1

This sounds like an effective way to get more people involved and get
people involved more deeply.  As a practical matter, I think at least one
full committer or PMC member should stay active in the feature branch to
provide guidance.  I expect this will help ease some of the challenges with
big merges when it comes time for the feature branch to merge back to trunk.

Chris Nauroth
Hortonworks
http://hortonworks.com/


On Tue, Jul 16, 2013 at 8:52 PM, Tsuyoshi OZAWA <ozawa.tsuyoshi@gmail.com>wrote:

> I agree with your proposal. If code tracking gets easier, it can
> reduce the reviewer's time and effort.
> +1(non-binding).
>
> On Wed, Jul 17, 2013 at 3:31 AM, Luke Lu <llu@apache.org> wrote:
> > Sounds good to me. This would encourage non-trivial code contribution and
> > maintenance.
> >
> > +1.
> >
> > Are we going to enforce branch ACLs (mostly to prevent mistakes)?
> >
> >
> >
> >
> > On Mon, Jul 15, 2013 at 4:10 PM, Chris Douglas <cdouglas@apache.org>
> 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
> >>
>
>
>
> --
> - Tsuyoshi
>

--047d7b3a9016fd498204e1b8757f--