Re: Apache MXNet v1.4.0 release status

2019-01-08 Thread Qing Lan
t; > -Original Message- > From: Steffen Rochel [mailto:steffenroc...@gmail.com] > Sent: Tuesday, January 8, 2019 10:51 AM > To: dev@mxnet.incubator.apache.org > Subject: Re: Apache MXNet v1.4.0 release status > > Kellen and Tao - > ye

Re: [Announcement] New Committer - Roshani Nagmote

2019-01-08 Thread Steffen Rochel
Congratulation Roshani! On Tue, Jan 8, 2019 at 8:53 AM Qing Lan wrote: > Congrats Roshani! Great to have you here! > > -Qing > > > > > > > Congrats Roshani. Well deserved. > > > >> On Tue, Jan 8, 2019, 8:29 AM Marco de Abreu wrote: > >> > >> Great to have you on board, Roshani! > >> > >>

Re: [Announcement] New Committer - Roshani Nagmote

2019-01-08 Thread Qing Lan
Congrats Roshani! Great to have you here! -Qing > > > Congrats Roshani. Well deserved. > >> On Tue, Jan 8, 2019, 8:29 AM Marco de Abreu > >> Great to have you on board, Roshani! >> >> -Marco >> >> Am Di., 8. Jan. 2019, 15:18 hat Carin Meier >> geschrieben: >> >>> Please join me in

Re: [Announcement] New Committer - Roshani Nagmote

2019-01-08 Thread kellen sunderland
Congrats Roshani. Well deserved. On Tue, Jan 8, 2019, 8:29 AM Marco de Abreu Great to have you on board, Roshani! > > -Marco > > Am Di., 8. Jan. 2019, 15:18 hat Carin Meier > geschrieben: > > > Please join me in welcoming Roshani Nagmote as a new committer. > > > > She has been active in the

Re: [Announcement] New Committer - Roshani Nagmote

2019-01-08 Thread Marco de Abreu
Great to have you on board, Roshani! -Marco Am Di., 8. Jan. 2019, 15:18 hat Carin Meier geschrieben: > Please join me in welcoming Roshani Nagmote as a new committer. > > She has been active in the project for quite some time. She has managed the > 1.3.0 release as well as being involved

Re: Apache MXNet v1.4.0 release status

2019-01-07 Thread kellen sunderland
19 10:51 AM > To: dev@mxnet.incubator.apache.org > Subject: Re: Apache MXNet v1.4.0 release status > > Kellen and Tao - > yes, the understanding is that dependencies need to be considered and all > licences referenced to include in top level LICENSE file. > Appreciate your help with it. &g

RE: Apache MXNet v1.4.0 release status

2019-01-07 Thread Lv, Tao A
What should I do for the double headers in 3rdparty/mkldnn/src/cpu/xbyak/? -tao -Original Message- From: Steffen Rochel [mailto:steffenroc...@gmail.com] Sent: Tuesday, January 8, 2019 10:51 AM To: dev@mxnet.incubator.apache.org Subject: Re: Apache MXNet v1.4.0 release status Kellen

Re: Apache MXNet v1.4.0 release status

2019-01-07 Thread Steffen Rochel
Kellen and Tao - yes, the understanding is that dependencies need to be considered and all licences referenced to include in top level LICENSE file. Appreciate your help with it. Steffen On Mon, Jan 7, 2019 at 6:39 PM kellen sunderland < kellen.sunderl...@gmail.com> wrote: > Sorry to hear about

Re: Apache MXNet v1.4.0 release status

2019-01-07 Thread kellen sunderland
Sorry to hear about the licensing issues. I was following the general vote but I'm still lacking some clarity around what licenses in the onnx-trt repo need to be surfaced. I believe onnx-trt is MIT licensed, but it includes Onnx as a third party repo which then brings in dependencies with a

Re: [Annoucement] New Committer -- Iblis Lin

2019-01-07 Thread Tianqi Chen
Welcome Iblis! Thank you for making MXNet.jl awesome. Tianqi On Mon, Jan 7, 2019 at 9:47 AM Chiyuan Zhang wrote: > Welcome Iblis! Thank you very much for your hard work and continuous > efforts on the Julia branch lately! > > Best, > Chiyuan > > On Sat, Jan 5, 2019 at 12:13 PM Carin Meier

Re: [Annoucement] New Committer -- Iblis Lin

2019-01-07 Thread Chiyuan Zhang
Welcome Iblis! Thank you very much for your hard work and continuous efforts on the Julia branch lately! Best, Chiyuan On Sat, Jan 5, 2019 at 12:13 PM Carin Meier wrote: > Please join me in welcoming Iblis Lin as a new committer. > > He has been a long time contributor to the Julia package, is

Re: Julia Package Release Process

2019-01-07 Thread Iblis Lin
I put the note. I'm fine with leaving the issue tracker at that. On 1/8/19 1:28 AM, Chiyuan Zhang wrote: I just checked that I have ability to disable the issue tracker on dmlc/MXNet.jl. Iblis: let me know if you would like me to disable the issue (after you transferred active ones to mxnet

Re: Julia Package Release Process

2019-01-07 Thread Chiyuan Zhang
I just checked that I have ability to disable the issue tracker on dmlc/MXNet.jl. Iblis: let me know if you would like me to disable the issue (after you transferred active ones to mxnet main repo). Disabling issues makes the whole 'issues' tab disappear. I think we can also adopt clojure repo's

Re: Julia Package Release Process

2019-01-07 Thread Iblis Lin
Yes, I have them on main repo. But for MXNet.jl, I'm repo collaborator. Anyway, I'm browsing the issues and migrating some of them. On 1/8/19 12:46 AM, Chris Olivier wrote: Do you not have write permissions on mxnet repo? On Mon, Jan 7, 2019 at 6:13 AM iblis wrote: just found that I don't

Re: Julia Package Release Process

2019-01-07 Thread Chris Olivier
Do you not have write permissions on mxnet repo? On Mon, Jan 7, 2019 at 6:13 AM iblis wrote: > just found that I don't have the permission to transfer issues of > dmlc/MXNet.jl. > Could anyone help me on this? > > On 1/7/19 12:16 PM, iblis wrote: > > okay. > > Before disabling the issue

Re: Julia Package Release Process

2019-01-07 Thread Carin Meier
I think you need admin permissions on both repos to do that which might be problematic. Since it looks like there is just one recent open issue, can you replicate it on the main MXNet repo and have a link to the original issue? FWIW - When the Clojure package joined the main repo. I just put

Re: Julia Package Release Process

2019-01-07 Thread iblis
just found that I don't have the permission to transfer issues of dmlc/MXNet.jl. Could anyone help me on this? On 1/7/19 12:16 PM, iblis wrote: okay. Before disabling the issue tracker, I'm going to transfer the issue from MXNet.jl to main repo. (via

Re: [Annoucement] New Committer -- Iblis Lin

2019-01-07 Thread Hagay Lupesko
Congrats Iblis! On Sat, Jan 5, 2019 at 2:35 PM Steffen Rochel wrote: > Congratulation Ilbis! > > On Sat, Jan 5, 2019 at 1:45 PM Lin Yuan wrote: > > > Welcome Iblis, > > > > Great to see a good Julia support in MXNet! > > > > Lin > > > > On Sat, Jan 5, 2019 at 12:32 PM Marco de Abreu > >

Re: Julia Package Release Process

2019-01-06 Thread iblis
okay. Before disabling the issue tracker, I'm going to transfer the issue from MXNet.jl to main repo. (via https://help.github.com/articles/transferring-an-issue-to-another-repository/) On 1/7/19 12:17 AM, Chris Olivier wrote: +1 for disabling issue tracker and putting a note on original repo

Re: Julia Package Release Process

2019-01-06 Thread Chris Olivier
+1 for disabling issue tracker and putting a note on original repo (if it isn’t already there) that work/issue tracking has moved to mxnet (using julia label in github or Jira). m On Sun, Jan 6, 2019 at 1:19 AM iblis wrote: > Before PR #10149 got merged (Oct 5, 2018) into main repo, > julia

Re: soft relu gradient, is it correct?

2019-01-06 Thread Matthias Seeger
Hi Pedro, these are just helper functions, you need to check the operator. In this case, the function is the derivative as function of the *output*, which is cheaper to compute: y = log(1 + exp(x)) => dy/dx = 1/(1 + exp(-x)) = 1 - exp(-y) If you check all sorts of other ops, the same is the

Re: Julia Package Release Process

2019-01-06 Thread iblis
Before PR #10149 got merged (Oct 5, 2018) into main repo, julia code is developed and maintained in the separate repo -- dmlc/MXNet.jl. After that PR, there are no further development happened in dmlc/MXNet.jl. We work with the main repo now. But the original MXNet.jl repo is still there, it

Re: Julia Package Release Process

2019-01-05 Thread Chris Olivier
Curious: Why is the julia code maintained in a separate repo? I was under the impression that it was donated/permanently merged into the mxnet source tree. Does it work with other frameworks other than mxnet? On Sat, Jan 5, 2019 at 8:32 PM Iblis Lin wrote: > If there is trademark issue, how

Re: Julia Package Release Process

2019-01-05 Thread Iblis Lin
If there is trademark issue, how about this option: 3) transferring the MXNet.jl repo ownership from DMLC to Apache. On 1/6/19 6:45 AM, Justin Mclean wrote: Hi, 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl It's under DMLC. I have the committer bit of this repo.

Re: Julia Package Release Process

2019-01-05 Thread Iblis Lin
On 1/6/19 5:48 AM, Carin Meier wrote: Do you know of any other Julia Apache projects? Maybe we could look and see how they are doing it. well, seems no. -- Iblis Lin

Re: Julia Package Release Process

2019-01-05 Thread Justin Mclean
Hi, > 1) Reuse the old repo: https://github.com/dmlc/MXNet.jl > It's under DMLC. I have the committer bit of this repo. I'm not 100% sure that would be allowed from a branding/trademark perspective, any distribution owned by a 3rd party can't be called "Apache MXNet". > 2) A

Re: [Annoucement] New Committer -- Iblis Lin

2019-01-05 Thread Steffen Rochel
Congratulation Ilbis! On Sat, Jan 5, 2019 at 1:45 PM Lin Yuan wrote: > Welcome Iblis, > > Great to see a good Julia support in MXNet! > > Lin > > On Sat, Jan 5, 2019 at 12:32 PM Marco de Abreu > wrote: > > > Welcome Iblis, > > > > great to have you on board! > > > > -Marco > > > > Am Sa., 5.

Re: Julia Package Release Process

2019-01-05 Thread Justin Mclean
Hi, > I know there are some conditions under which Apache can distribute releases > downstream. Short version it's fine to distribute packages that consist of voted on ASF releases, but you are not allowed to create and distribute packages that contain un-released code. See also [1] Thanks,

Re: Julia Package Release Process

2019-01-05 Thread Carin Meier
Iblis, Thank you for your work in developing a release process for the Julia package. Thanks especially for explaining it in way that is approachable for others not familiar with the Julia dependency management system. I know there are some conditions under which Apache can distribute releases

Re: [Annoucement] New Committer -- Iblis Lin

2019-01-05 Thread Lin Yuan
Welcome Iblis, Great to see a good Julia support in MXNet! Lin On Sat, Jan 5, 2019 at 12:32 PM Marco de Abreu wrote: > Welcome Iblis, > > great to have you on board! > > -Marco > > Am Sa., 5. Jan. 2019, 21:13 hat Carin Meier > geschrieben: > > > Please join me in welcoming Iblis Lin as a new

Re: [Annoucement] New Committer -- Iblis Lin

2019-01-05 Thread Marco de Abreu
Welcome Iblis, great to have you on board! -Marco Am Sa., 5. Jan. 2019, 21:13 hat Carin Meier geschrieben: > Please join me in welcoming Iblis Lin as a new committer. > > He has been a long time contributor to the Julia package, is responsible > for bringing into the main MXNet repo, and is

Re: joining slack channel

2019-01-05 Thread Aaron Markham
On the left side, click Channels, then you will see a search option. Look for mxnet there. On Fri, Jan 4, 2019 at 6:45 PM Fehervari, Istvan wrote: > Thanks for the invite. I am new to Slack so this might be a noob question > but I only see the #general and #welcome channels in ASF. How do I

Re: joining slack channel

2019-01-04 Thread Fehervari, Istvan
Thanks for the invite. I am new to Slack so this might be a noob question but I only see the #general and #welcome channels in ASF. How do I join the #mxnet channel? Thanks a lot! Istvan On 1/4/19, 5:44 AM, "Aaron Markham" wrote: I sent you an invite. Cheers, Aaron On

RE: joining slack channel

2019-01-04 Thread Lv, Tao A
Invitation is sent to mue...@amazon.com. You can find mxnet in ASF channels. -Original Message- From: Muenz, Edison [mailto:mue...@amazon.com.INVALID] Sent: Friday, January 4, 2019 11:46 PM To: dev@mxnet.incubator.apache.org Subject: Re: joining slack channel Hi, can I get an invite

Re: joining slack channel

2019-01-04 Thread Muenz, Edison
Hi, can I get an invite to the Slack channel as well? From: Aaron Markham Sent: Friday, January 4, 2019 3:42 PM To: dev@mxnet.incubator.apache.org Subject: Re: joining slack channel I sent you an invite. Cheers, Aaron On Fri, Jan 4, 2019 at 1:12 PM

Re: joining slack channel

2019-01-04 Thread Aaron Markham
I sent you an invite. Cheers, Aaron On Fri, Jan 4, 2019 at 1:12 PM István Fehérvári wrote: > Please add me to the slack channel. > > Thank you, > Istvan >

Re: Running CI for doc changes

2019-01-04 Thread Aaron Markham
e green > >> circle here [3] (e.g. Python 3: CPU Win) represents a node. > >> > >> #1 would be your example use case. In case of a doc change, we would > skip > >> our unit test pipelines while the website pipeline would still be > >> executed. > >>

Re: Running CI for doc changes

2019-01-03 Thread István Fehérvári
3: CPU Win) represents a node. >> >> #1 would be your example use case. In case of a doc change, we would skip >> our unit test pipelines while the website pipeline would still be >> executed. >> #2 would be language specific changes, for example. Imagine a change to &g

Re: Running CI for doc changes

2019-01-03 Thread István Fehérvári
be your example use case. In case of a doc change, we would skip > our unit test pipelines while the website pipeline would still be executed. > #2 would be language specific changes, for example. Imagine a change to the > Scala code. This would require all Scala and Clojure jobs to re-run

Re: Running CI for doc changes

2019-01-03 Thread Marco de Abreu
change, we would skip our unit test pipelines while the website pipeline would still be executed. #2 would be language specific changes, for example. Imagine a change to the Scala code. This would require all Scala and Clojure jobs to re-run, but there would be no need to run R, Julia or Python

Re: Incubator Podling Report (Due 2nd January)

2019-01-02 Thread Haibin Lin
Dear MXNet mentors, Please review and approve quarterly podling report at https://wiki.apache.org/incubator/January2019. The report was created by myself (PPMC member) with contributions from Steffen. Sergey Kolychev (PPMC member) reviewed and approved. Thanks. Best, Haibin On Wed, Jan 2, 2019

Re: Incubator Podling Report (Due 2nd January)

2019-01-02 Thread Haibin Lin
Dear MXNet community, The section for "How has the community developed since the last report?" has been updated with recent developments in MXNet ecosystem. Please feel free to provide feedbacks on the draft report. Thanks. Best, Haibin On Wed, Jan 2, 2019 at 1:23 PM Michael Wall wrote: >

Re: Incubator Podling Report (Due 2nd January)

2019-01-02 Thread Michael Wall
Thanks Steffen and Haibin. On Wed, Jan 2, 2019 at 3:09 PM Steffen Rochel wrote: > Dear MXNet community - > Haibin and I are working on the MXNet report. See a draft at > https://wiki.apache.org/incubator/January2019. > Please provide feedback by 5pm PST today, so the report can be submitted in

Re: Incubator Podling Report (Due 2nd January)

2019-01-02 Thread Steffen Rochel
Dear MXNet community - Haibin and I are working on the MXNet report. See a draft at https://wiki.apache.org/incubator/January2019. Please provide feedback by 5pm PST today, so the report can be submitted in time by EOB today. Thanks, Steffen On Tue, Jan 1, 2019 at 10:39 PM Justin Mclean wrote:

Re: Incubator Podling Report (Due 2nd January)

2019-01-01 Thread Justin Mclean
Hi, The report is due today. [1] If you cannot report this month, it will eb noted in teh board report and you'll be asked to report next month. Thanks, Justin 1. https://wiki.apache.org/incubator/January2019

Re: [RESULTS][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc0

2018-12-28 Thread Steffen Rochel
Correction: This vote passes with 5 +1 votes (3 binding) and no 0 or -1 votes. +1 votes - Jim Jagielski / binding - Carin Meier / binding - Naveen Swamy / binding - Tao A Lv - Aston Zhang Regards, Steffen On Thu, Dec 27, 2018 at 12:24 PM Steffen Rochel wrote: > Dear MXNet

RE: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc0

2018-12-26 Thread Lv, Tao A
and INT8 performance/accuracy looks good. -tao -Original Message- From: Naveen Swamy [mailto:mnnav...@gmail.com] Sent: Saturday, December 22, 2018 6:52 AM To: dev@mxnet.incubator.apache.org Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc0 +1 Verified Signatures

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc0

2018-12-21 Thread Naveen Swamy
+1 Verified Signatures Downloaded source from dist server and Tested Scala Package on Linux CPU/ On Fri, Dec 21, 2018 at 11:21 AM Carin Meier wrote: > +1 (binding) - Tested on OSX with Clojure/Scala package > > On Thu, Dec 20, 2018 at 12:25 PM Steffen Rochel > wrote: > > > Dear MXNet

Re: Apache MXNet v1.4.0 release status

2018-12-21 Thread Steffen Rochel
Dear MXNet community - I hope you have seen that voting for v1.4.0.rc0 has started and will continue until December 27th noon. So far two binding +1 votes. I suggesting the following schedule to account for holidays and of course depending on voting feedback. Vote on dev@ until 12/27 Vote on

Re: Malformed package uploaded to Maven central

2018-12-21 Thread Naveen Swamy
I don't think they will disable PUT because some projects might be manually uploading artifacts. Here is the ticket i created : https://issues.apache.org/jira/browse/INFRA-17489 On Fri, Dec 21, 2018 at 10:23 AM Frank Liu wrote: > If the release procedure is always push to staging and manually

Re: Malformed package uploaded to Maven central

2018-12-21 Thread Naveen Swamy
Hi Qing, Thanks for bringing this to the attention of the community. I understand it was an unintended consequences of publish experiment. I will raise a INFRA ticket to remove this package from the releases repo. Could you please file a GitHub issue or MXNet JIRA and mention the commands you

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc0

2018-12-21 Thread Jim Jagielski
+1 (binding) > On Dec 20, 2018, at 12:24 PM, Steffen Rochel wrote: > > Dear MXNet community, > > This is the vote to release Apache MXNet (incubating) version v1.4.0. > Voting will start December 20 noon PST and close on December 27 noon PST. > > Link to release notes: > >

Re: Cambricon MLU support for MXNet.

2018-12-20 Thread Steffen Rochel
> Look forward to continued participation and contribution in the future. > > > -- > 发件人:Skalicky, Sam > 发送时间:2018年12月18日(星期二) 06:03 > 收件人:dev@mxnet.incubator.apache.org > 抄 送:张昊翀 > 主 题:Re: Cambricon MLU suppo

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc0

2018-12-20 Thread Aston Zhang
+ 1 tested with code at zh.diveintodeeplearning.org on both Windows and Linux. Thank @yajiedesign and @szha for the pip wheels. Cheers, Aston On Thu, Dec 20, 2018 at 9:25 AM Steffen Rochel wrote: > Dear MXNet community, > > This is the vote to release Apache MXNet (incubating) version v1.4.0.

Re: [Question] UI change policy in MXNet

2018-12-20 Thread Anirudh Subramanian
On Thu, Dec 20, 2018, 1:56 PM Lin Yuan Hi Anirudh, > > Thanks a lot for your clarifications! I have some followup > questions/comments: > > 1) Which guideline should we follow when updating the UI in MXNet > operators? > A) MXNet follows semantic versioning, so breaking changes to operator >

Re: [Question] UI change policy in MXNet

2018-12-20 Thread Lin Yuan
Hi Anirudh, Thanks a lot for your clarifications! I have some followup questions/comments: 1) Which guideline should we follow when updating the UI in MXNet operators? A) MXNet follows semantic versioning, so breaking changes to operator interfaces can be introduced only in major versions.

Re: [Question] UI change policy in MXNet

2018-12-20 Thread Anirudh Subramanian
1) Which guideline should we follow when updating the UI in MXNet operators? A) MXNet follows semantic versioning, so breaking changes to operator interfaces can be introduced only in major versions. 2) Who should approve the UI change? A) Contributors who may have worked on the operator and/or

Re: Apache MXNet v1.4.0 release status

2018-12-19 Thread Haibin Lin
Hi Steffen, Aston and I would like to bring this PR to your attention: https://github.com/apache/incubator-mxnet/pull/13686, where Zhi fixed the num_worker argument of DataLoader on windows. Without this fix, using DataLoader with num_worker > 0 would result in crash on Windows. Bringing this PR

Re: [Annoucement] New Committer -- Da Zheng

2018-12-17 Thread Hagay Lupesko
Congrats Da! On Mon, Dec 17, 2018 at 5:44 PM Marco de Abreu wrote: > Welcome Da, great to have you on board! > > Am Di., 18. Dez. 2018, 02:35 hat Lv, Tao A > geschrieben: > > > Congrats Da! Thank you for the effort on bringing MKL-DNN to MXNet. It's > > really the footstone for the latter work

Re: [Annoucement] New Committer -- Da Zheng

2018-12-17 Thread Marco de Abreu
Welcome Da, great to have you on board! Am Di., 18. Dez. 2018, 02:35 hat Lv, Tao A geschrieben: > Congrats Da! Thank you for the effort on bringing MKL-DNN to MXNet. It's > really the footstone for the latter work and improvements. > > -Original Message- > From: Tianqi Chen

RE: [Annoucement] New Committer -- Da Zheng

2018-12-17 Thread Lv, Tao A
Congrats Da! Thank you for the effort on bringing MKL-DNN to MXNet. It's really the footstone for the latter work and improvements. -Original Message- From: Tianqi Chen [mailto:tqc...@apache.org] Sent: Tuesday, December 18, 2018 1:02 AM To: dev@mxnet.incubator.apache.org Subject:

Re: [DISCUSS] About the usage of CUDA/CUDNN

2018-12-17 Thread Marco de Abreu
> but I not don't understand the legal lingo > > > > @Hen : Could you provide input to this? > > > > Thanks, Naveen > > > > On Mon, Dec 17, 2018 at 3:29 PM Davydenko, Denis < > > dzianis.davydze...@gmail.com> wrote: > > > >> Kelle

RE: [Annoucement] New Committer -- Da Zheng

2018-12-17 Thread Zhao, Patric
Congratulation, Da! Really thanks for your great supports and looking forward the more cooperation together :) > -Original Message- > From: Tianqi Chen [mailto:tqc...@apache.org] > Sent: Tuesday, December 18, 2018 1:02 AM > To: dev@mxnet.incubator.apache.org > Subject: [Annoucement]

Re: [DISCUSS] About the usage of CUDA/CUDNN

2018-12-17 Thread Hen
3:29 PM Davydenko, Denis < > dzianis.davydze...@gmail.com> wrote: > >> Kellen, please see conversation [1] on previously published proposal re: >> maven publishing pipeline. I think your concerns are valid and we should >> look into security aspect of running our CI

Re: [DISCUSS] About the usage of CUDA/CUDNN

2018-12-17 Thread Naveen Swamy
not don't understand the legal lingo @Hen : Could you provide input to this? Thanks, Naveen On Mon, Dec 17, 2018 at 3:29 PM Davydenko, Denis < dzianis.davydze...@gmail.com> wrote: > Kellen, please see conversation [1] on previously published proposal re: > maven publishing

Re: [DISCUSS] About the usage of CUDA/CUDNN

2018-12-17 Thread Davydenko, Denis
Kellen, please see conversation [1] on previously published proposal re: maven publishing pipeline. I think your concerns are valid and we should look into security aspect of running our CI on a broader scope, not bound to just artifact publishing. I believe right now Qing's question

Re: [DISCUSS] About the usage of CUDA/CUDNN

2018-12-17 Thread kellen sunderland
Restricted nodes may provide enough security for some use cases, but in my opinion they don't provide enough for artifact publishing. An example would be if there were a exploit available that worked against a Jenkins master. In this case I think an attacker code still pivot to a secure node

Re: [DISCUSS] About the usage of CUDA/CUDNN

2018-12-17 Thread Qing Lan
Hi Kellen, Firstly the restricted node is completely isolated to the PR-checking CI system (physically) which is explained in here: https://cwiki.apache.org/confluence/display/MXNET/Restricted+jobs+and+nodes. What you are mentioning: the Public CIs are all having troubles if they are public

Re: [DISCUSS] About the usage of CUDA/CUDNN

2018-12-17 Thread kellen sunderland
I'm not in favour of publishing artifacts from any Jenkins based systems. There are many ways to bundle artifacts and publish them from an automated system. Why we would use a CI system like Jenkins for this task? Jenkins frequently has security vulnerabilities and is designed to run arbitrary

Re: [Annoucement] New Committer -- Da Zheng

2018-12-17 Thread Alex Zai
Congrats Da. On Mon, Dec 17, 2018, 7:20 PM Emani, Ashok Congratulations Da, well deserved! > > On 12/17/18, 9:02 AM, "Tianqi Chen" wrote: > > Dear Community: > > Please join me to welcome Da Zheng as a new committer of the MXNet. > > Da is the main author of MKL-DNN integration and

Re: [Annoucement] New Committer -- Da Zheng

2018-12-17 Thread Emani, Ashok
Congratulations Da, well deserved! On 12/17/18, 9:02 AM, "Tianqi Chen" wrote: Dear Community: Please join me to welcome Da Zheng as a new committer of the MXNet. Da is the main author of MKL-DNN integration and recently he champions the control flow support. He is one

Re: [Annoucement] New Committer -- Da Zheng

2018-12-17 Thread Lin Yuan
Congrats! On Mon, Dec 17, 2018 at 9:19 AM Steffen Rochel wrote: > Congratulation Da! > > On Mon, Dec 17, 2018 at 9:02 AM Tianqi Chen wrote: > > > Dear Community: > > > > Please join me to welcome Da Zheng as a new committer of the MXNet. > > > > Da is the main author of MKL-DNN integration and

Re: API change discussion to resolve inconsistencies in Gluon Model Zoo

2018-12-17 Thread Skalicky, Sam
I think it would be a good idea to do this in all the language bindings so that error messages can be appropriate and familiar in the user’s language rather than confusing exceptions coming from the c++ backend. Heres an issue I filed for tracking:

Re: [Annoucement] New Committer -- Da Zheng

2018-12-17 Thread Steffen Rochel
Congratulation Da! On Mon, Dec 17, 2018 at 9:02 AM Tianqi Chen wrote: > Dear Community: > > Please join me to welcome Da Zheng as a new committer of the MXNet. > > Da is the main author of MKL-DNN integration and recently he champions the > control flow support. He is one of the few "explorer

Re: Apache MXNet v1.4.0 release status

2018-12-17 Thread Pedro Larroy
Hi Steffen Added some notes in your PR for the release notes. In particular, I'm a bit concerned about the status of topology aware communication, since it has open issues and is not being tested in CI. (The tests also fail). I think we should anounce it when it's working properly and it's well

Re: Cambricon MLU support for MXNet.

2018-12-17 Thread Pedro Larroy
Hi Haochong Welcome to MXNet, It's exciting to have additional hardware platforms added and supported in the project. The CI system for MXNet is donated by AWS to the project. We have a small hardware lab with embedded physical hardware like ARM boards including NVidia Jetson which we are

RE: Cambricon MLU support for MXNet.

2018-12-17 Thread Lv, Tao A
PM To: dev@mxnet.incubator.apache.org; ??? Cc: d...@mxnet.apache.org; solomon.zhc Subject: Re: Cambricon MLU support for MXNet. small point: mshadow is being deprecated. probably you shouldn’t invest too much time on it. just an FYI On Sun, Dec 16, 2018 at 6:33 PM 张昊翀 wrote: > Dear MXNet comm

Re: Cambricon MLU support for MXNet.

2018-12-16 Thread Chris Olivier
small point: mshadow is being deprecated. probably you shouldn’t invest too much time on it. just an FYI On Sun, Dec 16, 2018 at 6:33 PM 张昊翀 wrote: > Dear MXNet community, > > We are from Cambricon, a leading supplier of artificial intelligence > chips. We have two product lines, including IP

Re: Cambricon MLU support for MXNet.

2018-12-16 Thread Hagay Lupesko
Welcome to the MXNet community Haochong! It's exciting to learn about your plans to contribute to MXNet! I highly recommend that you document your proposal and technical design in MXNet's design proposals wiki [1 ], where you can

Re: Proposal for a recurrent architecture meeting and long term direction

2018-12-16 Thread Pedro Larroy
Hi I think you make good points. We can address your concerns by sending notes to the mailing list and use the wiki / RFCs appropriately so the community can follow and participate asynchronously so asynchronous participation is still possible. I would say let's try and see if they bring value,

Re: Proposal for a recurrent architecture meeting and long term direction

2018-12-16 Thread Tianqi Chen
I feel that online meeting may not address most of the issues get raised in a short amount of time(1h) and still suffers the problem of not being publically archivable. Maybe we can not try more asynchronous way? (RFC discussion in issues. and/or discuss @dev). Just my two cents and I am not

Re: Proposal for a recurrent architecture meeting and long term direction

2018-12-16 Thread Gavin M Bell
Nice!!!  Perfect! "I'm trying real hard to be the shepherd." -Jules Winnfield > On Dec 14, 2018, at 3:04 PM, Marco de Abreu wrote: > > That's a great idea, Pedro! > > -Marco > > Am Fr., 14. Dez. 2018, 14:34 hat Pedro Larroy > geschrieben: > >> Hi MXNetters >> >> To address the

Re: Apache MXNet v1.4.0 release status

2018-12-15 Thread Steffen Rochel
Dear MXNet community - all issues beside one have been addressed. I suggest to document the last remaining issue as known problem and move forward with the release. Please communicate if you have concerns of know about critical issues to be

Re: [DISCUSS] About the PR merging policy

2018-12-14 Thread Anirudh Acharya
Thanks Qing for bringing this up. I think the cwiki can contain pointers to apache guidelines - - https://www.apache.org/dev/committers.html - https://www.apache.org/dev/new-committers-guide.html - And a few thumb rules( not hard and fast rules, we should trust the committers to act

Re: [DISCUSS] About the PR merging policy

2018-12-14 Thread Carin Meier
Thanks Steffen, I had remembered reading that but couldn't find it again :) So yes - maybe we can duplicate that section and/or provide a link to a new committers guide. I'm thinking it should go on the community page here https://cwiki.apache.org/confluence/display/MXNET/Community Eventually,

Re: Julia CI Package

2018-12-14 Thread Carin Meier
I would create an issue for it and ping Iblis Lin on it https://github.com/apache/incubator-mxnet/pulls?q=is%3Apr+author%3Aiblis17 - He is the contributor that brought in the Julia package and got the CI process running with it so he might have more insight. - Carin On Fri, Dec 14, 2018 at 2:38

Re: Julia CI Package

2018-12-14 Thread kellen sunderland
If it's hanging consistently would you be able to dump a native stack trace and see what call specifically is hanging? On Fri, Dec 14, 2018 at 11:38 AM Alex Zai wrote: > Is anyone familiar with the Julia build and can help debug an issue where > the Julia stage in the CI just hangs? I have made

Re: Proposal for a recurrent architecture meeting and long term direction

2018-12-14 Thread Marco de Abreu
That's a great idea, Pedro! -Marco Am Fr., 14. Dez. 2018, 14:34 hat Pedro Larroy geschrieben: > Hi MXNetters > > To address the project growth and increased contributions I'm > proposing a monthly meeting / hangout to have community discussions > about MXNet architecture and mid / longer term

Re: [DISCUSS] About the PR merging policy

2018-12-13 Thread Steffen Rochel
We do have already a guide which covers the issue: https://cwiki.apache.org/confluence/display/MXNET/Development+Process#DevelopmentProcess-GuidelinesforReviewers/Committers

Re: [DISCUSS] About the PR merging policy

2018-12-12 Thread Carin Meier
Qing - thanks for bringing this up. I think it would be a good thing to have a document on the wiki to help with these sorts of questions. In fact, since the project is growing with more new committers, maybe we could use a "New Committer Guide" with the process of how to get going and any FAQ

Re: [DISCUSS] About the PR merging policy

2018-12-12 Thread Anton Chernov
There was no policy setup before for this as far as I know. Personally, I don't see any value in introducing another blocker for enough slow process of PR merges. The best value / burden ratio one gets from lightweight 'another pair of eyes' approach. Anton ср, 12 дек. 2018 г. в 01:24, Tianqi

Re: [DISCUSS] About the PR merging policy

2018-12-11 Thread Tianqi Chen
I think it is fine as long as we act on good faith. I will normally respect code review comments from anyone who might be able to give reasonable comments, and beg to differ with good technical reasoning. Normally contributions happen in a way that things won't get blocked in small features. For

Re: Slack invite hotlink

2018-12-11 Thread Michael Wall
I am not sure honestly. I read that as the token expires in the 30 days and the shortened URL is permanent and will always point to the token even after it expires. There has been some discussion in the #asfinfra channel on slack[1]. If I figure anything out I'll report back. [1]

Re: Slack invite hotlink

2018-12-11 Thread Marco de Abreu
Hi Mike, thanks for the heads up and linking the ticket. In there, Chris stated that he converted the link to a permanent one: > The link in your shortened URL is now permanent. Does that address your concerns? Best regards, Marco On Tue, Dec 11, 2018 at 6:19 PM Michael Wall wrote: > Marco,

Re: Include MKLDNN into default mxnet pip package

2018-12-11 Thread Naveen Swamy
Great effort Alex and also folks from Intel. +1 to make MKLDNN default. On Tue, Dec 11, 2018 at 9:10 AM Kumar, Vikas wrote: > +1 > > On 12/10/18, 8:01 PM, "Zhao, Patric" wrote: > > +1, thanks for the efforts, Alex. > > > > > -Original Message- > > From: Alex Zai

Re: Slack invite hotlink

2018-12-11 Thread Michael Wall
Marco, Seems like that link is only good for 30 days. See https://issues.apache.org/jira/browse/INFRA-17152. Mike On Tue, Dec 11, 2018 at 12:01 PM Marco de Abreu wrote: > Hey everyone, > > there's a hotlink [1] that allows people to join Apaches Slack server > directly, I found it here [2].

Re: Include MKLDNN into default mxnet pip package

2018-12-11 Thread Kumar, Vikas
+1 On 12/10/18, 8:01 PM, "Zhao, Patric" wrote: +1, thanks for the efforts, Alex. > -Original Message- > From: Alex Zai [mailto:aza...@gmail.com] > Sent: Tuesday, December 11, 2018 8:00 AM > To: dev@mxnet.incubator.apache.org > Subject: Include

RE: Include MKLDNN into default mxnet pip package

2018-12-10 Thread Zhao, Patric
+1, thanks for the efforts, Alex. > -Original Message- > From: Alex Zai [mailto:aza...@gmail.com] > Sent: Tuesday, December 11, 2018 8:00 AM > To: dev@mxnet.incubator.apache.org > Subject: Include MKLDNN into default mxnet pip package > > Continuation from the following thread: >

Re: Invite for slack request

2018-12-09 Thread Steffen Rochel
Welcome to MXNet project! On Mon, Dec 10, 2018 at 5:22 AM Nicolas Modrzyk wrote: > Bonjour, Good morning, > > Nico here, working a bit on the Clojure port. > Would it be possible to get a slack invitation ? > > Nico >

Re: Requesting slack access

2018-12-09 Thread Steffen Rochel
Welcome to the MXNet project! On Mon, Dec 10, 2018 at 5:22 AM Thadani, Rohit wrote: > I'd like to help contribute to the mxnet project so I though it might be > useful to join the slack channels > > Thanks > Rohit, >

<    2   3   4   5   6   7   8   9   10   11   >