Re: Propose to discontinue supporting Apache MXNet on Windows 7

FWIW, my company is only beginning to transition to Windows 10 now, and my past experience would lead me to believe that many enterprises stick with old versions of Windows long past when you think they would. Seems to me that if you are unwilling to deprecate python 2.7, then continuing to

Re: [VOTE] Subscribe dev@ to Github Activities

ecoupling the recognized forum from > the technology they use, and that github contributors can easily > communicate with the community on the list. > > -sz > > On Wed, Jul 18, 2018 at 9:05 AM, Barber, Christopher < > christopher.bar...@analog.com> wrot

Re: [VOTE] Subscribe dev@ to Github Activities

stead. Indu On Wed, Jul 18, 2018, 5:51 AM Barber, Christopher < christopher.bar...@analog.com> wrote: > Can't people already subscribe to github notifications? I think it is safe > to assume that developers are already smart enough to figure out h

Re: [VOTE] Subscribe dev@ to Github Activities

Can't people already subscribe to github notifications? I think it is safe to assume that developers are already smart enough to figure out how to do that if they want. What problem are you really trying to solve here? On 7/18/18, 4:49 AM, "Chris Olivier" wrote: -1. (changed from -0.9)

Re: users@mxnet

Whatever you do, make sure to list all these information sources in one easy-to-find place. For instance, it may not be very obvious to anyone that they can read the dev mailing list on lists.apache.org. It is bad if users aren't even aware that other channels exist. On 6/18/18, 2:45 PM,

Re: users@mxnet

I don't understand why you would want a users mailing list when you already have discussion forums. Users that want to be notified of new posts on the forum can configure their notification preferences appropriately. The traffic on the forums is already pretty low. I would think you would not

Re: MXNet Name Change?

Yes, I think it is kind of late to try to get people to say "mix-net" and it makes it seem like yet another complex technology that no one even knows how to pronounce (e.g. LaTeX). Most English speakers are going to say "em-ex-net". If you really want people to say "mix-net" then you should

Re: MXNet Name Change?

While the name could be better, I would instead focus on (1) making mxnet much more extensible (e.g. support ability to dynamically load operators from external shared libraries), (2) feature parity with tensorflow, (3) support for non-NVIDIA GPUs, (4) clearly demonstrating and publicizing

Re: [VOTE] Change Scala namespace from dmlc to org.apache

ld code for much longer than you anticipated (especially if changed go into the old implementation). On Tue, Mar 13, 2018 at 9:11 AM, Barber, Christopher < christopher.bar...@analog.com> wrote: > Personally, I believe that MXNet jumped the gun on 1.0. It is pretty

Re: [VOTE] Change Scala namespace from dmlc to org.apache

That sounds like a lot of work and it would be easy to get wrong if it is even feasible. On 3/13/18, 11:51 AM, "kellen sunderland" wrote: I don't know about aliasing a namespace in Scala, but I wonder how hard it would be to either (1) provide a fascade

Re: Following semantic versioning

o.larroy.li...@gmail.com> > wrote: > > > This is a good point. What additional blockers would there be for linking > > against a user provided library with custom operators? > > > > > > > > On Tue, Mar 6, 2018 at 5:16 PM, Barber, Christopher &l

Re: Following semantic versioning

To avoid this kind of problem, you really need to support features that allow MXNet to be extended without having to resort to forking. There is currently no way to add C++ custom operators without forking, and no way to share such operators across projects. This creates a perverse incentive to

Re: Display the master branch website in default for a period

. März 2018, 22:11: > Do you have specific public benchmarks in mind? > > On Mar 1, 2018 10:13, "Barber, Christopher" <christopher.bar...@analog.com > > > wrote: > > > I think one thing that could draw more users would

Re: Proposal for treating warnings as errors in Linux & Clang builds (-Werror)

Tue, Jan 16, 2018 at 7:48 AM Marco de Abreu < > marco.g.ab...@googlemail.com<mailto:marco.g.ab...@googlemail.com>> > wrote: > > So you're proposing to have a stage AFTER test execution which would report > warnings as errors? While this is a good id

Re: Proposal for treating warnings as errors in Linux & Clang builds (-Werror)

Personally, I don’t like treating warnings as errors because it prevents compilation from completing and causes you to lose any ability to test the code and get any other information. Killing the build because of a failed warning for something that might not matter means that you may not find

Re: Increase indentation limit from 100 to 120 characters

For languages like C++ and Java it is hard to stay within 80 columns without resorting to overly terse naming scheme or awkward indentation. 120 really makes a lot of sense for C++ and it seems easier to adopt the same standard throughout the codebase since it may be annoying or difficult to