Thanks, Alan. I have updated the PR (
https://github.com/apache/incubator-tephra/pull/60) with the suggested
changes.

Gokul

On Thu, Sep 14, 2017 at 2:59 PM, Alan Gates <[email protected]> wrote:

> +1
>
> Alan.
>
> On Thu, Sep 14, 2017 at 2:58 PM, Gokul Gunasekaran <[email protected]>
> wrote:
>
> > Hi Alan,
> >
> > From https://www.apache.org/legal/resolved.html#category-b, looks like
> EPL
> > license in binary should be alright.
> >
> > I will modify the PR to put the LICENSE_BINARY, NOTICE_BINARY and the
> > licenses directory under tephra-distribution directory. I will also
> remove
> > any references to LGPL/FindBugsJSR305 in those files. Also, I will add a
> > README in tephra-distribution directory that mentions that the
> dependencies
> > with the licenses mentioned in LICENSE/NOTICE/licenses will be included
> in
> > the distribution that will be generated when the user builds it manually
> > (and that the binary distribution is not distributed by Apache Tephra).
> >
> > Let me know if that sounds good to you.
> >
> > Thanks,
> > Gokul
> >
> > On Thu, Sep 14, 2017 at 2:40 PM, Alan Gates <[email protected]>
> wrote:
> >
> > > Ok, so I think you are saying all of these licenses only apply to the
> > > binary release.  I am skeptical about packaging LGPL even in a binary
> > > release and would want input from those more steeped in Apache rules
> than
> > > me.  But the others are ok once combined with the stuff in the
> > > tephra-distribution directory.  I’d just combine the licenses directory
> > > with that directory and perhaps include a README so it’s clear how the
> > > pieces fit together.
> > >
> > > Alan.
> > >
> > > On Thu, Sep 14, 2017 at 2:34 PM, Andreas Neumann <[email protected]>
> > wrote:
> > >
> > > > Hi Alan,
> > > >
> > > > this is a pure source distribution, and it does not include binaries,
> > and
> > > > the top-level LICENSE file includes only the Apache license.
> > > >
> > > > However, we were advised in the previous release vote that we need to
> > > > include these licenses in the tephra-distribution directory. See here
> > for
> > > > reference:
> > > > http://mail-archives.apache.org/mod_mbox/incubator-
> > general/201705.mbox/%
> > > > 3CCAOqetn-BFk8uHj89Rix2ozJYfuZ9FidSH7xRj
> EvKJ%3Dr0YbJdtA%40mail.gmail.
> > > > com%3E
> > > >
> > > > How do you advise we address this? Any guidance would be appreciated.
> > > >
> > > > Thanks -Andreas.
> > > >
> > > > On Thu, Sep 14, 2017 at 12:41 PM, Alan Gates <[email protected]>
> > > wrote:
> > > >
> > > > > -1
> > > > >
> > > > > This code appears to contain some artifacts that are licensed under
> > > > > unnacceptable licenses.  Further, I could not find any guide
> > indicated
> > > > > which parts of the code are under which licenses.
> > > > >
> > > > > See https://www.apache.org/legal/resolved.html for a summary of
> > > allowed
> > > > > licenses.
> > > > >
> > > > > In the licenses directory there is a copy of the LGPL (which is not
> > > > allowed
> > > > > in an Apache release), the EPL (which is allowed only for binary
> > > > > artifacts), and Aopa.PL, which appears to be putting all the code
> > into
> > > > the
> > > > > public domain (IANAL, so I might be reading it wrong).
> > > > >
> > > > > It’s possible the Aopa part is ok as long it only applies to code
> > > Tephra
> > > > is
> > > > > using.  The EPL might be ok if it’s only for binary artifacts.  I
> > don’t
> > > > > believe there is any way that the LGPL is ok.
> > > > >
> > > > > And a guide is needed to indicate which parts of the code are under
> > > which
> > > > > licenses so it is clear to anyone who downloads the code that these
> > > other
> > > > > licenses do not apply to the whole system.  See
> > > > > https://github.com/apache/hive/blob/master/LICENSE for an example.
> > > > >
> > > > > Alan.
> > > > >
> > > > > On Thu, Sep 14, 2017 at 9:00 AM, James Taylor <
> > [email protected]>
> > > > > wrote:
> > > > >
> > > > > > +1. Verified that all Phoenix unit tests pass with the RC.
> > > > > >
> > > > > > On Wed, Sep 13, 2017 at 8:31 PM Andreas Neumann <[email protected]
> >
> > > > wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > This is a call for a vote on releasing Apache Tephra
> > > > 0.13.0-incubating,
> > > > > > > release candidate 1. This is the sixth release of Tephra.
> > > > > > >
> > > > > > > The source tarball, including signatures, digests, etc. can be
> > > found
> > > > > at:
> > > > > > >
> > > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0.
> > > > > > 13.0-incubating-rc1/src
> > > > > > >
> > > > > > > The tag to be voted upon is v0.13.0-incubating:
> > > > > > >
> > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.
> > > > > > git;a=shortlog;h=refs/tags/v0.13.0-incubating
> > > > > > >
> > > > > > > The release hash is ae63ce233eb4b34eed03208322f17da941dee0f3:
> > > > > > >
> > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.
> > > > > > git;a=commit;h=ae63ce233eb4b34eed03208322f17da941dee0f3
> > > > > > >
> > > > > > > The Nexus Staging URL:
> > > > > > > https://repository.apache.org/content/repositories/
> > > > > orgapachetephra-1009
> > > > > > >
> > > > > > > Release artifacts are signed with the following key:
> > > > > > > http://people.apache.org/keys/committer/anew
> > > > > > >
> > > > > > > KEYS file available:
> > > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> > > > > > >
> > > > > > > For information about the contents of this release, see:
> > > > > > >
> > > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0.
> > > > > > 13.0-incubating-rc1/CHANGES.txt
> > > > > > >
> > > > > > > Please vote on releasing this package as Apache Tephra
> > > > > 0.13.0-incubating
> > > > > > >
> > > > > > > The vote will be open for 72 hours.
> > > > > > >
> > > > > > > [ ] +1 Release this package as Apache Tephra 0.13.0-incubating
> > > > > > > [ ] +0 no opinion
> > > > > > > [ ] -1 Do not release this package because ...
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Andreas
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to