hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ruilong Huo <r...@pivotal.io>
Subject Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ rpm binary release
Date Fri, 26 May 2017 15:11:24 GMT
Hi Roman,

Thanks for your feedback!

We will merge the license information for the C/C++ components and prepare
LICENSE and NOTICE files accordingly.

As for JSON in PXF which is incompatible with ASL v2, the fix is to replace
it with some library which is compatible or remove it?

Furthermore, Hongxu helped to get the license information for Ranger as
well and it turns out that there two dependencies with GPL license which is
also not compatible with ASL v2:

1. stax-api-1.0-2.jar (GPL): StAX is a standard XML processing API that
allows you to stream XML data from and to your application.

2. jaxb-impl-2.2.3-1.jar (CDDL 1.1 GPL 2.0): Old JAXB Runtime module.
Contains sources required for runtime processing.

They are actually directly required by hadoop common and thus is indirectly
required by HAWQ Ranger. They are bundled hawq binary during packaging with
maven. Further check in hadoop binary shows that they are bundled as well.
However, the LICENSE in hadoop binary does not include them. Would you
please shed some light on how to handle this case? Thanks.

Best regards,
Ruilong Huo

On Fri, May 26, 2017 at 10:11 AM, Roman Shaposhnik <roman@shaposhnik.org>

> On Tue, May 23, 2017 at 12:39 AM, Ruilong Huo <rhuo@pivotal.io> wrote:
> > Thanks Lei and Roman for the comments. Keeping the LICENSE and NOTICE
> files
> > separated for each hawq rpm package makes it clear to understand and
> > minimum maintenance effort.
> >
> > The DISCLAIMER is common for hawq components. However, we have separate
> > binary packages for different components, such hawq core, pxf, and
> ranger,
> > which means users might download and install them separately.
> > So, I would prefer that we have separate DISCLAIMER file for each of the
> > hawq rpm package.
> >
> > For now, we have identified the license information for hawq dependencies
> > and proposed the process to merge that information to LICENSE and NOTICE
> > files for hawq components. Can you review that and give your feedback
> > before we prepare these files for further review?
> I took a look at the spreadsheet and I think you're on exactly the right
> track.
> For C/C++ components I trust your evaluation. As for PXF -- I'd like to
> take
> a look at how they compose their JARs myself.
> Ed and I already identified one issues with PXF that would have to be
> fixed:
> json can't be used because of the "do no evil" license.
> > Also, can you please elaborate on the license management plugin and
> > documentation for them? Thanks.
> These are mostly useful for Java projects but here's what I had in mind:
>     https://github.com/hierynomus/license-gradle-plugin
>     http://www.mojohaus.org/license-maven-plugin/
>     https://github.com/pivotal/LicenseFinder
> Thanks,
> Roman.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message