Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (nike.apache.org: domain of billie.rinaldi@gmail.com
 designates 209.85.216.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGZGg1jeaEeC3uB6p4wGeykH7BT7=FChABJANym9A0cdJDh9hA@mail.gmail.com>
References: 
 <CAGHyZ6JXBNpgH8nrA_sE9ss8NXAE7Se_Ob=BuxZaFA098bg_2Q@mail.gmail.com>
	<CAF1jEfBeegbudwN0+0_LvdraoRxbfNff9t6ntvo72_=69UPy1w@mail.gmail.com>
	<CAGZGg1jeaEeC3uB6p4wGeykH7BT7=FChABJANym9A0cdJDh9hA@mail.gmail.com>
Date: Tue, 17 Jun 2014 12:26:05 -0700
Message-ID: 
 <CAF1jEfDB9r8wOpsWnbBSmzM1T7NyFY4pQ=vokX6VUTDjzk7Ntg@mail.gmail.com>
Subject: Re: moving rat to a profile?
From: Billie Rinaldi <billie.rinaldi@gmail.com>
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: multipart/alternative; boundary=001a11c151547806d804fc0d1d3d

--001a11c151547806d804fc0d1d3d
Content-Type: text/plain; charset=UTF-8

On Tue, Jun 17, 2014 at 12:14 PM, Michael Allen <michael@sqrrl.com> wrote:

> In my not so humble opinion, adding licenses to a small set of missing
> files really isn't that hard for a release manager (or other random
> committer) to do periodically.  On the other hand, the barrier that the RAT
> checks throw up to new developers is quite real, and quite annoying.
>

The problem is not the actual adding of licenses, but that this encourages
a lack of understanding of committer responsibilities.  From our bylaws,
"Under the terms of the CLA that all committers must sign, a committer's
primary responsibility is to ensure that all code committed to Apache
Accumulo is licensed appropriately and meets those criteria set forth in
the CLA (including both original works and patches committed on behalf of
other contributors)."  It doesn't matter if contributors check the license
headers, but committers should be checking them for every commit, not just
periodically or at release time.


>
>
>
>
> On Tue, Jun 17, 2014 at 3:09 PM, Billie Rinaldi <billie.rinaldi@gmail.com>
> wrote:
>
> > I'm not thrilled about turning it off by default.  How about putting it
> in
> > a profile that would be enabled by default, but could be disabled with a
> > flag for those who don't understand why it's failing?
> >
> >
> > On Tue, Jun 17, 2014 at 11:44 AM, Sean Busbey <busbey@cloudera.com>
> wrote:
> >
> > > I've had a few different new-to-Accumulo contributors recently run into
> > the
> > > issue of Rat failing the build after changing branches.
> > >
> > > I know we already have a warning about this[1], but AFAICT it's over
> the
> > > threshold for consumable information.
> > >
> > > Even after pointing people to the warning, the existing workaround
> > tripped
> > > up atleast one of them. Despite the warning about using "git clean,"
> the
> > > destruction of their local IDE changes were surprising.
> > >
> > > For contributions to Accumulo that aren't coming from committers, the
> Rat
> > > plugin seems much more likely to give a false positive than to catch an
> > > error. Additionally, whatever committer is reviewing the contribution
> > > should be checking for license compliance anyways.
> > >
> > > In the interests of reducing the surprise for new contributors, I'd
> like
> > to
> > > move our use of Rat to a profile that is only default enabled during a
> > > release run.
> > >
> > > The profile would still let those who want rat to run on every build to
> > > enable it and we could update the guide for handling new contributions
> to
> > > say committers should enable the rat profile to help guard against
> > errors.
> > >
> > > Any objections?
> > >
> > > [1]: http://accumulo.apache.org/source.html#running-a-build
> > >
> > > --
> > > Sean
> > >
> >
>
>
>
> --
>
> *Michael Allen*
> Security Architect | Sqrrl-----------------------------------130
> Prospect Street | Cambridge, MA 02139415.699.0106 | www.sqrrl.com
> -----------------------------------
>
> The information contained in this communication may be confidential,
> subject to legal privilege, or otherwise protected from disclosure,
> and is intended solely for the use of the intended recipient(s). If
> you are not the intended recipient of this communication, please
> destroy all copies in your possession, notify the sender that you have
> received this communication in error, and note that any review or
> dissemination of, or the taking of any action in reliance on, this
> communication is expressly prohibited.  Please note that sqrrl data,
> INC. reserves the right to intercept, monitor, and retain e-mail
> messages to and from its systems as permitted by applicable law.
>

--001a11c151547806d804fc0d1d3d--