Re: Request to join MXNet slack channel

[Steffen Rochel]

HI Tali - welcome to the project. Added you to the ASF MXNet slack channel.
Steffen

On Wed, Aug 1, 2018 at 3:21 PM Taliesin Beynon
 wrote:

> Hello,
>
> I’d like to join the slack channel.
>
> Sorry if this is the wrong list to mail, but saw some others requests come
> this way!
>
> Thanks,
> Tali

Request to join MXNet slack channel

[Taliesin Beynon]

Hello,

I’d like to join the slack channel.

Sorry if this is the wrong list to mail, but saw some others requests come this 
way!

Thanks,
Tali

Re: MXNet Berlin Office Hours

[Steffen Rochel]

Ivan - you don't have to wait until next week, please feel free to post
your question on https://discuss.mxnet.io/ or here or u...@mxnet.apache.org.

Regards,
Steffen

On Wed, Aug 1, 2018 at 8:52 AM Marco de Abreu
 wrote:

> Hello Ivan,
>
> Sorry, the office hours were yesterday. It would be great if you could
> attend next week!
>
> Best regards,
> Marco
>
> Ivan Serdyuk  schrieb am Mi., 1. Aug. 2018,
> 17:28:
>
> > Nock-nock. Anybody in a meeting room?
> >
> > On Mon, Jul 16, 2018 at 12:27 PM, Anton Chernov 
> > wrote:
> >
> > > Dear MXNet community,
> > >
> > > As part of our customer support the MXNet Berlin team is offering
> office
> > > hours on Tuesdays 6pm-7pm (CEST) | 9:00am-10am (PST).
> > >
> > > They happen onsite in the Amazon Berlin office:
> > > Krausenstraße 38, 10117 Berlin in BER12 01.501
> > >
> > > Conference Bridge Information
> > >
> > > Chime meeting ID: 5461650798
> > > Join via browser screen share: https://chime.aws/5461650798
> > > Join via phone (US): +1-929-432-4463 <(929)%20432-4463>,,5461650798#
> > > Join via phone (US toll-free): +1-855-552-4463 <(855)%20552-4463>
> ,,5461650798#
> > > International dial-in: https://chime.aws/dialinnumbers/
> > > In-room video system: Ext: 62000, Meeting PIN: 5461650798#
> > >
> > > How can we help you?
> > >
> > > The following are a few examples of the types of consultations we
> > provide:
> > >
> > > * CI and infrastructure questions
> > > * Build system
> > > * Benchmarking
> > > * Edge devices (for example Raspberry Pi, Jetson)
> > > * C++
> > > * General questions
> > >
> > > Before attending
> > >
> > > Try finding answers on:
> > >
> > > * Our discussion forum (https://discuss.mxnet.io)
> > > * StackOverflow mxnet tag (https://stackoverflow.com/
> > > questions/tagged/mxnet)
> > > * MXNet website (https://mxnet.incubator.apache.org/faq/)
> > > * Github issues (https://github.com/apache/incubator-mxnet/issues)
> > >
> > > If this does not help:
> > >
> > > In advance fill out a github issue (
> > > https://github.com/apache/incubator-mxnet/issues/new) at least a few
> > days
> > > before so that the team member who will help with the issue gets a
> chance
> > > to prepare.
> > >
> > > Main point of contact through email: mxnet-edge-oncall-primary[at]a
> > > mazon.com
> > >
> > > Best regards
> > > Anton Chernov
> > >
> > > [1]
> > > https://cwiki.apache.org/confluence/display/MXNET/
> > > MXNet+Berlin+Office+Hours
> > >
> >
>

Re: Seattle meetup

[Steffen Rochel]

I just updated the agenda for the meetup in Seattle on August 16th 2018.
https://www.meetup.com/Apache-MXNet-Seattle-meetup/events/253104242/
We will have two tutorials:
(1) GluonNLP - a deep learning toolkit for Natural Language Processing
(2) Handwriting OCR with MXNet on AWS SageMaker

Please spread the word and hope to see you in Seattle. The plan is to
record and publish the meetup.
Please let me know suggestions and ideas you have for future topics.

Regards,
Steffen

On Tue, Jul 31, 2018 at 2:21 PM Marco de Abreu
 wrote:

> Hi,
>
> I just found this Meetup invite:
> https://www.meetup.com/Apache-MXNet-Seattle-meetup/events/253104242/
>
> Best regards,
> Marco
>

Re: MXNet Berlin Office Hours

[Marco de Abreu]

Hello Ivan,

Sorry, the office hours were yesterday. It would be great if you could
attend next week!

Best regards,
Marco

Ivan Serdyuk  schrieb am Mi., 1. Aug. 2018,
17:28:

> Nock-nock. Anybody in a meeting room?
>
> On Mon, Jul 16, 2018 at 12:27 PM, Anton Chernov 
> wrote:
>
> > Dear MXNet community,
> >
> > As part of our customer support the MXNet Berlin team is offering office
> > hours on Tuesdays 6pm-7pm (CEST) | 9:00am-10am (PST).
> >
> > They happen onsite in the Amazon Berlin office:
> > Krausenstraße 38, 10117 Berlin in BER12 01.501
> >
> > Conference Bridge Information
> >
> > Chime meeting ID: 5461650798
> > Join via browser screen share: https://chime.aws/5461650798
> > Join via phone (US): +1-929-432-4463,,5461650798#
> > Join via phone (US toll-free): +1-855-552-4463,,5461650798#
> > International dial-in: https://chime.aws/dialinnumbers/
> > In-room video system: Ext: 62000, Meeting PIN: 5461650798#
> >
> > How can we help you?
> >
> > The following are a few examples of the types of consultations we
> provide:
> >
> > * CI and infrastructure questions
> > * Build system
> > * Benchmarking
> > * Edge devices (for example Raspberry Pi, Jetson)
> > * C++
> > * General questions
> >
> > Before attending
> >
> > Try finding answers on:
> >
> > * Our discussion forum (https://discuss.mxnet.io)
> > * StackOverflow mxnet tag (https://stackoverflow.com/
> > questions/tagged/mxnet)
> > * MXNet website (https://mxnet.incubator.apache.org/faq/)
> > * Github issues (https://github.com/apache/incubator-mxnet/issues)
> >
> > If this does not help:
> >
> > In advance fill out a github issue (
> > https://github.com/apache/incubator-mxnet/issues/new) at least a few
> days
> > before so that the team member who will help with the issue gets a chance
> > to prepare.
> >
> > Main point of contact through email: mxnet-edge-oncall-primary[at]a
> > mazon.com
> >
> > Best regards
> > Anton Chernov
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/MXNET/
> > MXNet+Berlin+Office+Hours
> >
>

Re: MXNet virtual hangout 2018-August-1 8am and 5pm PDT

[Steffen Rochel]

Hi - it looks there has been confusion about the hangout scheduled for
today. I was on the 8am PDT call and chatted with Marco.
I will be on the call today Aug 1st 5pm PDT as well.
Please drop me a note if you missed the hangout notice or got confused due
to changes in the hangout invite and would like to get an a call next week.

Regards,
Steffen

On Sun, Jul 29, 2018 at 9:50 PM Steffen Rochel 
wrote:

> I would like to remind everybody about the hangout on August 1st 8am PDT
> and 5pm PDT. Please see also the hangout invitations from Pedro.
>
>
>
>-
>
>Dial in instructions:
>-
>
>   https://chime.aws/8536075882
>
>   Meeting ID: 8536 07 5882
>
>   United States Toll-Free: +1 855-552-4463 <(855)%20552-4463>
>   Meeting PIN: 8536 07 5882
>
>   One-click Mobile Dial-in (United States (1)): +1 206-462-5569
>   <(206)%20462-5569>,,8536075882#
>
>   International: https://chime.aws/dialinnumbers/
>
>
>-
>
>Agenda - see hangout wiki page
>
> .
>Feel free to add topics you consider important for the community.
>
>
> Regards,
> Steffen
>
> On Wed, Jul 18, 2018 at 10:32 AM Steffen Rochel 
> wrote:
>
>> I would like to invite for virtual hangout on 2018-August-1 8am and 5pm
>> PDT.
>>
>>-
>>
>>Dial in instructions:
>>-
>>
>>   https://chime.aws/8536075882
>>
>>   Meeting ID: 8536 07 5882
>>
>>   United States Toll-Free: +1 855-552-4463 <(855)%20552-4463>
>>   Meeting PIN: 8536 07 5882
>>
>>   One-click Mobile Dial-in (United States (1)): +1 206-462-5569
>>   <(206)%20462-5569>,,8536075882#
>>
>>   International: https://chime.aws/dialinnumbers/
>>   -
>>
>>Agenda:
>>- TBD
>>
>>
>> Please feel free to add agenda items to hangout wiki page
>> 
>> .
>> Hope to (virtually) see you on August 1st.
>>
>> Steffen
>>
>

Re: MXNet Berlin Office Hours

[Ivan Serdyuk]

Nock-nock. Anybody in a meeting room?

On Mon, Jul 16, 2018 at 12:27 PM, Anton Chernov  wrote:

> Dear MXNet community,
>
> As part of our customer support the MXNet Berlin team is offering office
> hours on Tuesdays 6pm-7pm (CEST) | 9:00am-10am (PST).
>
> They happen onsite in the Amazon Berlin office:
> Krausenstraße 38, 10117 Berlin in BER12 01.501
>
> Conference Bridge Information
>
> Chime meeting ID: 5461650798
> Join via browser screen share: https://chime.aws/5461650798
> Join via phone (US): +1-929-432-4463,,5461650798#
> Join via phone (US toll-free): +1-855-552-4463,,5461650798#
> International dial-in: https://chime.aws/dialinnumbers/
> In-room video system: Ext: 62000, Meeting PIN: 5461650798#
>
> How can we help you?
>
> The following are a few examples of the types of consultations we provide:
>
> * CI and infrastructure questions
> * Build system
> * Benchmarking
> * Edge devices (for example Raspberry Pi, Jetson)
> * C++
> * General questions
>
> Before attending
>
> Try finding answers on:
>
> * Our discussion forum (https://discuss.mxnet.io)
> * StackOverflow mxnet tag (https://stackoverflow.com/
> questions/tagged/mxnet)
> * MXNet website (https://mxnet.incubator.apache.org/faq/)
> * Github issues (https://github.com/apache/incubator-mxnet/issues)
>
> If this does not help:
>
> In advance fill out a github issue (
> https://github.com/apache/incubator-mxnet/issues/new) at least a few days
> before so that the team member who will help with the issue gets a chance
> to prepare.
>
> Main point of contact through email: mxnet-edge-oncall-primary[at]a
> mazon.com
>
> Best regards
> Anton Chernov
>
> [1]
> https://cwiki.apache.org/confluence/display/MXNET/
> MXNet+Berlin+Office+Hours
>

Re: Automated Flaky Test Detector

[Pedro Larroy]

Hi Carl

This is great, I like a lot the design for the tool. I think it will
prevent addition of flaky tests once is implemented.
I don't have major concerns with the design, please keep us updated with
PRs about this tool.

Thanks!

Pedro.

On Tue, Jul 31, 2018 at 3:01 AM Carl Tsai  wrote:

> Minor correction:
>
> I'm working with the *Apache* MXNet engine team at Amazon!
>
> Carl
>
> On Mon, Jul 30, 2018 at 5:42 PM Carl Tsai  wrote:
>
> > Hi all,
> >
> >
> >
> > My name is Carl Tsai, I’m an intern working with the Amazon MXNet engine
> > team. For the past several weeks, I’ve been working with my mentor Hao
> Jin
> > on an automatic flaky test detection system. As you may know, there’s an
> > ongoing effort to reduce the number of flaky tests in the code base, and
> > this flaky test detector is meant to help ensure that these efforts will
> > have a long-lasting impact on the quality of our tests.
> >
> >
> >
> > This is an automated tool that will be run on PR checks to detect flaky
> > tests before we merge them. It will check PRs for new and modified test
> > cases and run them through a flakiness checker so that we can have high
> > confidence that our tests are not flaky. There’s a design overview on
> > confluence
> > <
> https://cwiki.apache.org/confluence/display/MXNET/Automated+Flaky+Test+Detector
> >—
> > I’d be happy to hear any feedback!
> >
> >
> >
> > In the meantime, one of the components, the flakiness checker, has been
> > merged under the tools/ folder and I’d encourage those of you who are
> > working on flaky tests or writing new tests to try it out. Documentation
> > can be found on the confluence page for the project as well as on the
> Reproducing
> > Test Results Page
> > <
> https://cwiki.apache.org/confluence/display/MXNET/Reproducing+test+results
> >
> > under tips and tricks, and I’m open to suggestions on how to improve it.
> >
> >
> >
> > Thanks,
> >
> > Carl
> >
>

Re: Separate repo for MXNet infrastructure

[Pedro Larroy]

I like tools more.

On Wed, Aug 1, 2018 at 11:05 AM Marco de Abreu
 wrote:

> Hi,
>
> definitely a good point, Isabel. During our office hour we thought about
> creating a repository under the Apache account with a name like
> incubator-mxnet-tools or incubator-mxnet-infrastructure. Does anybody have
> other ideas for naming or maybe a better solution?
>
> Best regards,
> Marco
>
> On Wed, Aug 1, 2018 at 10:35 AM Isabel Drost-Fromm 
> wrote:
>
> >
> >
> > Am 1. August 2018 09:36:24 MESZ schrieb Yuelin Zhang <
> > zhangyuelinch...@gmail.com>:
> > >My concern is where should my code be finally merged. This bot is not a
> > >part of MXNet framework but it serves MXNet community. For now, a good
> > >option is to have a separate repo for infrastructure.
> >
> > As this would be something that serves the mxnet project, my advise would
> > be to make sure it ends up in a location that is controlled by the Apache
> > mxnet PMC, in a location that is mirrored back to ASF resources.
> >
> > Isabel
> >
> > --
> > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
> >
>

Re: Separate repo for MXNet infrastructure

[Marco de Abreu]

Hi,

definitely a good point, Isabel. During our office hour we thought about
creating a repository under the Apache account with a name like
incubator-mxnet-tools or incubator-mxnet-infrastructure. Does anybody have
other ideas for naming or maybe a better solution?

Best regards,
Marco

On Wed, Aug 1, 2018 at 10:35 AM Isabel Drost-Fromm 
wrote:

>
>
> Am 1. August 2018 09:36:24 MESZ schrieb Yuelin Zhang <
> zhangyuelinch...@gmail.com>:
> >My concern is where should my code be finally merged. This bot is not a
> >part of MXNet framework but it serves MXNet community. For now, a good
> >option is to have a separate repo for infrastructure.
>
> As this would be something that serves the mxnet project, my advise would
> be to make sure it ends up in a location that is controlled by the Apache
> mxnet PMC, in a location that is mirrored back to ASF resources.
>
> Isabel
>
> --
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
>

Re: Separate repo for MXNet infrastructure

[Isabel Drost-Fromm]

Am 1. August 2018 09:36:24 MESZ schrieb Yuelin Zhang 
:
>My concern is where should my code be finally merged. This bot is not a
>part of MXNet framework but it serves MXNet community. For now, a good
>option is to have a separate repo for infrastructure.

As this would be something that serves the mxnet project, my advise would be to 
make sure it ends up in a location that is controlled by the Apache mxnet PMC, 
in a location that is mirrored back to ASF resources.

Isabel

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Separate repo for MXNet infrastructure

[Yuelin Zhang]

Hello all,

I worked on a label bot which serves MXNet community. It is able to:
1. Send daily GitHub issue reports   (design
)
(PR 11861 )
2. Predict labels of unlabeled issues (design
)
(PR 11935  )
3. Help non-committers to add labels (design
)
(PR 11957 )

My concern is where should my code be finally merged. This bot is not a
part of MXNet framework but it serves MXNet community. For now, a good
option is to have a separate repo for infrastructure.

I will appreciate it if someone can share ideas.

Thanks,

Cathy