Welcome Jim, appreciating your support.
Steffen
On Mon, Jun 18, 2018 at 3:14 PM Naveen Swamy wrote:
> Hi All,
>
> I am excited to announce that we have an additional mentor for MXNet: Jim
> Jagielski, the cofounder of Apache, he brings vast experience in building
> and growing successful
That is great news!
Welcome on board Jim!
On Mon, Jun 18, 2018, 15:14 Naveen Swamy wrote:
> Hi All,
>
> I am excited to announce that we have an additional mentor for MXNet: Jim
> Jagielski, the cofounder of Apache, he brings vast experience in building
> and growing successful communities
Hi,
This is the vote to release Apache MXNet (incubating) version 1.2.1. Voting
will start now and close Thursday June 21st 7:00 PM PDT.
Link to release candidate 1.2.1.rc0:
https://github.com/apache/incubator-mxnet/releases/tag/1.2.1.rc0
View this page for installation instructions:
Thanks for your input. Do these tests really require a p3 or would g3 be
sufficient? We got 2 GPUs on the g3 instances and they are a lot
-Marco
Indhu schrieb am Mo., 18. Juni 2018, 15:02:
> I was working on testing the notebooks from https://gluon.mxnet.io/ as
> part
> of the nightly tests to
Hi all,
Since there are some issues with publishing scala package to maven, the
1.2.1 vote doesn't have to be blocked for the Scala package release.
I will create the vote for 1.2.1.rc0 soon.
Anirudh
On Mon, Jun 18, 2018 at 1:27 PM, Anirudh wrote:
> Hi Sina,
>
> RC is available here:
I am personally not a big fan of mailing list but agree with Thomas
that we may get extra users, which worth a try.
On the other hand, I also have concern that we do not have a community
big enough to support multiple forums. If people asked questions but
got no response, that can be worse than
I was actually the one stating that we didn't need a user mailing list
during the Seattle meetup, given all the reasons already exposed above.
However given what proponents of a mailing list said, I personally wouldn't
mind adding a new channel as a user mailing list, and monitoring it. There
I agree with Tianqi, Eric and others. We shouldn't dilute the community
with another forum. Disqus is already working and has healthy
participation, you can get an email digest if you so desire. Subscribing to
a mailing list to get a question answered is quite a heavyweight investment
for many
"Mailing list is an obsolete legacy for old projects"...
Not true. If you don't understand the reason and rationale and *benefits* of
using a mailing list, and why they are so core to how Apache runs projects, I'd
be happy to provide some data.
> On Jun 18, 2018, at 2:53 PM, Eric Xie wrote:
>
Hi All,
I am excited to announce that we have an additional mentor for MXNet: Jim
Jagielski, the cofounder of Apache, he brings vast experience in building
and growing successful communities around projects. I am sure we will be
able to tap into his experience to bring alignment and build a
Hi all,
I was at the FOSS Backstage/Apache EU Roadshow last week, it covered many
important topics in open-source software and governance. I also gave a
presentation on Distributed Inference using Apache MXNet and Apache Spark.
I also had the opportunity to listen and meet some of the Open
Anirudh, I have tried to fix and automate parts of the publish process and
written down the process. If everything works as expected & since it takes
building on 3 different platforms it could take 4-6 hours. We will also
continue to automate this further. This is excluding the time it needs to
I was working on testing the notebooks from https://gluon.mxnet.io/ as part
of the nightly tests to make sure we notice any API change that could break
code in those notebooks.
The README in the nightly folder said the tests are being run on machines
with multiple GPUs. I was wondering if I have
Hi,
Currently, we have two methods for single-machine communication:
parameter server and NCCL ring reduction. Both of these methods have
some downsides. Parameter server does not differentiate between NVLink
connections and PCI-E, so it ends up using the higher latency and
slower PCI-E
Thanks Meghna. Do you know what hardware the nightly tests are currently
running on? I'm adding some nightly tests. It will be useful to know.
On Mon, Jun 18, 2018 at 9:11 AM Meghna Baijal
wrote:
> Hi,
> This readme is incorrect and I am fixing this as a part of the nightly
> tests PR soon.
>
Hagay,
Thanks! I added the MXNet 1.3 page.
Please let me know if you need me to add any other details.
- Carin
On Mon, Jun 18, 2018 at 4:01 PM, Hagay Lupesko wrote:
> Carin,
>
> Thanks for contributing so much to MXNet!
> I just went through the planned MXNet v1.3 release scope [1], and did
Hi Sina,
RC is available here:
https://github.com/apache/incubator-mxnet/releases/tag/1.2.1.rc0 . We are
waiting to publish scala package to maven before we start the vote. Naveen,
Qing and Andrew are working on this.
Anirudh
On Mon, Jun 18, 2018 at 1:18 PM, Afrooze, Sina
wrote:
> Just
Just wondering if there is any estimate on when a 1.2.1 RC may be created? We
are using 1.3.0 beta builds because those are the only pip-install-able builds
available, but they introduce some instability in our workflow that we'd like
to avoid by switching to a 1.2.1 build. - Sina
On
Carin,
Thanks for contributing so much to MXNet!
I just went through the planned MXNet v1.3 release scope [1], and did not
see the Clojure package. I think it would be a great addition to MXNet, and
initially can be marked as experimental.
Did you consider adding it to MXNet 1.3 as an
I like the idea to have a user mail list, it should be able to cover the
user segment who prefer to use mail lists. Though my concern is how many of
us will be volunteered to maintain this list. We have several contributors
actively maintain the forum, including Sina, Thom, and Thomas. We need
Well, there is a trend to for speaking about MXNet (Ukraine). At least I
have visited a meetup (with a workshop).
On Mon, Jun 18, 2018 at 9:42 PM, Sebastian wrote:
> I am puzzled by the reluctance of this project to setup a user mailinglist
> to be honest.
>
> MXNet has major issues with
Neither TF nor Pytorch uses mailing lists though. In fact I can't think of any
deep learning community that uses mailing lists. Mailing list is an obsolete
legacy for old projects. No point in bringing it into new projects.
Thanks,
Eric
On 2018/06/18 18:42:12, Sebastian wrote:
> I am puzzled
IMHO, the approach(mail list or discuss) have nothing to do with the
popularity of the project. If you look at TF or pytorch you mentioned.
Pytorch uses discuss forum and slack, tf uses stackoverflow for support.
Both are popular but not adopting maillist. Note that I know both are both
not
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,
On 6/18/2018 9:18 PM, Jim Jagielski wrote:
> IMO, that is the wrong way to look at it.
>
> A users@ mailing list is a great, easy, low-cost and low-overhead way of
> *increasing* the user community and providing an extra level of support.
> Unless there is "strong evidence" that this is NOT
I am puzzled by the reluctance of this project to setup a user
mailinglist to be honest.
MXNet has major issues with attracting a community outside of Amazon
(whenever I hear folks talking about deep learning, they usually mention
tensorflow, pytorch and keras, but I rarely hear someone talk
Hi Naveen,
Sorry I missed this. Can you please elaborate on how long it takes
typically for publishing the scala packages to maven before the vote?
I think if there is considerable churn in publishing these packages today,
we should not wait for the package for the vote as we may sacrifice our
Facebook is definitely a bad idea: we will be dependent on third party
provider + unclear who & how manages such group etc.
Forum + Confluence + Slack is much better then.
On Mon, Jun 18, 2018 at 7:17 PM, Ivan Serdyuk
wrote:
> Greetings Barber, Christopher. I had an idea to move out some
Hi,
Currently, we have two methods for single-machine communication:
parameter server and NCCL ring reduction. Both of these methods have
some downsides. Parameter server does not differentiate between NVLink
connections and PCI-E, so it ends up using the higher latency and
slower PCI-E
Greetings Barber, Christopher. I had an idea to move out some discussions,
covering Java and Scala API, to Facebook. So if somewhere exists a local
JUG or Scala user group - they could reflect the topic of discussion. But
background stuff could take place on mailing lists, Slack, forum, whatever.
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
IMO, that is the wrong way to look at it.
A users@ mailing list is a great, easy, low-cost and low-overhead way of
*increasing* the user community and providing an extra level of support. Unless
there is "strong evidence" that this is NOT the case, I would recommend we
create the list.
> On
Hi,
This readme is incorrect and I am fixing this as a part of the nightly
tests PR soon.
Thanks,
Meghna
On Sun, Jun 17, 2018 at 7:05 AM kellen sunderland <
kellen.sunderl...@gmail.com> wrote:
> I'm not a commiter, but I would say this is clearly not correct. I would
> propose removing the doc
33 matches
Mail list logo
