Dear MXNet Community:
There is a great discussion going on in terms of lowering the barrier of
entries and encourage more contribution to the project. One of the general
goals is to encourage a broader pool of contributions. I want to make the
following proposal:
Besides Committers and PMC, let
+1 Great idea. Adding a name to the contributor list is a good idea. Also,
I've found that thanking the person for the review on the PR is another way
to express gratitude for their time and effort.
On Fri, Oct 19, 2018 at 2:51 PM Tianqi Chen wrote:
> Dear MXNet Community:
>
> There is a great
+1
reviews are great contributions given that it takes good understanding and
investment of time to provide insightful feedback.
On Fri, Oct 19, 2018 at 11:51 AM Tianqi Chen wrote:
> Dear MXNet Community:
>
> There is a great discussion going on in terms of lowering the barrier of
> entries and
Dear MXNet Community:
There is a great discussion going on in terms of lowering the barrier of
entries and encourage more contribution to the project. One of the general
goals is to encourage a broader pool of contributions. I want to make the
following proposal:
Besides Committers and PMC, let
Hello everyone!
I'm writing this note to raise awareness about some issues I'm seeing with
the Python API docs. While some of the issues can be traced back prior to
v1.3.0, the biggest issue of docs not rendering is fairly recent.
At a high level, Sphinx (our Python API docs generator) is getting
I did pip install mxnet-mkl==1.3.1b20181018 on an AMD Ryzen 1950X and unit
tests are passing.
Is this build using AVX512? in /proc/cpuinfo I see only "avx" flag.
There's no "avx2" like on recent intel cpus.
Pedro.
On Fri, Oct 19, 2018 at 5:12 PM Hagay Lupesko wrote:
> Awesome collaborative
Great!
I started a rough draft for collaboration at
https://cwiki.apache.org/confluence/display/MXNET/Become+a+Committer+Proposal
.
Everyone feel free to enhance and provide feedback.
- Carin
On Fri, Oct 19, 2018 at 10:55 AM Steffen Rochel
wrote:
> +1, great suggestion, thanks Carin!
> I'm
Allright then, I closed that PR. Thanks for your feedback.
On Wed, Oct 17, 2018 at 9:06 PM kellen sunderland <
kellen.sunderl...@gmail.com> wrote:
> May be of interest to people that we're trying get a good set of
> production-ready Dockerfiles (which I'm referring to as runtime Dockerfiles
> in
Awesome collaborative effort across many contributors and companies!
The boost is impressive and for MXNet users to get this boost "out of the
box" is a great benefit and makes MXNet an even better choice.
Alex - can you clarify whether there are any down sides with regards to
noon AVX-512
Dave - invited you to MXNet slack channel. Thanks for contributing to MXNet
& Clojure project.
Steffen
On Fri, Oct 19, 2018 at 5:53 AM Dave Liepmann
wrote:
> Hi, could I get an invitation to the MXNet slack? I'm working with the
> Clojure contrib project and
>
I think in general it's always a good idea to reduce barriers to entry into
the project. Therefore I think separating committer and PMC roles is a good
idea, as it helps encourage and recognize contributors by giving them
commit early; and then it allows the new committers to spend some more time
If there is no downside on platforms not supporting AVX512 instructions,
then +1
On Wed, Oct 17, 2018, 14:10 Alex Zai wrote:
> Hey all,
> We have been working hard these past few months to integrate and stabilize
> Intel’s MKLDNN deep learning CPU accelerator into Mxnet and have made
>
Python 2.7 reaches End of Life by the end on 2019.Take that into account.
About Python 3.x, why not having 3.6 docker images? I know 3.7 is not yet
supposed by MXNet. But starting with 3 5 doesn't make much sense for me
On Wed, Oct 17, 2018, 11:52 Meghna Baijal
wrote:
> Hi All,
>
> I am
Hi, could I get an invitation to the MXNet slack? I'm working with the
Clojure contrib project and
https://mxnet.incubator.apache.org/community/mxnet_channels.html said this
is the place to ask.
Thanks in advance,
Dave
Background:
There is a desire to increase the committer pool and grow the community.
This thread is to discuss the possibility of revision the current committer
criteria in light of the following goals:
- Make it easier to newcomers to be committers
- Recognize non-code contributions as paths to
15 matches
Mail list logo