Re: Retrospective: MXNet release process

2017-09-17 Thread Seb Kiureghian
In addition to your points, releases should be on apache.org and its mirror network. Not on github.com. On Fri, Sep 15, 2017 at 5:45 PM, pracheer gupta wrote: > Hi dev@, > > As you are aware MXNet recently had its first release under the Apache > banner. > > > As a first-time release, there was

Re: Discussion Forums?

2017-09-17 Thread Greg Stein
Let me refine that statement a little bit: * you asked, "handling user support" ... no decisions are made there, so the Foundation doesn't require a permanent record * BUT. development *decisions* must be handled on an Apache-archived mailing list. My apologies, that should have been in the list

Re: Discussion Forums?

2017-09-17 Thread Greg Stein
Anywhere is just fine. You will have to work harder for discoverability, but the Foundation has never mandated on-our-hardware for community interactions. On Sun, Sep 17, 2017 at 11:02 PM, Seb Kiureghian wrote: > Thanks Greg! Just want to clarify, if the community intends to use the > forum as a

Re: Discussion Forums?

2017-09-17 Thread Seb Kiureghian
Thanks Greg! Just want to clarify, if the community intends to use the forum as a primary mode of handling user support, does it need to be hosted on the VM provided by Apache, or can we host it elsewhere? Thanks, Seb On Sun, Sep 17, 2017 at 8:57 PM, Greg Stein wrote: > On Sun, Sep 17, 2017 at

Re: Discussion Forums?

2017-09-17 Thread Greg Stein
On Sun, Sep 17, 2017 at 6:30 PM, Seb Kiureghian wrote: >... > Discourse is open source so we can host it on Apache infrastructure and > include it on our site. To be clear: each community gets a single VM, and they are responsible for running that VM (we provide a base level system, with approp

Re: Discussion Forums?

2017-09-17 Thread Clebert Suconic
An advantage of apache is apache people from other projects. If you use the standard mail lists that will make it clearer for other developers from other groups to pick up your list and contribute. I mean I would know how to find your list easily. But If you advertise something different than yo

Re: Integrating a forum with the mailing lists for better usability

2017-09-17 Thread Seb Kiureghian
We got some clarification in the other thread from general@incubator. There is no official policy on forums other than (1)The main way people interact has to be on Apache infrastructure and (2)All decisions must be made on the mailing lists. Given these two rules, we have two options for setting up

Re: Discussion Forums?

2017-09-17 Thread Chris Mattmann
Thanks, Seb. From: Seb Kiureghian Reply-To: "sebou...@gmail.com" Date: Sunday, September 17, 2017 at 4:30 PM To: "dev@mxnet.incubator.apache.org" Cc: "mattm...@apache.org" , "gene...@incubator.apache.org" Subject: Re: Discussion Forums? are you making it so that the default way t

Re: Discussion Forums?

2017-09-17 Thread Seb Kiureghian
> > are you making it so that the default way to interact with *Apache* MXNet > (note emphasis) to not be on Apache infrastructure? Discourse is open source so we can host it on Apache infrastructure and include it on our site. I will suggest PonyMail on the original thread and see what the commu

Re: Discussion Forums?

2017-09-17 Thread Chris Mattmann
Hi, I can’t stress this enough – tooling is all fine and dandy, but are you making it so that the default way to interact with *Apache* MXNet (note emphasis) to not be on Apache infrastructure? There is no official policy other than if it didn’t happen on the list, it didn’t happen. Decisions

Re: Discussion Forums?

2017-09-17 Thread Seb Kiureghian
Hi Chris, Members of the Apache MXNet community have pointed to the high level of activity on Pytorch's forum as a reason to use Discourse. Discourse has a lot of great community features which make it easier to have a discussion, follow specific questions, and learn

[BUILD FAILED] Branch master build 392

2017-09-17 Thread Apache Jenkins Server
Build for MXNet branch master has broken. Please view the build at https://builds.apache.org/job/incubator-mxnet/job/master/392/

[BUILD FAILED] Branch master build 393

2017-09-17 Thread Apache Jenkins Server
Build for MXNet branch master has broken. Please view the build at https://builds.apache.org/job/incubator-mxnet/job/master/393/

[BUILD FAILED] Branch master build 390

2017-09-17 Thread Apache Jenkins Server
Build for MXNet branch master has broken. Please view the build at https://builds.apache.org/job/incubator-mxnet/job/master/390/

[BUILD FAILED] Branch master build 391

2017-09-17 Thread Apache Jenkins Server
Build for MXNet branch master has broken. Please view the build at https://builds.apache.org/job/incubator-mxnet/job/master/391/