Thank you everyone for your valuable advice.
> so if you did want to avoid including the license in your
> releases you would either need to rely on the file as an external
> dependency or completely reimplement the functionality not deriving it from
> this file.
Including the BSD-3 style
I'm cancelling this vote due to licensing concerns found in [1].
1.
https://lists.apache.org/thread.html/r5a2954287e2db23a26c4a22880fea5beceb352af1a6fb2e8323d0cbc%40%3Cgeneral.incubator.apache.org%3E
--
Aaron Radzinski
On Fri, Jun 12, 2020 at 11:29 AM Aaron Radzinski
wrote:
> Hello all,
>
On 2020/06/14 01:31:11, Justin Mclean wrote:
> Hi,
>
> +1 (binding)
Thank you, Justin!
> - Unable to compile on OSX but assume that’s not a supported platform. It
> would be good to mention this in the README.
The build should work on macOS with the requirements listed in the README.
Hi,
I should be more clear. The 2 options in the case below is
1) Numpy License Headers Only
2) Apache Header with Numpy License Header
Re-reading my original reply does sound like I'm saying the Numpy
license should be removed in the case for the Apache License Headers
from the file. This
For clarity the "additional license" in this case is the Apache License
Header that a contributor added above the numpy license. I agree that
the original license should remain if the file is considered derived in
anyway. The podling was asking if they had authority to make the change
to remove
On Sat, Jun 13, 2020 at 2:19 PM Bob Paulin wrote:
> Hi,
>
> I agree there does not appear to be consensus on when it's appropriate to
> add Apache License Headers to Third Party code across projects. Here is
> Justin's email that request the Apache Headers removed [1]
>
>
>
> - file copyright
HI,
> * If there’s no any different opinion or objection, keep either origin
> Numpy license or ASF license but not dual, which depends on how MXNet’s
> source file evolves when the origin Numpy files changes?
IMO only if there are significant changes to the file, if in doubt I’d keep the
Hi Bob, Leonard,
Thanks for the elaboration/guideline on the dual license issue.
May I have the conclusion as below based on Bob’s direction/suggestion:
* If there’s no any different opinion or objection, keep either origin
Numpy license or ASF license but not dual, which depends on how
