Re: Suggestions on how to increase community involvement on Apache MXNet incubating?

As mentioned by others, it is very important for the community to know what is happening, roadmap, low hanging bug fix or feature development. Along with that, it is hard and time-consuming to get a basic high-level understanding of various components, architecture and packages of MXNet. My 2

Re: Refactoring MXNet scala code to use "org.apache.mxnet"

Suneel, I tend to think for this issue, GitHub issue is good enough and we do not need JIRA. Can you clarify what is the advantage you see in using JIRA over GitHub issue for this specific case? Thanks! Hagay On 1/4/18, 16:34, "Suneel Marthi" wrote: Jira has been

Re: Refactoring MXNet scala code to use "org.apache.mxnet"

Jira has been around for a while - https://issues.apache.org/jira/projects/MXNET/ switch to using jira On Thu, Jan 4, 2018 at 7:31 PM, Roshani Nagmote wrote: > Hi, > > As currently, MXNet does not have Jira project, I have created github issue > for now. >

Re: Refactoring MXNet scala code to use "org.apache.mxnet"

anywhere to mark it as a breaking change in the latest version? On Thu, Jan 4, 2018 at 2:16 PM, Roshani Nagmote wrote: > Hello all, > > I am working on publishing mxnet-scala release to maven repository and as a > part of that, I will also be refactoring mxnet-scala

Re: Refactoring MXNet scala code to use "org.apache.mxnet"

Is there a Jira for this? Please create a Jira and reference that in the PR for this. On Thu, Jan 4, 2018 at 5:16 PM, Roshani Nagmote wrote: > Hello all, > > I am working on publishing mxnet-scala release to maven repository and as a > part of that, I will also be

Re: Suggestions on how to increase community involvement on Apache MXNet incubating?

I think the main point being raised is an easy way to know what is happening and proposals. Github has quite a lot of nice features with respect to this: - Issues make perfect sense in terms of discussing a single-point of feature/bug and get feedback from anyone who can comment, additionally

Re: Suggestions on how to increase community involvement on Apache MXNet incubating?

Hello Markus, first of all, very good points! Regarding (1): In my opinion, we should always have some time of chat as this is the most convenient way for users and contributors to ask a quick question. I agree that proper discussions should be held on dev@, but sometimes a quick discussion in a

Re: Suggestions on how to increase community involvement on Apache MXNet incubating?

I really like most of what has been said, and the below might be a bit of a repeat, but through a different lens. One key aspect to consider when thinking about participation in OSS projects is the journey a contributor makes, which starts before even using the software. Each of the steps of the

Re: [DISCUSS] Build OSX builds in CI (possibly with TravisCI).

Hope everyone had a good break. Just wanted to check if there were further thoughts on OSX builds. Chris, did you have time to look into virtualizing Mac OS? Would it make sense for us to put something in place in the interim e.g. the clang solution? On Tue, Dec 12, 2017 at 7:59 PM, de Abreu,

Re: Suggestions on how to increase community involvement on Apache MXNet incubating?

Agreed with Chris and Jeff. Googling for MXNet roadmap is enlightening. Also the communication channels are disperse. I would remove suggesting "Ask questions" in issues in the README.md because this encourages inflation of issues that are just questions. We should link to the slack channel or