Re: [Question] LimitedInputStream license issue in Spark source.

2023-02-28 Thread Justin Mclean
Hi, The issue is not the original header it is the addition of the ASF header. The ASF header states "Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.” I ‘m not sure this is true with this file even though both Spark and this file are under the

Re: LICENSE and NOTICE file content

2018-06-23 Thread Justin Mclean
Hi, > The CDDL, CPL, MPL license lists and ALv2 headers at bottom. > > CDDL, CPL and MPL are Cat B (looking at > http://www.apache.org/legal/resolved.html#category-b here). The reciprocity > requires notice, and so I would think NOTICE is the right place? The listing > is to comply with this

Re: LICENSE and NOTICE file content

2018-06-23 Thread Justin Mclean
Hi, > Yes, there's just one set, and it's really for the binary distribution. See [1] it’s a good idea to have a different LICENSE and NOTICE for source and binary (and lots of other projects do this). > - License information is listed in NOTICE when it should be in LICENSE > > While I think I

Re: LICENSE and NOTICE file content

2018-06-21 Thread Justin Mclean
Hi, The PR was just for the LICENSE and NOTICE you still may want to look at the jar issue. Thanks, Justin - To unsubscribe e-mail: dev-unsubscr...@spark.apache.org

Re: LICENSE and NOTICE file content

2018-06-21 Thread Justin Mclean
Hi, Here you go [1]. That is however only for the source, re the connivance binary (which I’ve not checked) the LICENSE and NOTICE is very likely to be different. It turns out the Android project does have a NOTICE file and that had an effect on the spark one. Thanks, Justin 1. https://github

LICENSE and NOTICE file content

2018-06-21 Thread Justin Mclean
Hi, We’ve recently had a number of incubating projects copy your LICENSE and NOTICE files as they see Spark as a popular project and they are a little sad when the IPMC votes -1 on their releases. Now I'm not on your PMC, don’t know your projects history and there may be valid reasons for the

Re: Some minor LICENSE and NOTICE issues with 2.0 preview release

2016-06-02 Thread Justin Mclean
Hi, > It's a fair point that this would be better. I'll put it on my radar. Thanks for the consideration. If you need anything reviewed just ask. Justin - To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional

Re: Some minor LICENSE and NOTICE issues with 2.0 preview release

2016-06-02 Thread Justin Mclean
Hi, > My understanding of the trademark policy from discussions over the past > month is that software identifiers like Maven coordinates do not > strictly require 'apache’. Yes it's not required, but given the branding issues it may useful to do. >> - The year in the NOTICE file is out of date