Thanks for the clarification, Naveen. I'd recommend against having wiki or
other mutable document for such discussion, because people's response (or
the lack of it in the case of lazy consensus) is only toward the version
they saw, which can be changed. Rather, it would likely be a better idea to
Sheng,
It is in the wiki, I also added a TOC to find it easily.
https://cwiki.apache.org/confluence/display/MXNET/PROPOSAL%3A+Apache+MXNet%28Incubating%29+Office+Hours#PROPOSAL:ApacheMXNet(Incubating)OfficeHours-How
?
How?
Developers would have 1 hour every week to dedicate to office hours
Hi Naveen,
While your enthusiasm is certainly appreciated, next time, shall we include
the "new Issue Type" in the discussion first? I found no prior mention on
this.
Also, a reminder to everyone that next time, let's respect Apache Infra's
time by following the instructions to have an Apache
If it is buggy, how does it matter if it is performant or not? I am not
seeing the rationale to make the correct version only opt-in.
On Mon, Jul 23, 2018 at 6:47 PM, Leonard Lausen
wrote:
> Currently the default kernel of nn.Embedding backward is known to be
> buggy on P3 instances or using
Hi, Hen,
Thanks a lot for your feedback, it is very valuable!
I should have been probably more explicit about idea and intention of providing
users with office hours channel of communication. The idea behind office hours
is to provide an additional communication channel to Apache MXNet users.
Noting that, as far as I can tell, there is no such thing as 'MXNet SDK',
'AWS MXNet SDK' or 'Amazon MXNet SDK'.
On Wed, Jul 18, 2018 at 2:30 PM, Mu Li wrote:
> A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet SDK.
>
> On Wed, Jul 18, 2018 at 2:22 PM, Davydenko, Denis <
>
My concerns on Office Hours are:
1) Voice and F2F are not very welcoming for a diverse community. There I
am, sitting in New Zealand, and you want me to get on the phone and wake up
the rest of the family to have a conversation. Or get on a plane.
2) Having to book time is also not very
done
On Mon, Jul 23, 2018 at 7:33 PM, Tao Sun wrote:
> Admin,
>
> Will you please grant me access to this channel? Thanks!
>
Hey All, just created a INFRA ticket(https://issues.apache.o
rg/jira/browse/INFRA-16805) requesting a new Issue Type "Office Hours" on
JIRA to better manage and support Office hours request.
One feedback I received was that "Apache" was neither mentioned in the
discussion nor in the PROPOSAL on
Admin,
Will you please grant me access to this channel? Thanks!
Noting that I find "MXNet Berlin team" a very confusing concept.
Does that mean "Apache MXNet committers who happen to live in Berlin?"
On Mon, Jul 16, 2018 at 2:27 AM, Anton Chernov wrote:
> Dear MXNet community,
>
> As part of our customer support the MXNet Berlin team is offering office
>
Currently the default kernel of nn.Embedding backward is known to be
buggy on P3 instances or using Cuda 9.2 (though the issue also occurs on
other instances with earlier version of Cuda, but less often).
https://github.com/apache/incubator-mxnet/issues/11314
There is currently an opt-in for
Thanks again for organizing Roshani. I believe the TensorRT work is ready
for a merge. Thanks to Marek and all the NVIDIA people for iterating on
it. If possible could a committer review, make sure it meets their
expectations and then merge? PR is here:
Hi All,
I had earlier filed an issue with functionality-duplication/code-refactor
here - https://github.com/apache/incubator-mxnet/issues/11811
As per the suggestion in the github issue I would like to bring it to the
attention of the wider community -
The operators defined in sample_op.cc and
Hello Roshani,
frequent releases are good and I'm supportive for this in general in order
to provide our users with the latest features and improvements. But at the
moment, I'm slightly concerned about the test coverage due to [1]. I want
us to be conscious about cutting a release even though not
I will share the slides and Jupyter Notebook that will be used for the talk.
Thanks
Sandeep
On Mon, Jul 23, 2018 at 1:37 AM Ivan Serdyuk
wrote:
> Ar least - your speakers could share slides
>
> On Mon, Jul 23, 2018 at 10:44 AM, Hagay Lupesko wrote:
>
> > No, unfortunately we're not planning
Hi all,
As mentioned before, code freeze date is today July 23rd. Please try to get
your ongoing PRs merged by today.
Please let me know if there are any concerns or need more time.
Thanks,
Roshani
On Thu, Jul 19, 2018 at 1:16 PM Anirudh Acharya
wrote:
> @sandeep krishnamurthy the bug fixes
Ar least - your speakers could share slides
On Mon, Jul 23, 2018 at 10:44 AM, Hagay Lupesko wrote:
> No, unfortunately we're not planning to stream or record the meetup
> (equipment/budget)
>
> On Fri, Jul 20, 2018 at 9:36 AM Ivan Serdyuk >
> wrote:
>
> > Are you providing streaming or
No, unfortunately we're not planning to stream or record the meetup
(equipment/budget)
On Fri, Jul 20, 2018 at 9:36 AM Ivan Serdyuk
wrote:
> Are you providing streaming or recording?
>
> On Fri, Jul 20, 2018 at 7:27 PM, Hagay Lupesko wrote:
>
> > Hey folks,
> >
> > Sandeep and me are hosting a
19 matches
Mail list logo
