Re: licenses and copyrights of dependencies

2018-11-08 Thread Justin Mclean
Hi, > @Justin I understand the need for this to be transitive but what if the > artifact has contracting licenses, e.g. as mentioned BSD-c2 vs BSD-c3? I > assume it is not our problem to figure this out but just put whatever is in > there in our LICENSE file?= I would probably put both in the

Re: licenses and copyrights of dependencies

2018-11-08 Thread Jonas Pfefferle
2018 12:43PM Subject: Re: licenses and copyrights of dependencies What Alex is saying makes sense. Whether you like it or not, you are creating a derived work (or something - I am not a lawyer), and that needs its own L On Nov 7, 2018, at 9:03 AM, Alex Harui wrote: IIRC, we use the

Re: licenses and copyrights of dependencies

2018-11-07 Thread Vincent S Hou
ulian Hyde wrote: - To: general@incubator.apache.org From: Julian Hyde Date: 11/07/2018 12:43PM Subject: Re: licenses and copyrights of dependencies What Alex is saying makes sense. Whether you like it or not, you are creating a derived work (or something - I am not a lawyer), and that needs

Re: licenses and copyrights of dependencies

2018-11-07 Thread Justin Mclean
Hi, > we need to include licenses of all components shipped in an artifact. The > example just appends all licenses to the LICENSE file including the > copyrights. Is the copyright required? If the license include it and the terms of the license say so then yes. This applied to common

Re: licenses and copyrights of dependencies

2018-11-07 Thread Julian Hyde
n. >> >> >> Best wishes. >> Vincent Hou (侯胜博) >> >> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, >> IBM Cloud >> >> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, >> Phone: +1(919)254-7182 >&g

Re: licenses and copyrights of dependencies

2018-11-07 Thread Alex Harui
nWhisk Contributor, Open Technology, >IBM Cloud > > Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, > Phone: +1(919)254-7182 > Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, >United States > > -----"Jon

Re: licenses and copyrights of dependencies

2018-11-07 Thread Jonas Pfefferle
S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States -"Jonas Pfefferle" wrote: - To: "general@incubator.apache.org" From: "Jonas Pfefferle" Date: 11/07/2018 07:35AM Su

Re: licenses and copyrights of dependencies

2018-11-07 Thread Vincent S Hou
efferle" wrote: - To: "general@incubator.apache.org" From: "Jonas Pfefferle" Date: 11/07/2018 07:35AM Subject: licenses and copyrights of dependencies Hi all, We are just preparing a new release and are wondering how and what is required for licenses and copyright

Re: licenses and copyrights of dependencies

2018-11-07 Thread Bertrand Delacretaz
Hi, On Wed, Nov 7, 2018 at 1:35 PM Jonas Pfefferle wrote: > ...Shouldn't the copyright be appended > to the NOTICE file instead?... Probably not - the NOTICE must be minimal as per http://www.apache.org/dev/licensing-howto.html we must only add "any *mandatory* legal notifications specific to

Re: licenses and copyrights of dependencies

2018-11-07 Thread Adrian Schuepbach
general@incubator.apache.org Date: 11/07/2018 01:52 PM Subject: Re: licenses and copyrights of dependencies Since we are only shipping jars and jars already include the licenses e.g. in META-INF or the pom file, we could refer to them in the NOTICE file instead of replicating them. Jonas

Re: licenses and copyrights of dependencies

2018-11-07 Thread Jonas Pfefferle
Since we are only shipping jars and jars already include the licenses e.g. in META-INF or the pom file, we could refer to them in the NOTICE file instead of replicating them. Jonas On Wed, 07 Nov 2018 13:35:04 +0100 "Jonas Pfefferle" wrote: Hi all, We are just preparing a new release

licenses and copyrights of dependencies

2018-11-07 Thread Jonas Pfefferle
Hi all, We are just preparing a new release and are wondering how and what is required for licenses and copyrights of components shipped with an artifact. According to the release policy http://www.apache.org/legal/release-policy.html#distribute-other-artifacts we need to include licenses