[jira] [Commented] (TAMAYA-144) Ensure correct licensing for binary distribution
[ https://issues.apache.org/jira/browse/TAMAYA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990382#comment-15990382 ] ASF subversion and git services commented on TAMAYA-144: Commit 824bb9ffd539b49ebefba819dbb053c4f6ac69a3 in incubator-tamaya-site's branch refs/heads/master from [~hugo.hirsch] [ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-site.git;h=824bb9f ] TAMAYA-144: Add legal docs > Ensure correct licensing for binary distribution > > > Key: TAMAYA-144 > URL: https://issues.apache.org/jira/browse/TAMAYA-144 > Project: Tamaya > Issue Type: Bug > Components: API, Docs, Extensions >Affects Versions: 0.2-incubating >Reporter: Anatole Tresch >Assignee: Oliver B. Fischer > Labels: build, tamaya-required-03 > Fix For: 0.3-incubating > > Original Estimate: 24h > Remaining Estimate: 24h > > The binary LICENSE and NOTICE needs a little work [1], could you please fix > this for the next release. > - LICENSE is missing MIT licensed Asciidoctor and CodeRay (used in docs) > - The final jar contains a number of 3rd party licensed software that is not > mentioned in LICENSE/NOTICE. This includes Dropwizard (Apache license with > NOTICE file), Jackson Core, Databind and Annotations (Apache), Gogole Common > libs, Joda Time (Apache with NOTICE), Jackson Afterburner (Apache?), slf4j > (MIT), Logbock (EPL or GNU), Hibinate Validator (Apache), Glassfish (CDDL), > Sun Expression Language Reference Implementation (CDDL), snakeyaml (Apache), > Apache Commons, Jetty (Apache with NOTICE), Jersey (CDDL), H2K (CDDL), > Javassist (MPL or GPL), Metrics (Apache), argparse4j (MIT), Arquillian > (Apache?), Shrink-wrap (Apache?), JBoss Modules (Apache), JBoss logging > (Apache). > Most of this is Apache licensed, but there a few NOTICE files that may effect > your NOTICE [3] and there a couple of MIT licensed file. The CDDL / MPL > license software which need to treated carefully. [4] > I may of missed a couple and you may want to double check the JBoss logging > as at one point it was GPL not Apache licensed. > Thanks, > Justin > 1. http://www.apache.org/dev/licensing-howto.html#binary > 2. ./modules/server/lib/tamaya-server-0.2-incubating.jar > 3. http://www.apache.org/dev/licensing-howto.html#alv2-dep > 4. http://www.apache.org/legal/resolved.html#category-b -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TAMAYA-144) Ensure correct licensing for binary distribution
[ https://issues.apache.org/jira/browse/TAMAYA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990385#comment-15990385 ] ASF subversion and git services commented on TAMAYA-144: Commit 110b5566bd0dd7b6610fbba3fbee2d30e1de8111 in incubator-tamaya's branch refs/heads/master from [~hugo.hirsch] [ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;h=110b556 ] TAMAYA-144: Fix legal stuff. > Ensure correct licensing for binary distribution > > > Key: TAMAYA-144 > URL: https://issues.apache.org/jira/browse/TAMAYA-144 > Project: Tamaya > Issue Type: Bug > Components: API, Docs, Extensions >Affects Versions: 0.2-incubating >Reporter: Anatole Tresch >Assignee: Oliver B. Fischer > Labels: build, tamaya-required-03 > Fix For: 0.3-incubating > > Original Estimate: 24h > Remaining Estimate: 24h > > The binary LICENSE and NOTICE needs a little work [1], could you please fix > this for the next release. > - LICENSE is missing MIT licensed Asciidoctor and CodeRay (used in docs) > - The final jar contains a number of 3rd party licensed software that is not > mentioned in LICENSE/NOTICE. This includes Dropwizard (Apache license with > NOTICE file), Jackson Core, Databind and Annotations (Apache), Gogole Common > libs, Joda Time (Apache with NOTICE), Jackson Afterburner (Apache?), slf4j > (MIT), Logbock (EPL or GNU), Hibinate Validator (Apache), Glassfish (CDDL), > Sun Expression Language Reference Implementation (CDDL), snakeyaml (Apache), > Apache Commons, Jetty (Apache with NOTICE), Jersey (CDDL), H2K (CDDL), > Javassist (MPL or GPL), Metrics (Apache), argparse4j (MIT), Arquillian > (Apache?), Shrink-wrap (Apache?), JBoss Modules (Apache), JBoss logging > (Apache). > Most of this is Apache licensed, but there a few NOTICE files that may effect > your NOTICE [3] and there a couple of MIT licensed file. The CDDL / MPL > license software which need to treated carefully. [4] > I may of missed a couple and you may want to double check the JBoss logging > as at one point it was GPL not Apache licensed. > Thanks, > Justin > 1. http://www.apache.org/dev/licensing-howto.html#binary > 2. ./modules/server/lib/tamaya-server-0.2-incubating.jar > 3. http://www.apache.org/dev/licensing-howto.html#alv2-dep > 4. http://www.apache.org/legal/resolved.html#category-b -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Podling Report Reminder - May 2017
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 17 May 2017, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, May 03). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/May2017 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Regarding TAMAYA-144
John, I assume, "repackage" also applies to simple Maven dependencies? Take Dropwizard support in Parfait: https://github.com/performancecopilot/parfait/blob/master/parfait-dropwizard/pom.xml It references 2 libraries from Dropwizard. Doesn't even do a NOTICE file or something, just using it, like JSR 363 which is also used there. Regardless of how tedious you end up dealing with those things, the extension or integration modules for say Dropwizard or JodaTime, JSR 363 (both already are in Sandbox) and many others will require such dependencies. Maybe Tamaya "core" can reduce external dependencies, but the extension libraries can't. There are Apache projects like SIS (the most popular downstream user of JSR 275) where parts of the project are not even under the Apache license at all (I'm not even sure, if it's Open Source, but if so it is based on a proprietary license by some Oil, Gas and Energy standards body) and that also works fine for SIS ;-) It long left the incubator and seems to have quite an impressive number of contributors: http://sis.apache.org/team-list.html Werner On Sun, Apr 30, 2017 at 10:38 AM, Werner Keil wrote: > Same here. > > Werner > > > On Sun, Apr 30, 2017 at 6:19 AM, Anatole Tresch > wrote: > >> hi oliver >> >> mo is ok. when? it is a free day here in zh... >> best Anatole >> >> Am 30.04.2017 00:11 schrieb "Oliver B. Fischer" > >: >> >> > Hi all, >> > >> > I need someone to discuss https://issues.apache.org/jira >> /browse/TAMAYA-144. >> > We could do it during our regular hangout or separately on Monday. >> > >> > Ho would have time for it? >> > >> > Oliver >> > >> > >> > -- >> > N Oliver B. Fischer >> > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany >> > P +49 30 44793251 >> > M +49 178 7903538 >> > E o.b.fisc...@swe-blog.net >> > S oliver.b.fischer >> > J oliver.b.fisc...@jabber.org >> > X http://xing.to/obf >> > >> > >> > >
Re: Regarding TAMAYA-144
Same here. Werner On Sun, Apr 30, 2017 at 6:19 AM, Anatole Tresch wrote: > hi oliver > > mo is ok. when? it is a free day here in zh... > best Anatole > > Am 30.04.2017 00:11 schrieb "Oliver B. Fischer" >: > > > Hi all, > > > > I need someone to discuss https://issues.apache.org/ > jira/browse/TAMAYA-144. > > We could do it during our regular hangout or separately on Monday. > > > > Ho would have time for it? > > > > Oliver > > > > > > -- > > N Oliver B. Fischer > > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > > P +49 30 44793251 > > M +49 178 7903538 > > E o.b.fisc...@swe-blog.net > > S oliver.b.fischer > > J oliver.b.fisc...@jabber.org > > X http://xing.to/obf > > > > >
