Re: Worked LICENSE and NOTICE example

Hi, > Perhaps showing a negative example of a resource you then realize you > can't add, e.g. you find a picture on flickr.com that you want to > bundle, but it's classified as CC Non-Commercial; so you find one that > you CAN include instead, but need to provide attribution for it. Nice idea

Re: Worked LICENSE and NOTICE example

Hi, > I wondered why you did not mention file headers further (beyond for > inspecting licenses), as that is part of ASF policy (while not a legal > requirement for using the Apache license) Very good question, I was just focused on the license and notice and didn’t look at headers and it may

Re: Worked LICENSE and NOTICE example

Perhaps showing a negative example of a resource you then realize you can't add, e.g. you find a picture on flickr.com that you want to bundle, but it's classified as CC Non-Commercial; so you find one that you CAN include instead, but need to provide attribution for it. Also propagation of

Re: Worked LICENSE and NOTICE example

This is a great tutorial, thanks, Justin! Also good video editing. I wondered why you did not mention file headers further (beyond for inspecting licenses), as that is part of ASF policy (while not a legal requirement for using the Apache license) The example is very simple, but actually there

Re: Worked LICENSE and NOTICE example

> Feedback, spelling errors, legal corrections/queries etc etc all welcome. > Do people think this is useful and would they like to see more examples? > > Hi Justin, I think this is very helpful and I'd love to see more examples. I'm involved in a project in incubation now, and I am grateful for

Re: Worked LICENSE and NOTICE example

I can buy that, Justin. Starting to better communicate that knowledge is very much appreciated! On Fri, Jun 24, 2016 at 10:34 AM, Justin Mclean wrote: > Hi, > > > Someday a tool to codify this into a wizard like thing would be awesome. > :) > > IMO (and I know others

Re: Worked LICENSE and NOTICE example

Hi, > Someday a tool to codify this into a wizard like thing would be awesome. :) IMO (and I know others have different opinions) I don’t think that actually possible other than in simple cases. if you know the policy it’s reasonably obvious what needs to be done and a tool would not actually

Re: Worked LICENSE and NOTICE example

Such a pain point while finding your way and even having to add something later. Thanks for taking the time for this! Someday a tool to codify this into a wizard like thing would be awesome. :) On Thu, Jun 23, 2016 at 11:31 PM, Henry Saputra wrote: > Justin, > > Thank

Re: Worked LICENSE and NOTICE example

Justin, Thank you for putting this up. This is super helpful. - Henry On Thu, Jun 23, 2016 at 7:16 AM, Justin Mclean wrote: > Hi, > > At the last ApacheCon I was discussing with Marvin about some of the > issues around assembling license and notice files. One of the

Re: Worked LICENSE and NOTICE example

HI, > This gets tricky because something in category B won't be in the > source release, and thus should not be in the standard LICENSE/NOTICE. Correct and that why it's a good example to make - may be a few other examples first to cover other issues (propagation of NOTICE files for instance

Re: Worked LICENSE and NOTICE example

On Wed, Jun 22, 2016 at 11:49 PM, Justin Mclean wrote: Justin, thank you so much for pushing forward with this! > I could make an example with Category B licenses (weak copy left) > as I’ve not covered that yet. This gets tricky because something in category B won't

Re: Worked LICENSE and NOTICE example

+1 This is awesome, Justin. Thanks for making the time to put this together. Justin Mclean wrote: Hi, At the last ApacheCon I was discussing with Marvin about some of the issues around assembling license and notice files. One of the ideas we come up with was to have some worked examples. So

Re: Worked LICENSE and NOTICE example

Hi, On Thu, Jun 23, 2016 at 8:49 AM, Justin Mclean wrote: > > You can’t have a dependancy (other than optional) on or include non > permissive licenses like LGPL. Even if it’s an optional dependancy nothing > would go in NOTICE as it’s not bundled. > Right, non-bundled

Re: Worked LICENSE and NOTICE example

Hi, > Great idea, Justin! Thanks! I’m considering making several examples, perhaps a few other people can help me out? > What about including an example in the NOTICE about the inclusion of a > non-permissive 3rd party license (e.g., LGPL)? You can’t have a dependancy (other than optional) on

Re: Worked LICENSE and NOTICE example

Great idea, Justin! What about including an example in the NOTICE about the inclusion of a non-permissive 3rd party license (e.g., LGPL)? I can make a PR in case you find it relevant. On Thu, Jun 23, 2016 at 2:16 AM, Justin Mclean wrote: > Hi, > > At the last

Re: Worked LICENSE and NOTICE example

Hi Justin, This is the best guide to understand the topic. Thank you. Regards Ajay Yadava On Thu, Jun 23, 2016 at 11:25 AM, Jean-Baptiste Onofré wrote: > Hi Justin, > > great, really helpful ! > > Regards > JB > > > On 06/23/2016 02:16 AM, Justin Mclean wrote: > >> Hi, >> >>

Re: Worked LICENSE and NOTICE example

Hi Justin, great, really helpful ! Regards JB On 06/23/2016 02:16 AM, Justin Mclean wrote: Hi, At the last ApacheCon I was discussing with Marvin about some of the issues around assembling license and notice files. One of the ideas we come up with was to have some worked examples. So here

Re: Worked LICENSE and NOTICE example

Hi, > One question - do the other licenses (MIT/BSD) have to be copied as separate > files That is the preferred way as otherwise the LICENSE file can become too long if many licenses are involved. > or listing their content in LICENSE file is acceptable? That is also acceptable. If you have

Re: Worked LICENSE and NOTICE example

Justin - this is useful. Thank you. One question - do the other licenses (MIT/BSD) have to be copied as separate files or listing their content in LICENSE file is acceptable? On Jun 22, 2016, at 8:16 PM, Justin Mclean wrote: > Hi, > > At the last ApacheCon I was