On Mon, Jan 20, 2020 at 1:17 PM Lausen, Leonard
wrote:
> If I don't misremember, our mentor Markus Weimer suggested at KDD 2019 in a
> conversation that it's easiest to stop bundling non-ASF 3rdparty code.
You do not misremember :-) If possible, it is easiest for everyone
involved to capture the
Quote from Tianqi:
> The pro of doing so is that it indeed simplifies the release process, as
> these additional dependencies becomes category-B level dependencies as in
> https://www.apache.org/legal/resolved.html
Why would the dependencies become category-B level? It seems all licensing
consider
-1
I think is brittle to download a piece of source code that needs network
connectivity to build. The network is always in flux. Source archives that
need to download too many dependencies to build will end up broken with
time. I would expect source to build with a reasonable set of well known
sy
I agree with Tianqi. We may change our build system, but this won't free us
from the necessity to validate the licenses of our dependencies.
The question at this point is whether we are allowed to differentiate
between our main-source and hold it to the strict standards while treating
the third pa
I don't have an opinion, but would like to list pros and cons of doing so.
The pro of doing so is that it indeed simplifies the release process, as
these additional dependencies becomes category-B level dependencies as in
https://www.apache.org/legal/resolved.html
The con of doing so is that it b
+1
On Fri, Jan 17, 2020 at 1:59 PM Chris Olivier wrote:
> +1
>
> On Fri, Jan 17, 2020 at 10:19 AM Lausen, Leonard >
> wrote:
>
> > Dear MXNet community,
> >
> > as per recent mail on gene...@incubator.apache.org [1] there are a
> number
> > of
> > licensing issues in MXNet 1.6rc1. Based on anec
+1
On Fri, Jan 17, 2020 at 10:19 AM Lausen, Leonard
wrote:
> Dear MXNet community,
>
> as per recent mail on gene...@incubator.apache.org [1] there are a number
> of
> licensing issues in MXNet 1.6rc1. Based on anecdotal evidence I believe
> there
> has been no release so far without any licensi
Dear MXNet community,
as per recent mail on gene...@incubator.apache.org [1] there are a number of
licensing issues in MXNet 1.6rc1. Based on anecdotal evidence I believe there
has been no release so far without any licensing issues, which is a blocker to
MXNet graduating from it's incubating stat
