Re: Requesting slack access

[Chaitanya Bapat]

Hello Jagadeesh,

Welcome to the MXNet community. Have sent you an invite at
jagadeesh.01101...@gmail.com
Let us know more about your use case and how you found out about MXNet.

Welcome once again
Cheers,
Chai

On Fri, 25 Oct 2019 at 23:11, Jagadeesh kotra 
wrote:

> Hi,
>
> I would like to join slack channel.
>
> Here's my GitHub
> https://github.com/jkotra
>


-- 
*Chaitanya Prakash Bapat*
*+1 (973) 953-6299*

[image: https://www.linkedin.com//in/chaibapat25]
[image: https://www.facebook.com/chaibapat]
[image:
https://twitter.com/ChaiBapchya] [image:
https://www.linkedin.com//in/chaibapat25]

Re: ONNX Support

[Hen]

On Mon, Oct 7, 2019 at 6:32 PM Chaitanya Bapat  wrote:

> Thanks a lot everyone for chiming in.
>
> Update: The issue in my PR was a bug (unrelated to ONNX) I introduced while
> switching from GPU to non-GPU 2D transpose support. Thanks to Xingjian Shi
>  for pointing that out. Apologies from my
> side.
>
> As it stands now, the PR passes. I added a unit test to track that bug. So
> we don't need any disabling.
>
> Since this wasn't related to ONNX per se, I guess the premise behind this
> discussion is now null and void.
> Also as it turns out, there are customers who use MXNet with ONNX so we
> might have to continue testing and supporting (even if in maintenance mode)
>
>
Note that 'we' there is a bit vague. Apache does not have customers, so
there's no "we have to continue".

If the community no longer has belief/trust/energy/interest in the code,
then one approach is to remove it from the primary build and put it into a
separate directory or repository. You can add a readme on how to
re-integrate it and a note that if someone is interested in contributing to
it then the community will do their best to respond.

Or you can delete it. Amazon can always fork the code in a separate repo
for their customers.

Hen