Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMTypuvhdht04=rU+NMBdtfF=dhGsR82+xxEG7nvP4caZabYuA@mail.gmail.com>
References: <CAMTypuub8S+J5WYPqt8B9ke4TEJwduWVbaX-Ndcoa1aMeoasbQ@mail.gmail.com>
 <CAMTypuvhdht04=rU+NMBdtfF=dhGsR82+xxEG7nvP4caZabYuA@mail.gmail.com>
From: Lei Chang <chang.lei.cn@gmail.com>
Date: Mon, 22 May 2017 22:11:53 +0800
Message-ID: <CAE44UQfTUO6xFRNB_sR2RBpacri1zDZ_Z+fAjSiXT17jv7O-3Q@mail.gmail.com>
Subject: Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ
 2.2.0.0-incubating rpm binary release
To: dev <dev@hawq.incubator.apache.org>
Cc: Roman Shaposhnik <rshaposhnik@pivotal.io>
Content-Type: multipart/alternative; boundary="001a11477a0afcfbbc05501d7322"
archived-at: Mon, 22 May 2017 14:12:04 -0000

--001a11477a0afcfbbc05501d7322
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I think Option 2 is better, more clear.

Cheers
Lei


On Mon, May 22, 2017 at 10:15 AM, Ruilong Huo <rhuo@pivotal.io> wrote:

> Hi Roman,
>
> Please let us know if you get a chance to review this. Or someone else wh=
o
> can help on this? Thanks.
>
> Best regards,
> Ruilong Huo
>
> On Mon, May 15, 2017 at 3:12 PM, Ruilong Huo <rhuo@pivotal.io> wrote:
>
> > Hi Roman,
> >
> > Currently I am preparing LICENSE, NOTICE, and DISCLAIMER files for Apac=
he
> > HAWQ 2.2.0.0-incubating rpm binary release. The components of the binar=
y
> > package
> > <https://dist.apache.org/repos/dist/dev/incubator/hawq/
> 2.2.0.0-incubating.RC2/apache-hawq-rpm-2.2.0.0-incubating.tar.gz>
> > are as below:
> >
> > *> tar -xzvf apache-hawq-rpm-2.2.0.0-incubating.tar.gz; tree
> > hawq_rpm_packages*
> > hawq_rpm_packages
> > =E2=94=9C=E2=94=80=E2=94=80 apache-hawq-2.2.0.0-el7.x86_64.rpm
> > =E2=94=9C=E2=94=80=E2=94=80 apache-tomcat-7.0.62-el6.noarch.rpm
> > =E2=94=9C=E2=94=80=E2=94=80 hawq-ranger-plugin-2.2.0.0-1.el7.centos.noa=
rch.rpm
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-3.2.1.0-1.el6.noarch.rpm
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-hbase-3.2.1.0-1.el6.noarch.rpm
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-hive-3.2.1.0-1.el6.noarch.rpm
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-jdbc-3.2.1.0-1.el6.noarch.rpm
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-json-3.2.1.0-1.el6.noarch.rpm
> > =E2=94=94=E2=94=80=E2=94=80 pxf-service-3.2.1.0-1.el6.noarch.rpm
> >
> > Given the LICENSE, NOTICE, and DISCLAIMER for Apache HAWQ source in top
> > directory:
> >
> > *> tree incubator-hawq/*
> > incubator-hawq/
> > =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=94=E2=94=80=E2=94=80 NOTICE
> >
> > We plan to put LICENSE, NOTICE, and DISCLAIMER for binary release in a
> > dedicated directory named dist which under top directory. Then these
> files
> > will be copied to the rpm packages in packaging stage.
> >
> > Here are two options for the layout of the LICENSE, NOTICE, and
> DISCLAIMER
> > for the components:
> >
> > *Option 1: Combine the licenses of all the components into one LICENSE,
> > NOTICE, and DISCLAIMER respectively. For example:*
> >
> > *> cd $APACHE_HAWQ_TOP_DIR; tree dist*
> > dist
> > =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=94=E2=94=80=E2=94=80 NOTICE
> >
> > *Option 2: Keep the separated LICENSE, NOTICE, and DISCLAIMER for each =
of
> > the components. For example:*
> >
> > *> cd $APACHE_HAWQ_TOP_DIR; tree dist/*
> > dist/
> > =E2=94=9C=E2=94=80=E2=94=80 hawq
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 NOTICE
> > =E2=94=9C=E2=94=80=E2=94=80 pxf
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 NOTICE
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-hbase
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 NOTICE
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-hdfs
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 NOTICE
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-hive
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 NOTICE
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-jdbc
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 NOTICE
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-json
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 NOTICE
> > =E2=94=9C=E2=94=80=E2=94=80 pxf-service
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 NOTICE
> > =E2=94=9C=E2=94=80=E2=94=80 ranger-plugin
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> > =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> > =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 NOTICE
> > =E2=94=94=E2=94=80=E2=94=80 tomcat
> >     =E2=94=9C=E2=94=80=E2=94=80 DISCLAIMER
> >     =E2=94=9C=E2=94=80=E2=94=80 LICENSE
> >     =E2=94=94=E2=94=80=E2=94=80 NOTICE
> >
> > For option 1, it is easier to maintain the LICENSE, NOTICE, and
> DISCLAIMER
> > files. However, it contains all the licenses for all the components. Th=
us
> > it is hard to identify which component contains what licenses.
> >
> > For option 2, it needs extra maintenance effort. But, it is clear that
> > what are the licenses for each of the components.
> >
> > Would you please share you comments and let us know which is better?
> > Thanks.
> >
> > Best regards,
> > Ruilong Huo
> >
>

--001a11477a0afcfbbc05501d7322--