Thanks Roman for the heads up! I will start a discussion in dev list so that you can also help:)
Best regards, Ruilong Huo On Fri, May 5, 2017 at 1:42 AM, Roman Shaposhnik <[email protected]> wrote: > Hi Ruilong! > > its great to see that you've connected with Anthony -- his team has > the most extensive experience dealing > with a similar issue and can provide especially helpful feedback on > the Java side of things (C/C++ is > actually somewhat easier). > > Also, I saw your email on the general@ but you really should bring > this discussion back to dev@hawq. > I can chime in there as well. > > Thanks, > Roman. > > On Thu, May 4, 2017 at 4:44 AM, Ruilong Huo <[email protected]> wrote: > > Hi Anthony, > > > > Thank you so much for the descriptive information with perfect examples! > > > > We will read these materials and get back to you if there is more > concerns:) > > > > Regarding the Apache HAWQ 2.2.0.0 incubating release, it is great to have > > your review which, I believe, will help us a lot in many aspects. > > To make sure you can receive the vote email once the artifacts for the > > release is available and help to review, please subscribe hawq dev list > > ([email protected]) at > > http://hawq.incubator.apache.org/#mailing-lists if you are not in the > list > > yet. > > > > Just to confirm with you for the example of netty, it is not in the > LICENSE > > file since it is ASL 2.0 license, right? Thanks. > > > > Best regards, > > Ruilong Huo > > > > On Wed, May 3, 2017 at 10:26 PM, Anthony Baker <[email protected]> > wrote: > >> > >> Hi Ruilong, > >> > >> Please review these links: > >> > >> > >> https://cwiki.apache.org/confluence/display/GEODE/ > License+Guide+for+Contributors > >> https://nifi.apache.org/licensing-guide.html > >> > >> The contents of LICENSE and NOTICE for the binary distribution typically > >> includes the contents of LICENSE / NOTICE from the source release > (assuming > >> that the source dependencies are also bundled in the binary release) as > well > >> as the additional binaries you are are bundling. > >> > >> Developing the LICENSE contents is fairly straightforward (see those > links > >> above). Here an example of a source LICENSE vs the binary LICENSE: > >> > >> https://github.com/apache/geode/blob/develop/LICENSE > >> > >> https://github.com/apache/geode/blob/develop/geode- > assembly/src/main/dist/LICENSE > >> > >> For each new dependency, go to the project website and determine the > >> license. I don’t know of a good automation tool for this. I looked > into > >> some maven plugins but they weren’t sufficient for our needs. Here’s an > >> example dependency Geode uses: > >> > >> https://github.com/netty/netty/blob/4.1/LICENSE.txt > >> > >> The NOTICE file is a bit more complicated, though the approach is > similar. > >> Most of the complexity is because many downstream projects don’t follow > good > >> practices in their NOTICE. Here’s the Geode NOTICE: > >> > >> > >> https://github.com/apache/geode/blob/develop/geode- > assembly/src/main/dist/NOTICE > >> > >> This specific section: > >> > >> Apache Log4j Core > >> ResolverUtil.java > >> Copyright 2005-2006 Tim Fennell > >> > >> > >> was propagated from this file which was embedded in > log4j-core-2.6.1.jar: > >> > >> > >> https://github.com/apache/logging-log4j2/blob/ > dbd2d252a1b4139a9bd9eb213c89f28498db6dcf/log4j-core/src/ > main/resources/META-INF/NOTICE > >> > >> Note that this process applies to *any* external binary you bundle in > your > >> distribution: jars, shared libs, etc. If you distribute any jars via > maven, > >> each of those jars should also include LICENSE / NOTICE. > >> > >> Let me know if you want to discuss further. I’d also be happy to review > >> your release. > >> > >> > >> Anthony > >> > >> > >> > >> > >> > >> On May 3, 2017, at 5:42 AM, Ruilong Huo <[email protected]> wrote: > >> > >> Hi Anthony, > >> > >> Thanks Ed for introducing you who might help us with generating contents > >> for LICENSE, and NOTICE files for apache hawq incubating binary release. > >> > >> This is Ruilong Huo from Pivotal HAWQ team and we need some guidance > from > >> you regarding how to generate contents for LICENSE and NOTICE for the > binary > >> release. Any comments are appreciated! > >> > >> We passed Apache HAWQ 2.2.0.0-incubating binary release PMC vote but > >> failed with IPMC vote. The major reason is that the binary rpm package > is > >> lack of LICENSE, NOTICE files. > >> > >> Please find below proposed steps for that and let us know if it is the > >> correct way or is there better ways to do that. Thanks. > >> > >> Step 1. Download apache hawq 2.2.0.0 incubating binary tarball: > >> 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 > >> > >> Step 2. Extract the rpm package for components from the tarball, which > >> basically contains hawq core (written by c/c++/java), pxf and ranger > >> (written by java) > >> > >> [gpadmin@localhost Downloads]$ ls -alt hawq_rpm_packages > >> -rw-r--r--. 1 gpadmin gpadmin 84083656 Apr 10 10:41 > >> apache-hawq-2.2.0.0-el7.x86_64.rpm > >> -rw-r--r--. 1 gpadmin gpadmin 8892442 Apr 10 10:41 > >> apache-tomcat-7.0.62-el6.noarch.rpm > >> -rw-r--r--. 1 gpadmin gpadmin 55353540 Apr 10 10:41 > >> hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm > >> -rw-r--r--. 1 gpadmin gpadmin 5668 Apr 10 10:41 > >> pxf-3.2.1.0-1.el6.noarch.rpm > >> -rw-r--r--. 1 gpadmin gpadmin 27034 Apr 10 10:41 > >> pxf-hbase-3.2.1.0-1.el6.noarch.rpm > >> -rw-r--r--. 1 gpadmin gpadmin 51142 Apr 10 10:41 > >> pxf-hdfs-3.2.1.0-1.el6.noarch.rpm > >> -rw-r--r--. 1 gpadmin gpadmin 68824 Apr 10 10:41 > >> pxf-hive-3.2.1.0-1.el6.noarch.rpm > >> -rw-r--r--. 1 gpadmin gpadmin 24724 Apr 10 10:41 > >> pxf-jdbc-3.2.1.0-1.el6.noarch.rpm > >> -rw-r--r--. 1 gpadmin gpadmin 18675 Apr 10 10:41 > >> pxf-json-3.2.1.0-1.el6.noarch.rpm > >> -rw-r--r--. 1 gpadmin gpadmin 227890 Apr 10 10:41 > >> pxf-service-3.2.1.0-1.el6.noarch.rpm > >> > >> Step 3. For the LICENSE of hawq core, pxf, and ranger binary, we add > below > >> contents based on the LICENSE in hawq core source tarball. > >> > >> 1) get the contents by extracting them from rpm. For example, rpm2cpio > >> hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm | cpio -div > >> > >> > >> ./hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch/usr/local/ > apache-hawq/ranger/lib/postgresql-9.1-901-1.jdbc4.jar > >> > >> ./hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch/usr/local/ > apache-hawq/ranger/lib/ranger-plugin-admin-2.2.0.0.jar > >> > >> ./hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch/usr/local/ > apache-hawq/ranger/plugin-service/lib/activation-1.1.jar > >> > >> ./hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch/usr/local/ > apache-hawq/ranger/plugin-service/lib/apacheds-i18n-2.0.0-M15.jar > >> > >> ./hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch/usr/local/ > apache-hawq/ranger/plugin-service/lib/apacheds-kerberos- > codec-2.0.0-M15.jar > >> > >> ./hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch/usr/local/ > apache-hawq/ranger/plugin-service/lib/api-asn1-api-1.0.0-M20.jar > >> > >> ./hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch/usr/local/ > apache-hawq/ranger/plugin-service/lib/api-util-1.0.0-M20.jar > >> > >> ./hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch/usr/local/ > apache-hawq/ranger/plugin-service/lib/asm-3.1.jar > >> > >> ./hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch/usr/local/ > apache-hawq/ranger/plugin-service/lib/avro-1.7.4.jar > >> ...... > >> > >> 2) check which license does each of the library jar use and add them to > >> the LICENSE file for binary release. > >> > >> Is there any tools can that show which license does each of the jar file > >> use or we can only do that by searching on the internet? Thanks. > >> > >> Best regards, > >> Ruilong Huo > >> > >> > > >
