Hi Justin,
I have created 2 issues for MKL[1] and pybind[2].
For [1], I think we need to remove it. For [2] I have raised on legal via
JIRA[3].
Can we resolve these issues during the next release?
Thanks!
[1] https://github.com/apache/incubator-mxnet/issues/15544
[2] https://github.com/apache/
I am a mentor of Druid. I think that Druid is more than ready to graduate. They
have been operating according to the Apache Way for a long time, and they have
a vibrant community.
Good luck!
Julian
> On Jul 15, 2019, at 3:42 PM, Gian Merlino wrote:
>
> Hi all,
>
> Since Apache Druid (incub
Hi,
> These licenses are for using MKL (the full release) as BLAS library. This
> functionality is optional and is not enabled by default. MKL is not shipped
> in source code.
If none of the code is bundled in the release artefact why is it mentioned in
LICENSE? [1]
Thanks,
Justin
1. http://
These licenses are for using MKL (the full release) as BLAS library. This
functionality is optional and is not enabled by default. MKL is not shipped in
source code.
-sz
On 2019/07/15 22:39:14, Justin Mclean wrote:
> Hi,
>
> I was just taking at look at the release and noticed the LICENSE fi
Hi all,
Since Apache Druid (incubating) entered the incubator in early 2018, the
community has grown more diverse, moved to ASF infrastructure, and adopted
the Apache Way. The community's achievements include the following:
- Performed 5 releases with 4 different release managers
- Invited 10 new
Hi,
I was just taking at look at the release and noticed the LICENSE file includes
the "Intel® Simplified license” this includes this clause "No reverse
engineering, decompilation, or disassembly of this Software is permitted.” and
there's also a "Limited patent license” mentioned which may be
Hi,
Thanks for helping validate and vote the release. I have created follow up
issue in MXNet[1] to be resolved before next release.
I think we should add note and the original license, aslo tagged the
contributor for more history.
It would be great if other IPMC members could help with the vote,
+1 binding
checked signature/checksum/disclaimer
license seems very thorough but two possible clarifications are suggested
below (*)
ran `make lib/libmxnet.so` successfully (opencv was listed as an optional
dependency but it seemed to be needed for this to work)
ran `make scalapkg` to generate Sca
Very good point... I'm personally fine w/ anything. Let's avoid bike shedding :)
> On Jul 15, 2019, at 11:07 AM, David Jencks wrote:
>
> To me, v2 implies an improvement over its predecessor and an expectation that
> eventually it will universally replace said predecessor.
>
> Perhaps
> DISCL
To me, v2 implies an improvement over its predecessor and an expectation that
eventually it will universally replace said predecessor.
Perhaps
DISCLAIMER-b.txt
DISCLAIMER-x.txt
might avoid this implication?
David Jencks
Sent from my iPhone
> On Jul 15, 2019, at 7:40 AM, Jim Jagielski wrote:
> On Jul 13, 2019, at 9:49 PM, Craig Russell wrote:
>
> DISCLAIMER.txt for the current standard disclaimer and some other name for
> the new disclaimer.
>
This seems less confusing, I think. DISCLAIMERv2.txt for the other?
--
With no -1 votes being cast, this IP clearance vote passes by lazy consensus.
I'll update the IP clearance form [1] to include the result.
Roy
[1] https://incubator.apache.org/ip-clearance/celix-http-admin.html
On 2019/07/12 08:57:00, Roy Lenferink wrote:
> Hi all,
>
> Apache Celix received a
[
https://issues.apache.org/jira/browse/INCUBATOR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved INCUBATOR-241.
Resolution: Fixed
The code repo is transferred into Apache group.
> IP clearance for Se
13 matches
Mail list logo
