Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of jon@cloudera.com designates
 209.85.212.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADcMMgGgQgCRBGihxdGjV_cCY4HRyCNCsd-n-QQ7z8gWjfDCug@mail.gmail.com>
References: 
 <CADcMMgGgQgCRBGihxdGjV_cCY4HRyCNCsd-n-QQ7z8gWjfDCug@mail.gmail.com>
From: Jonathan Hsieh <jon@cloudera.com>
Date: Fri, 14 Sep 2012 07:26:56 -0700
Message-ID: 
 <CAAha9a1RYkWy_E0_p59WHmYTSqtiUr2GPa1F8QOre1Qcpo5Gng@mail.gmail.com>
Subject: Re: Notes from yesterday's Contributors Pow Wow [WAS --> Re: HBase
 Developer's Pow-wow]
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7b66fb05852e3404c9aa38d2

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

On Wed, Sep 12, 2012 at 11:21 AM, Stack <stack@duboce.net> wrote:

>
> + Should there be more friction around committing?
>
> Suggestion that we try making lieutenants responsible for particular
> areas in the code base.  These folks would have to +1 anything that
> touches their area.  Formalize it in JIRA so these folks are
> auto-assigned issues when their component is chose.
>
> I think we had an escape hatch here -- +1 from one of the area experts or
two +1's from others outside the area.


> Lieutenants do not have to be committers, just someone interested in
> an area: e.g. Devaraj volunteered to look after rpc even though not
> committer.
>
> + Should each component have goals or at least a simple design posted;
> could help reviewing patches.
>
> + Who is going to do the all the work?
>
> Contributors?
>
>
-- 
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// jon@cloudera.com

--047d7b66fb05852e3404c9aa38d2--