Hi, MXNet community,
I would like to suggest that we (participants of dev@ list) spend couple more
days thinking about and discussing proposal for office hours and then, if no
active discussion is happening, move towards lazy vote to get to conclusion on
whether we can incorporate suggested pra
Sheng, cwiki keeps versions of page edits, you could always compare based
on the discussion date on dev@. Moving the page might or might not be an
issue, I would use caution on moving pages. I have seen other communities
use Google Doc, cwiki provides a central place to capture all process and
desi
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
i
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
meeting
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 men
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. I
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 <
> dz
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 welcoming.
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
Yes Naveen, I think you are saying exactly the same as I hinted. Sheng also
agreed with this.
Pedro.
On Thu, Jul 19, 2018 at 6:54 PM Naveen Swamy wrote:
> I do not think there needs to be a distinction made for
> support/office-hours by committer or contributors(in this case Amazon
> employed c
Thanks. Yeah, I think naming after focused area instead of Amazon internal
organization/team names would likely work better. That way, others who'd
like to offer help in that area can just jump in and start helping.
-sz
On Thu, Jul 19, 2018 at 9:51 AM, Pedro Larroy
wrote:
> There's an MXNet com
I do not think there needs to be a distinction made for
support/office-hours by committer or contributors(in this case Amazon
employed contributors) -- correct me if I misunderstood your guess :).
Like I said, I would rather call it MXNet Office hours and categorize the
kind of support that is offe
There's an MXNet comitter in our office hours (Marco de Abreu @marcoabreu),
others are contributors such as Anton (@lebeg) or others. I think we could
refocus the conversation to the point that the office hours might have some
emphasis in a particular area of MXNet.
On Thu, Jul 19, 2018 at 6:21 PM
I'm guessing Mu's intention is to make it clear that such invitation is
extended by teams in Amazon/AWS instead of by committers, so as to avoid
the confusion of the naming "MXNet SDK". Suggestions to achieve the same
goal are welcome.
Best regards,
-sz
On Thu, Jul 19, 2018 at 9:09 AM, Isabel Dro
On 18/07/18 23:30, Mu Li wrote:
A minor suggestion: rename MXNet SDK to AWS MXNet SDK or Amazon MXNet SDK.
What exactly is the Amazon MXNet SDK? What is the AWS MXNet SDK?
Your suggestion triggered my question because:
https://www.apache.org/foundation/marks/#products
Isabel
I think this should be called MXNet Office hours and in a subsection spell
what is supported now(expectation)? Amazon contributors could lead part of
the effort? and later have other interested contributors join this effort.
On Wed, Jul 18, 2018 at 2:30 PM, Mu Li wrote:
> A minor suggestion: ren
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 <
dzianis.davydze...@gmail.com> wrote:
> Hello, MXNet community,
>
> Following up on recent announcement of office hours introduction from
> MXNet Berlin team, we are tryi
17 matches
Mail list logo
