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: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: <53A09088.1010703@gmail.com>
References: 
 <CAGHyZ6JXBNpgH8nrA_sE9ss8NXAE7Se_Ob=BuxZaFA098bg_2Q@mail.gmail.com>
	<53A09088.1010703@gmail.com>
Date: Tue, 17 Jun 2014 15:05:14 -0400
Message-ID: 
 <CAGZGg1gGaYQi8PdvCqDRxzCSGXyNM=6aRHvzo0jfk5whuktrkQ@mail.gmail.com>
Subject: Re: moving rat to a profile?
From: Michael Allen <michael@sqrrl.com>
To: dev@accumulo.apache.org
Content-Type: multipart/alternative; boundary=001a1133c47ce189c004fc0cd2fc

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

I think a RAT profile makes a ton of sense.  I also think adding "Check new
files for licenses" within the patch review process for committers would go
along with that kind of change.

On Tue, Jun 17, 2014 at 3:01 PM, Josh Elser <josh.elser@gmail.com> wrote:

> I think I came to the same conclusion you outline here. It makes things
> harder for new contributors unnecessarily.
>
> I think activation rat as a part of the apache-release profile makes the
> most sense to me. While we don't want to commit incorrectly licensed files
> between releases, fixing it before we make the release is the very
> important part.
>
> Maybe we can recommend some sort of configuration via ~/.m2/settings.xml
> that devs could enable to always run RAT?
>
> - Josh
>
>
> On 6/17/14, 11:44 AM, Sean Busbey 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
>>
>>


-- 

*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.

--001a1133c47ce189c004fc0cd2fc--