Re: A proposal of supporting dynamic shape and shape symbol

2018-07-19 Thread Junru Shao
Hi Da,

So excited to see this proposal, it empowers MXNet with the capacity to
tackle modern CV/NLP tasks with ease! Vote for it.

Thanks,
Junru

On Thu, Jul 19, 2018 at 7:59 PM Zheng, Da  wrote:

> Hello all,
>
> As you know, MXNet performs static shape inference to optimize the
> performance. However, there are cases that the output arrays of an operator
> can’t be statically inferred. In addition, MXNet doesn’t support shape
> symbol. For example, the input shape of mx.sym.ones has to be a Python
> tuple right now.
>
> The design proposal below is trying to fix both problems.
> https://cwiki.apache.org/confluence/display/MXNET/Dynamic+shape
>
> Please let me know if you have any comments and suggestions.
>
> Best,
> Da
>


A proposal of supporting dynamic shape and shape symbol

2018-07-19 Thread Zheng, Da
Hello all,

As you know, MXNet performs static shape inference to optimize the performance. 
However, there are cases that the output arrays of an operator can’t be 
statically inferred. In addition, MXNet doesn’t support shape symbol. For 
example, the input shape of mx.sym.ones has to be a Python tuple right now.

The design proposal below is trying to fix both problems. 
https://cwiki.apache.org/confluence/display/MXNET/Dynamic+shape

Please let me know if you have any comments and suggestions.

Best,
Da


Re: Remove Caffe functionality

2018-07-19 Thread Mu Li
We cannot rely on #issue as a popularity score. No issue means either no
one is using it or it's well documented and has no bug.

Removing functionality is equivalent to API breaking, we should be very
careful about it.

I don't suggest the caffe2->onnx approach for 2 reasons:

1. it's complicated, people need to install pytorch and onnx, since caffe2
is merged into pytorch
2. both caffe2 and onnx are under rapid developing, it's hard to debug if
users submitted issues to us

If putting my amazon hat on, we must keep the caffe converter, since some
major customers are using it.

On Thu, Jul 19, 2018 at 1:42 PM, Afrooze, Sina  wrote:

> I think it'd be more sustainable long term to expect users to convert
> caffe -> caffe2 ->onnx->mxnet rather than caffe->mxnet. Perhaps an MXNet
> tutorial can show how to do this with minimum pain. - Sina
>
>
> On 7/19/18, 1:27 PM, "Steffen Rochel"  wrote:
>
> Hi Mu - do we have any indication how many users we do have on the
> functionality? I see only two github issues from 2017 open.
>
> On Thu, Jul 19, 2018 at 12:54 PM Mu Li  wrote:
>
> > Hi Anton,
> >
> > It's understandable that Caffe is old and its community is
> shrinking. For
> > this very reasons, existing caffe users are looking for
> alternatives. The
> > current converter is important for such users to transit to MXNet. It
> > addresses an important issue that: how I can reuse my previous caffe
> models
> > in MXNet.
> >
> > On Thu, Jul 19, 2018 at 11:53 AM, Anton Chernov  >
> > wrote:
> >
> > > Dear community,
> > >
> > > Currently MXNet has a Caffe framework integration (translator and
> > > converter) [1].
> > >
> > > There were some issues discovered with it, for example some tests
> were
> > > failing [2]. Since we decided to remove the flaky tests and
> proceed to
> > > making them stable I propose completely removing this functionality
> > > instead.
> > >
> > > There are multiple reasons to this:
> > >
> > > * Mind that this is Caffe 1 (not 2)
> > > * Some people mentioned: "Caffe is soo 2015."
> > > * Keeping functionality that is both unstable and old is a burden
> for
> > > maintenance.
> > > * Keeping functionality that nobody needs is not necessary overall
> > >
> > > Please let me know your thoughts.
> > >
> > > Best
> > > Anton
> > >
> > > [1]
> > > https://github.com/apache/incubator-mxnet/commits/
> > > master/tools/caffe_converter/convert_caffe_modelzoo.py
> > > [2]
> > > http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/
> > > incubator-mxnet/detail/master/1207/pipeline/
> > >
> >
>
>
>
>


Re: Remove Caffe functionality

2018-07-19 Thread Chris Olivier
There’s more production systems still using Caffe 1 than you may realize.
While it may be easy for individual developers to move off of Caffe, it
will be quite some time before many production systems are off of it,
because, as you can imagine, it’s much more difficult to change a live
system without a good transition plan (which the caffe integration features
do).  (I can think of several major services at my day job that use Caffe).

On Thu, Jul 19, 2018 at 1:42 PM Afrooze, Sina  wrote:

> I think it'd be more sustainable long term to expect users to convert
> caffe -> caffe2 ->onnx->mxnet rather than caffe->mxnet. Perhaps an MXNet
> tutorial can show how to do this with minimum pain. - Sina
>
>
> On 7/19/18, 1:27 PM, "Steffen Rochel"  wrote:
>
> Hi Mu - do we have any indication how many users we do have on the
> functionality? I see only two github issues from 2017 open.
>
> On Thu, Jul 19, 2018 at 12:54 PM Mu Li  wrote:
>
> > Hi Anton,
> >
> > It's understandable that Caffe is old and its community is
> shrinking. For
> > this very reasons, existing caffe users are looking for
> alternatives. The
> > current converter is important for such users to transit to MXNet. It
> > addresses an important issue that: how I can reuse my previous caffe
> models
> > in MXNet.
> >
> > On Thu, Jul 19, 2018 at 11:53 AM, Anton Chernov  >
> > wrote:
> >
> > > Dear community,
> > >
> > > Currently MXNet has a Caffe framework integration (translator and
> > > converter) [1].
> > >
> > > There were some issues discovered with it, for example some tests
> were
> > > failing [2]. Since we decided to remove the flaky tests and
> proceed to
> > > making them stable I propose completely removing this functionality
> > > instead.
> > >
> > > There are multiple reasons to this:
> > >
> > > * Mind that this is Caffe 1 (not 2)
> > > * Some people mentioned: "Caffe is soo 2015."
> > > * Keeping functionality that is both unstable and old is a burden
> for
> > > maintenance.
> > > * Keeping functionality that nobody needs is not necessary overall
> > >
> > > Please let me know your thoughts.
> > >
> > > Best
> > > Anton
> > >
> > > [1]
> > > https://github.com/apache/incubator-mxnet/commits/
> > > master/tools/caffe_converter/convert_caffe_modelzoo.py
> > > [2]
> > > http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/
> > > incubator-mxnet/detail/master/1207/pipeline/
> > >
> >
>
>
>
>


Re: Remove Caffe functionality

2018-07-19 Thread Afrooze, Sina
I think it'd be more sustainable long term to expect users to convert caffe -> 
caffe2 ->onnx->mxnet rather than caffe->mxnet. Perhaps an MXNet tutorial can 
show how to do this with minimum pain. - Sina


On 7/19/18, 1:27 PM, "Steffen Rochel"  wrote:

Hi Mu - do we have any indication how many users we do have on the
functionality? I see only two github issues from 2017 open.

On Thu, Jul 19, 2018 at 12:54 PM Mu Li  wrote:

> Hi Anton,
>
> It's understandable that Caffe is old and its community is shrinking. For
> this very reasons, existing caffe users are looking for alternatives. The
> current converter is important for such users to transit to MXNet. It
> addresses an important issue that: how I can reuse my previous caffe 
models
> in MXNet.
>
> On Thu, Jul 19, 2018 at 11:53 AM, Anton Chernov 
> wrote:
>
> > Dear community,
> >
> > Currently MXNet has a Caffe framework integration (translator and
> > converter) [1].
> >
> > There were some issues discovered with it, for example some tests were
> > failing [2]. Since we decided to remove the flaky tests and proceed to
> > making them stable I propose completely removing this functionality
> > instead.
> >
> > There are multiple reasons to this:
> >
> > * Mind that this is Caffe 1 (not 2)
> > * Some people mentioned: "Caffe is soo 2015."
> > * Keeping functionality that is both unstable and old is a burden for
> > maintenance.
> > * Keeping functionality that nobody needs is not necessary overall
> >
> > Please let me know your thoughts.
> >
> > Best
> > Anton
> >
> > [1]
> > https://github.com/apache/incubator-mxnet/commits/
> > master/tools/caffe_converter/convert_caffe_modelzoo.py
> > [2]
> > http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/
> > incubator-mxnet/detail/master/1207/pipeline/
> >
>





Re: Remove Caffe functionality

2018-07-19 Thread Steffen Rochel
Hi Mu - do we have any indication how many users we do have on the
functionality? I see only two github issues from 2017 open.

On Thu, Jul 19, 2018 at 12:54 PM Mu Li  wrote:

> Hi Anton,
>
> It's understandable that Caffe is old and its community is shrinking. For
> this very reasons, existing caffe users are looking for alternatives. The
> current converter is important for such users to transit to MXNet. It
> addresses an important issue that: how I can reuse my previous caffe models
> in MXNet.
>
> On Thu, Jul 19, 2018 at 11:53 AM, Anton Chernov 
> wrote:
>
> > Dear community,
> >
> > Currently MXNet has a Caffe framework integration (translator and
> > converter) [1].
> >
> > There were some issues discovered with it, for example some tests were
> > failing [2]. Since we decided to remove the flaky tests and proceed to
> > making them stable I propose completely removing this functionality
> > instead.
> >
> > There are multiple reasons to this:
> >
> > * Mind that this is Caffe 1 (not 2)
> > * Some people mentioned: "Caffe is soo 2015."
> > * Keeping functionality that is both unstable and old is a burden for
> > maintenance.
> > * Keeping functionality that nobody needs is not necessary overall
> >
> > Please let me know your thoughts.
> >
> > Best
> > Anton
> >
> > [1]
> > https://github.com/apache/incubator-mxnet/commits/
> > master/tools/caffe_converter/convert_caffe_modelzoo.py
> > [2]
> > http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/
> > incubator-mxnet/detail/master/1207/pipeline/
> >
>


Re: Release plan - MXNET 1.3

2018-07-19 Thread Anirudh Acharya
@sandeep krishnamurthy  the bug fixes in the
R-package is something we have just begun, there will not be anything
significant to announce before the v1.3 code freeze.

On Wed, Jul 18, 2018 at 10:08 PM Steffen Rochel 
wrote:

> To make it easier to find the discussions related to project proposals I
> added a column with a link to the thread on dev@ for most projects.
> Appreciate for the project owners to fill in the blanks and to check that I
> got the right threads.
>
> Regards,
> Steffen
>
> On Wed, Jul 18, 2018 at 7:11 PM Roshani Nagmote  >
> wrote:
>
> > Hi Kellen,
> >
> > Sure. I will update the notes with the information.
> >
> > Thanks,
> > Roshani
> >
> > On Wed, Jul 18, 2018 at 3:01 PM kellen sunderland <
> > kellen.sunderl...@gmail.com> wrote:
> >
> > > Hey Roshani,
> > >
> > > Would you be able to add 'TensorRT Runtime Integration' to the list of
> > > upcoming features?  We'll target getting the release in and polished by
> > the
> > > 23rd.  Design proposal is here:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/Runtime+Integration+with+TensorRT
> > > and the lead contributor is Marek Kolodziej.
> > >
> > > -Kellen
> > >
> > > On Wed, Jul 18, 2018 at 8:32 PM Roshani Nagmote <
> > roshaninagmo...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > I am starting the process to prepare for Apache MXNet (incubating)
> 1.3
> > > > Release. Please find project proposal draft for this release here:
> > > > <*
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+next+MXNet+Release
> > > > <
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+next+MXNet+Release
> > > > >*
> > > > >
> > > >
> > > > Target feature freeze date is July 23rd. A release candidate will be
> > cut
> > > > around Monday, August 6th and voting will commence from then until
> > > > Thursday, August 9th. If you have any additional features in progress
> > and
> > > > would like to include it in this release, please make sure to comment
> > so
> > > I
> > > > can update the release notes.
> > > >
> > > > Feel free to add any other comments/suggestions.
> > > >
> > > > Thanks,
> > > > Roshani
> > > >
> > >
> >
>


Re: Remove Caffe functionality

2018-07-19 Thread Mu Li
Hi Anton,

It's understandable that Caffe is old and its community is shrinking. For
this very reasons, existing caffe users are looking for alternatives. The
current converter is important for such users to transit to MXNet. It
addresses an important issue that: how I can reuse my previous caffe models
in MXNet.

On Thu, Jul 19, 2018 at 11:53 AM, Anton Chernov  wrote:

> Dear community,
>
> Currently MXNet has a Caffe framework integration (translator and
> converter) [1].
>
> There were some issues discovered with it, for example some tests were
> failing [2]. Since we decided to remove the flaky tests and proceed to
> making them stable I propose completely removing this functionality
> instead.
>
> There are multiple reasons to this:
>
> * Mind that this is Caffe 1 (not 2)
> * Some people mentioned: "Caffe is soo 2015."
> * Keeping functionality that is both unstable and old is a burden for
> maintenance.
> * Keeping functionality that nobody needs is not necessary overall
>
> Please let me know your thoughts.
>
> Best
> Anton
>
> [1]
> https://github.com/apache/incubator-mxnet/commits/
> master/tools/caffe_converter/convert_caffe_modelzoo.py
> [2]
> http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/
> incubator-mxnet/detail/master/1207/pipeline/
>


Re: MXNet developer setup on Mac with VSCode for develop, test and debug

2018-07-19 Thread Anton Chernov
I hope that the instructions will be for cmake soon. After merging this PR
[1] there should be not too much problems with the build (considering it's
without CUDA).

Best
Anton

[1] https://github.com/apache/incubator-mxnet/pull/11148

чт, 19 июл. 2018 г. в 18:59, Pedro Larroy :

> Have you guys tried CLion, works like a charm for me. (Requires license).
>
> On Wed, Jul 18, 2018 at 10:09 PM Naveen Swamy  wrote:
>
> > Thanks Sandeep for putting this together, it would make it easy for
> people
> > who prefer to IDEs to get started with MXNet easily.
> >
> > On Wed, Jul 18, 2018 at 1:04 PM, Lin Yuan  wrote:
> >
> > > Hi Aaron,
> > >
> > > This doc is for development on Mac. It is not intended for Windows
> users.
> > > Maybe we can start a different thread to discuss about MXNet build on
> > > Windows? I have tried it myself on a GPU instances built on Windows
> DLAMI
> > > 10.0. I would love to share with you my setup steps.
> > >
> > > Lin
> > >
> > > On Wed, Jul 18, 2018 at 11:43 AM Markham, Aaron
> > > 
> > > wrote:
> > >
> > > > This is tangential, but Lin, I noticed during the RC1 tests you said
> > you
> > > > tried it out on Windows and it worked for you. I'd like to get VS2017
> > or
> > > VS
> > > > Code working, take Sandeep's setup content and possibly your Windows
> > > > experience, and improve the MXNet Windows setup guide. I've tried it
> > and
> > > > failed. Multiple times. I also tried the MKLDNN instructions and
> > failed.
> > > I
> > > > tried the setup tools batch file and was hit with a lot of dependency
> > > > errors. Some of the problem isn't in the MXNet docs, but in the
> > > > dependencies' documentation, but I'm left to go figure that out on my
> > > own.
> > > > Anyway, any help you can provide here would be great. Also, if any of
> > you
> > > > reading this has a sort of checklist or guide for Windows, I'd love
> to
> > > see
> > > > it.
> > > >
> > > > BTW, I'm using Windows 10 with an NVIDIA GeForce GTX 980, and was
> > trying
> > > > to use VS2017 Community Edition and MKL. I went to MKL after OpenBLAS
> > > > wasn't installing/building.
> > > >
> > > > On 7/18/18, 10:59 AM, "Lin Yuan"  wrote:
> > > >
> > > > Thanks for the well-written document! As a new MXNet developer, I
> > > have
> > > > found it very helpful.
> > > >
> > > > Lin
> > > >
> > > > On Wed, Jul 18, 2018 at 10:50 AM sandeep krishnamurthy <
> > > s...@apache.org
> > > > >
> > > > wrote:
> > > >
> > > > > Hello Community,
> > > > >
> > > > >
> > > > >
> > > > > As a MXNet contributor, I had issues and took me some time on
> > > getting
> > > > > hands-on with MXNet codebase, being able to code, test, DEBUG
> > > > python/CPP
> > > > > combination. I have documented the steps for MXNet development
> > > setup
> > > > using
> > > > > VSCode on Mac. Document starts from installing all required
> > > > > tools/packages/IDEs/extensions and then provides steps for
> > > debugging
> > > > mix of
> > > > > Python/CPP code, which is most likely the case for any MXNet
> > > > developer, all
> > > > > in single IDE window. By end of this document, anyone should be
> > > able
> > > > to
> > > > > walk through the MXNet code, debug and be able to make first
> code
> > > > change.
> > > > >
> > > > >
> > > > >
> > > > > Please feel free to add comments, make changes as necessary.
> > > > >
> > > > >
> > > > >
> > > > https://cwiki.apache.org/confluence/display/MXNET/
> > > MXNet+Developer+Setup+on+Mac
> > > > >
> > > > > Best,
> > > > > Sandeep
> > > > >
> > > >
> > > >
> > > >
> > >
> >
>


Remove Caffe functionality

2018-07-19 Thread Anton Chernov
Dear community,

Currently MXNet has a Caffe framework integration (translator and
converter) [1].

There were some issues discovered with it, for example some tests were
failing [2]. Since we decided to remove the flaky tests and proceed to
making them stable I propose completely removing this functionality
instead.

There are multiple reasons to this:

* Mind that this is Caffe 1 (not 2)
* Some people mentioned: "Caffe is soo 2015."
* Keeping functionality that is both unstable and old is a burden for
maintenance.
* Keeping functionality that nobody needs is not necessary overall

Please let me know your thoughts.

Best
Anton

[1]
https://github.com/apache/incubator-mxnet/commits/master/tools/caffe_converter/convert_caffe_modelzoo.py
[2]
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/master/1207/pipeline/


Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Pedro Larroy
Yes Naveen, I think you are saying exactly the same as I hinted. Sheng also
agreed with this.

Pedro.

On Thu, Jul 19, 2018 at 6:54 PM Naveen Swamy  wrote:

> I do not think there needs to be a distinction made for
> support/office-hours by committer or contributors(in this case Amazon
> employed contributors) -- correct me if I misunderstood your guess :).
> Like I said, I would rather call it MXNet Office hours and categorize the
> kind of support that is offered, we might be able to find contributors
> willing to do this in different parts of the world regardless of their day
> job or not.
>
> On Thu, Jul 19, 2018 at 9:21 AM, Sheng Zha  wrote:
>
> > I'm guessing Mu's intention is to make it clear that such invitation is
> > extended by teams in Amazon/AWS instead of by committers, so as to avoid
> > the confusion of the naming "MXNet SDK". Suggestions to achieve the same
> > goal are welcome.
> >
> > Best regards,
> > -sz
> >
> > On Thu, Jul 19, 2018 at 9:09 AM, Isabel Drost-Fromm 
> > wrote:
> >
> > >
> > >
> > > On 18/07/18 23:30, Mu Li wrote:
> > >
> > >> A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet
> > SDK.
> > >>
> > >
> > > What exactly is the Amazon MXNet SDK? What is the AWS MXNet SDK?
> > >
> > > Your suggestion triggered my question because:
> > >
> > > https://www.apache.org/foundation/marks/#products
> > >
> > >
> > > Isabel
> > >
> > >
> >
>


Re: MXNet developer setup on Mac with VSCode for develop, test and debug

2018-07-19 Thread Pedro Larroy
Have you guys tried CLion, works like a charm for me. (Requires license).

On Wed, Jul 18, 2018 at 10:09 PM Naveen Swamy  wrote:

> Thanks Sandeep for putting this together, it would make it easy for people
> who prefer to IDEs to get started with MXNet easily.
>
> On Wed, Jul 18, 2018 at 1:04 PM, Lin Yuan  wrote:
>
> > Hi Aaron,
> >
> > This doc is for development on Mac. It is not intended for Windows users.
> > Maybe we can start a different thread to discuss about MXNet build on
> > Windows? I have tried it myself on a GPU instances built on Windows DLAMI
> > 10.0. I would love to share with you my setup steps.
> >
> > Lin
> >
> > On Wed, Jul 18, 2018 at 11:43 AM Markham, Aaron
> > 
> > wrote:
> >
> > > This is tangential, but Lin, I noticed during the RC1 tests you said
> you
> > > tried it out on Windows and it worked for you. I'd like to get VS2017
> or
> > VS
> > > Code working, take Sandeep's setup content and possibly your Windows
> > > experience, and improve the MXNet Windows setup guide. I've tried it
> and
> > > failed. Multiple times. I also tried the MKLDNN instructions and
> failed.
> > I
> > > tried the setup tools batch file and was hit with a lot of dependency
> > > errors. Some of the problem isn't in the MXNet docs, but in the
> > > dependencies' documentation, but I'm left to go figure that out on my
> > own.
> > > Anyway, any help you can provide here would be great. Also, if any of
> you
> > > reading this has a sort of checklist or guide for Windows, I'd love to
> > see
> > > it.
> > >
> > > BTW, I'm using Windows 10 with an NVIDIA GeForce GTX 980, and was
> trying
> > > to use VS2017 Community Edition and MKL. I went to MKL after OpenBLAS
> > > wasn't installing/building.
> > >
> > > On 7/18/18, 10:59 AM, "Lin Yuan"  wrote:
> > >
> > > Thanks for the well-written document! As a new MXNet developer, I
> > have
> > > found it very helpful.
> > >
> > > Lin
> > >
> > > On Wed, Jul 18, 2018 at 10:50 AM sandeep krishnamurthy <
> > s...@apache.org
> > > >
> > > wrote:
> > >
> > > > Hello Community,
> > > >
> > > >
> > > >
> > > > As a MXNet contributor, I had issues and took me some time on
> > getting
> > > > hands-on with MXNet codebase, being able to code, test, DEBUG
> > > python/CPP
> > > > combination. I have documented the steps for MXNet development
> > setup
> > > using
> > > > VSCode on Mac. Document starts from installing all required
> > > > tools/packages/IDEs/extensions and then provides steps for
> > debugging
> > > mix of
> > > > Python/CPP code, which is most likely the case for any MXNet
> > > developer, all
> > > > in single IDE window. By end of this document, anyone should be
> > able
> > > to
> > > > walk through the MXNet code, debug and be able to make first code
> > > change.
> > > >
> > > >
> > > >
> > > > Please feel free to add comments, make changes as necessary.
> > > >
> > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/MXNET/
> > MXNet+Developer+Setup+on+Mac
> > > >
> > > > Best,
> > > > Sandeep
> > > >
> > >
> > >
> > >
> >
>


Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Sheng Zha
Thanks. Yeah, I think naming after focused area instead of Amazon internal
organization/team names would likely work better. That way, others who'd
like to offer help in that area can just jump in and start helping.

-sz

On Thu, Jul 19, 2018 at 9:51 AM, Pedro Larroy 
wrote:

> There's an MXNet comitter in our office hours (Marco de Abreu @marcoabreu),
> others are contributors such as Anton (@lebeg) or others. I think we could
> refocus the conversation to the point that the office hours might have some
> emphasis in a particular area of MXNet.
>
> On Thu, Jul 19, 2018 at 6:21 PM Sheng Zha  wrote:
>
> > I'm guessing Mu's intention is to make it clear that such invitation is
> > extended by teams in Amazon/AWS instead of by committers, so as to avoid
> > the confusion of the naming "MXNet SDK". Suggestions to achieve the same
> > goal are welcome.
> >
> > Best regards,
> > -sz
> >
> > On Thu, Jul 19, 2018 at 9:09 AM, Isabel Drost-Fromm 
> > wrote:
> >
> > >
> > >
> > > On 18/07/18 23:30, Mu Li wrote:
> > >
> > >> A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet
> > SDK.
> > >>
> > >
> > > What exactly is the Amazon MXNet SDK? What is the AWS MXNet SDK?
> > >
> > > Your suggestion triggered my question because:
> > >
> > > https://www.apache.org/foundation/marks/#products
> > >
> > >
> > > Isabel
> > >
> > >
> >
>


Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Naveen Swamy
I do not think there needs to be a distinction made for
support/office-hours by committer or contributors(in this case Amazon
employed contributors) -- correct me if I misunderstood your guess :).
Like I said, I would rather call it MXNet Office hours and categorize the
kind of support that is offered, we might be able to find contributors
willing to do this in different parts of the world regardless of their day
job or not.

On Thu, Jul 19, 2018 at 9:21 AM, Sheng Zha  wrote:

> I'm guessing Mu's intention is to make it clear that such invitation is
> extended by teams in Amazon/AWS instead of by committers, so as to avoid
> the confusion of the naming "MXNet SDK". Suggestions to achieve the same
> goal are welcome.
>
> Best regards,
> -sz
>
> On Thu, Jul 19, 2018 at 9:09 AM, Isabel Drost-Fromm 
> wrote:
>
> >
> >
> > On 18/07/18 23:30, Mu Li wrote:
> >
> >> A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet
> SDK.
> >>
> >
> > What exactly is the Amazon MXNet SDK? What is the AWS MXNet SDK?
> >
> > Your suggestion triggered my question because:
> >
> > https://www.apache.org/foundation/marks/#products
> >
> >
> > Isabel
> >
> >
>


Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Pedro Larroy
There's an MXNet comitter in our office hours (Marco de Abreu @marcoabreu),
others are contributors such as Anton (@lebeg) or others. I think we could
refocus the conversation to the point that the office hours might have some
emphasis in a particular area of MXNet.

On Thu, Jul 19, 2018 at 6:21 PM Sheng Zha  wrote:

> I'm guessing Mu's intention is to make it clear that such invitation is
> extended by teams in Amazon/AWS instead of by committers, so as to avoid
> the confusion of the naming "MXNet SDK". Suggestions to achieve the same
> goal are welcome.
>
> Best regards,
> -sz
>
> On Thu, Jul 19, 2018 at 9:09 AM, Isabel Drost-Fromm 
> wrote:
>
> >
> >
> > On 18/07/18 23:30, Mu Li wrote:
> >
> >> A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet
> SDK.
> >>
> >
> > What exactly is the Amazon MXNet SDK? What is the AWS MXNet SDK?
> >
> > Your suggestion triggered my question because:
> >
> > https://www.apache.org/foundation/marks/#products
> >
> >
> > Isabel
> >
> >
>


Invitation: MXNet Hangout (II) @ Thu Aug 2, 2018 14:00 - 15:00 (CEST) (dev@mxnet.incubator.apache.org)

2018-07-19 Thread Pedro Larroy
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180802T12Z
DTEND:20180802T13Z
DTSTAMP:20180719T164141Z
ORGANIZER;CN=Pedro Larroy:mailto:pedro.larroy.li...@gmail.com
UID:7330gqo21ackeael39nbpf6...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@mxnet.incubator.apache.org;X-NUM-GUESTS=0:mailto:d...@mxnet.incu
 bator.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=pedro.larroy.li...@gmail.com;X-NUM-GUESTS=0:mailto:pedro.larroy.lists@g
 mail.com
CREATED:20180719T164027Z
DESCRIPTION:\n\n\n\nAdding a calendar invite:\n\n\nOrganizer: Steffen Roche
 l\n\n Dial in instructions:\n   -\n\n  https://chime.aws/8536075882\n\n
   Meeting ID: 8536 07 5882\n\n  United States Toll-Free: +1 855-552
 -4463 Meeting PIN: 8536 07 5882\n\n  One-click Mobile Dial-in (United S
 tates (1)): +1\n  206-462-5569\,\,8536075882#\n\n  International: h
 ttps://chime.aws/dialinnumbers/\n  -\n\n   Agenda:\n   - TBD\n\n\nPleas
 e feel free to add agenda items to hangout wiki page\n\n.\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~::~:~::-\nPlease do not edit this section of the descriptio
 n.\n\nView your event at https://www.google.com/calendar/event?action=VIEW;
 eid=NzMzMGdxbzIxYWNrZWFlbDM5bmJwZjZ0OTYgZGV2QG14bmV0LmluY3ViYXRvci5hcGFjaGU
 ub3Jn=MjgjcGVkcm8ubGFycm95Lmxpc3RzQGdtYWlsLmNvbWM4MzVmZTdkZjFlNWU3NzBlM
 zY5Mjk5NDBkYjRiMTlhMDgyOWI1OWY=Europe%2FBerlin=en=1.\n-::~:~::~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::
 -
LAST-MODIFIED:20180719T164141Z
LOCATION:Chime
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:MXNet Hangout (II)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics


Invitation: MXNet hangout (I) @ Wed Aug 1, 2018 17:00 - 18:00 (CEST) (dev@mxnet.incubator.apache.org)

2018-07-19 Thread Pedro Larroy
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180801T15Z
DTEND:20180801T16Z
DTSTAMP:20180719T164006Z
ORGANIZER;CN=Pedro Larroy:mailto:pedro.larroy.li...@gmail.com
UID:3aat42a0qkpd6giq7sl7fmp...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@mxnet.incubator.apache.org;X-NUM-GUESTS=0:mailto:d...@mxnet.incu
 bator.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Pedro Larroy;X-NUM-GUESTS=0:mailto:pedro.larroy.li...@gmail.com
CREATED:20180719T164005Z
DESCRIPTION:\n\nAdding a calendar invite:\n\n\nOrganizer: Steffen Rochel\n\
 n Dial in instructions:\n   -\n\n  https://chime.aws/8536075882\n\n
   Meeting ID: 8536 07 5882\n\n  United States Toll-Free: +1 855-552-446
 3  Meeting PIN: 8536 07 5882\n\n  One-click Mobile Dial-in (United Stat
 es (1)): +1\n  206-462-5569\,\,8536075882#\n\n  International: http
 s://chime.aws/dialinnumbers/\n  -\n\n   Agenda:\n   - TBD\n\n\nPlease f
 eel free to add agenda items to hangout wiki page\n\n.\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~::~:~::-\nPlease do not edit this section of the description.\
 n\nView your event at https://www.google.com/calendar/event?action=VIEW
 =M2FhdDQyYTBxa3BkNmdpcTdzbDdmbXA3MjkgZGV2QG14bmV0LmluY3ViYXRvci5hcGFjaGUub3
 Jn=MjgjcGVkcm8ubGFycm95Lmxpc3RzQGdtYWlsLmNvbWU3OWE2YWZjYWNjNDg1MTYyODU4
 ZDViY2IzM2U3N2ZjZDNmZTVkMjY=Europe%2FBerlin=en=1.\n-::~:~::~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180719T164005Z
LOCATION:Chime
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:MXNet hangout (I)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics


Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Sheng Zha
I'm guessing Mu's intention is to make it clear that such invitation is
extended by teams in Amazon/AWS instead of by committers, so as to avoid
the confusion of the naming "MXNet SDK". Suggestions to achieve the same
goal are welcome.

Best regards,
-sz

On Thu, Jul 19, 2018 at 9:09 AM, Isabel Drost-Fromm 
wrote:

>
>
> On 18/07/18 23:30, Mu Li wrote:
>
>> A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet SDK.
>>
>
> What exactly is the Amazon MXNet SDK? What is the AWS MXNet SDK?
>
> Your suggestion triggered my question because:
>
> https://www.apache.org/foundation/marks/#products
>
>
> Isabel
>
>


Re: Request for feedback: proposal for MXNet SDK Office hours

2018-07-19 Thread Isabel Drost-Fromm




On 18/07/18 23:30, Mu Li wrote:

A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet SDK.


What exactly is the Amazon MXNet SDK? What is the AWS MXNet SDK?

Your suggestion triggered my question because:

https://www.apache.org/foundation/marks/#products


Isabel



[RESULT][VOTE] Subscribe dev@ to Github Activities

2018-07-19 Thread Sheng Zha
Hi,

The vote concluded at 9PM today (2018/07/18), and here are the results:
+1
Timur Shenkao
Aaron Markham
Lin Yuan
Anirudh Acharya
Junru Shao
Yizhi Liu (committer)
Zhi Zhang (committer)
Tianqi Chen (committer)
Sheng Zha (committer)

-1
Qing Lan
Rahul Huilgol
K, S
Anirudh (committer)
Chris Olivier (committer)

The vote thread can be found here

(and
here
).
The original discussion thread can be found here

.

According to Apache Voting Process
, this procedural vote has
now passed.

However, some concerns has come up as part of the discussion on the voting
thread. Specifically, they are about increase in the amount of traffic (and
potentially noise) on dev list, and guidelines on how to manage them. In
light of that, I'd like to request that mentors help us connect with Apache
Infra team and help us explore our options on Github-Dev integration, and
hopefully we could find a solution that achieves the best balance.

For those who are interested, let's follow the best practice and continue
the discussion on managing the integration of Github with dev list in
parallel in the discussion thread
.
Thank you.

-sz