Has anybody looked at the latest RC's LICENSE/NOTICE files.

[Roman Shaposhnik <ro...@shaposhnik.org>]

Hi!

given the latest round of IP related issues with the
RC I'm wondering whether the community members
who voted on the release have given a carful look to
LICENSE and NOTICE files.

Remember, guys -- this is NOT a job of IPMC, Justin,
myself or any other mentors to make sure that your
project doesn't violate licensing requirements. It is
YOUR job. More specifically it is a job for a future
PMC of Apache HAWQ (after graduation) and I surely
hope most of you will end up on that PMC.

And yes it means that you do have that additional responsibility
that has little to do with writing code and everything to do with
pretending to be a lawyer. This is just how responsible open
source works.

Please let me know if you need any guidance on how
to approach reviewing LICENSE and NOTICE files.

Thanks,
Roman.

Re: Has anybody looked at the latest RC's LICENSE/NOTICE files.

[Shivram Mani <sh...@gmail.com>]

Would help (especially for those who don't have prior history with apache
projects) to have a wiki containing a checklist of things prior to a +1 for
a release candidate

On Tue, Sep 20, 2016 at 9:20 AM, Ed Espino <es...@apache.org> wrote:

> Thanks for your guidance on this Roman.  I couldn't agree more that the IP
> responsibility falls on all members of the Apache HAWQ incubator
> community.  Especially for this initial "IP" focused release, it isn't
> enough to give "+1" based on building and testability.  Additionally, it
> goes beyond the LICENSE and NOTICE files.  The ASF compliance review
> process applies to every single file included in the project (now and in
> the future).
>
> Justin shared a variant of a script (important function is search_all in
> tarball attached) he uses for IP review of a project. We can add it to the
> project's wiki for others to possibly use.  The volume of output is large.
> It gives a sense of the scope of the IP review process we own as a
> community.
>
> Regards,
> -=e
>
> On Tue, Sep 20, 2016 at 8:15 AM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
>> Hi!
>>
>> given the latest round of IP related issues with the
>> RC I'm wondering whether the community members
>> who voted on the release have given a carful look to
>> LICENSE and NOTICE files.
>>
>> Remember, guys -- this is NOT a job of IPMC, Justin,
>> myself or any other mentors to make sure that your
>> project doesn't violate licensing requirements. It is
>> YOUR job. More specifically it is a job for a future
>> PMC of Apache HAWQ (after graduation) and I surely
>> hope most of you will end up on that PMC.
>>
>> And yes it means that you do have that additional responsibility
>> that has little to do with writing code and everything to do with
>> pretending to be a lawyer. This is just how responsible open
>> source works.
>>
>> Please let me know if you need any guidance on how
>> to approach reviewing LICENSE and NOTICE files.
>>
>> Thanks,
>> Roman.
>>
>
>
>
> --
> *Ed Espino*
> *espino@apache.org <es...@apache.org>*
>



-- 
shivram mani

Re: Has anybody looked at the latest RC's LICENSE/NOTICE files.

[Ed Espino <es...@apache.org>]

Thanks for your guidance on this Roman.  I couldn't agree more that the IP
responsibility falls on all members of the Apache HAWQ incubator
community.  Especially for this initial "IP" focused release, it isn't
enough to give "+1" based on building and testability.  Additionally, it
goes beyond the LICENSE and NOTICE files.  The ASF compliance review
process applies to every single file included in the project (now and in
the future).

Justin shared a variant of a script (important function is search_all in
tarball attached) he uses for IP review of a project. We can add it to the
project's wiki for others to possibly use.  The volume of output is large.
It gives a sense of the scope of the IP review process we own as a
community.

Regards,
-=e

On Tue, Sep 20, 2016 at 8:15 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:

> Hi!
>
> given the latest round of IP related issues with the
> RC I'm wondering whether the community members
> who voted on the release have given a carful look to
> LICENSE and NOTICE files.
>
> Remember, guys -- this is NOT a job of IPMC, Justin,
> myself or any other mentors to make sure that your
> project doesn't violate licensing requirements. It is
> YOUR job. More specifically it is a job for a future
> PMC of Apache HAWQ (after graduation) and I surely
> hope most of you will end up on that PMC.
>
> And yes it means that you do have that additional responsibility
> that has little to do with writing code and everything to do with
> pretending to be a lawyer. This is just how responsible open
> source works.
>
> Please let me know if you need any guidance on how
> to approach reviewing LICENSE and NOTICE files.
>
> Thanks,
> Roman.
>



-- 
*Ed Espino*
*espino@apache.org <es...@apache.org>*