Re: About Becoming a Committer

[Pedro Larroy]

* I personally don't like the idea that comittership status is decided in a
closed mail list. This is not the transparency level that I would expect in
an open source project. I'm happy to receive feedback from others that
might be opposed to my application for committer to know what things could
be improved to get there. I have been doing a plethora of contributions to
the project over a year including ARM support, Android and CI, obviously
some of this work together with my team at Amazon (@lebeg,
@KellenSunderland, @marcoabreu). I don't have visibility on how much longer
one has to wait, or what needs to be improved to get there.

* My team is on-call for CI / CD which is also sponsored by us. To fix
problems promptly we would need write permissions to the repository. This
would normal in any other project, be open source or corporate. I think
it's not effective to be on-call when you can't submit critical fixes and
wait days for a CR. Basically I think everyone responsible or involved in
CI should have access rights. As you know, testing our project is a
challenging task for reasons discussed before.

Please comitters and mentors, provide a solution that allows us to work
more effectively and move the project forward faster, as is vital to make
it easier to contribute so we can attract more users.

Pedro.

On Tue, Jun 12, 2018 at 10:31 AM Yasser Zamani 
wrote:

>
>
> On 6/9/2018 12:45 AM, Sheng Zha wrote:
> > There have been a couple of offline inquiries from contributors about
> > becoming a committer. From those inquiries, it seems that there’s
> confusion
> > in our community about how to become a committer, so I’d like to take
> this
> > opportunity to clarify.
> >
> > The guideline about becoming a committer can be found at
> > https://cwiki.apache.org/confluence/display/MXNET/Becoming+a+Committer.
>
> I think that page at above link is great but the problem is new visitors
> cannot find it quickly then they ask privately from you. I myself was
> looking for it at mxnet.incubator.apache.org, so clicked on
> "Community->Contribute", the I read all page then I saw a link to wiki
> on page i.e. "MXNet Confluence Wiki: Development" where I guessed I
> might find something in wiki so clicked that. Then I saw "Becoming a
> Committer" in left side wiki's menu.
>
> I think we'll get fewer private inquiries on this if we add a direct
> link about it at
> https://mxnet.incubator.apache.org/community/contribute.html
>
> Regards.
>

Re: GitHub Label Bot Design

[Marco de Abreu]

Hello Cathy,
that's a great proposal. Thank you!

A few comments from my side:
- Good idea with the alias. We should have a special email-list for
automated reports to prevent spamming dev@.
- "Create weekly email to internal team members:" -> email-list
- "Part II - Label Bot - Amazon cloudwatch event (a) will trigger lambda
function(a) 9am every Monday. " -> Why don't we try to classify them ASAP?
- "This bot should have restricted permissions to avoid unexpected
operations." -> AFAIK, Apache does not allow bot accounts and we have to
use a committers credentials instead. This is not a big issue since we
already do this, but just to keep that in mind.

Best regards,
Marco

On Tue, Jun 12, 2018 at 1:07 PM Yuelin Zhang 
wrote:

> Sorry for the messed up url format.
> Please forward to this link: https://tinyurl.com/mxnetbot
>
>
> Thanks,
> Cathy
>
>
> On Tue, Jun 12, 2018 at 10:20 AM, Yuelin Zhang  >
> wrote:
>
> > Hi,
> >
> > Currently there are many issues on Incubator-MXNet
> >  repo, labeling issues can
> > drive attention of  contributors to specific areas. Right now, issues are
> > all manually labelled, which is time consuming.  And every time
> maintainers
> > need to @ a committer to add labels.
> > I am working on this label bot to automate/simplify this labeling issue
> > process and send weekly report to maintainers. Design proposal is on
> cwiki:
> > https://cwiki.apache.org/confluence/display/MXNET/Deep+Learn
> > ing+Based+GitHub+Label+Bot
> >
> > Please feel free to let me know if you have suggestions/requirements/
> > expectations.
> >
> > Thanks,
> > Cathy
> >
> >
> >
>

Re: GitHub Label Bot Design

[Yuelin Zhang]

Sorry for the messed up url format.
Please forward to this link: https://tinyurl.com/mxnetbot


Thanks,
Cathy


On Tue, Jun 12, 2018 at 10:20 AM, Yuelin Zhang 
wrote:

> Hi,
>
> Currently there are many issues on Incubator-MXNet
>  repo, labeling issues can
> drive attention of  contributors to specific areas. Right now, issues are
> all manually labelled, which is time consuming.  And every time maintainers
> need to @ a committer to add labels.
> I am working on this label bot to automate/simplify this labeling issue
> process and send weekly report to maintainers. Design proposal is on cwiki:
> https://cwiki.apache.org/confluence/display/MXNET/Deep+Learn
> ing+Based+GitHub+Label+Bot
>
> Please feel free to let me know if you have suggestions/requirements/
> expectations.
>
> Thanks,
> Cathy
>
>
>

Update on 1.2.1 release

[Anirudh]

Hi all,

Here are the PRs that are being tracked for 1.2.1 release:

Related to the save_params backwards incompatible change: #11127 (In
Progress), #11236 (In Progress), #11210 (In Progress)
MKLDNN Fixes: #11212 (In Progress)
Cross compilation for armv7 : #11054 (In Progress)
Scala Inference Memory leak fix: #11216 (In Progress)
Docs changes: #11211 (Merged)
Inplace RELU Activation, Slice operator perf improvement: #11142 (Merged)
Use cudnnv7 for depthwise conv #11233 (Merged)

Please let me know if I have missed something.

Anirudh

GitHub Label Bot Design

[Yuelin Zhang]

Hi,

Currently there are many issues on Incubator-MXNet
 repo, labeling issues can drive
attention of  contributors to specific areas. Right now, issues are all
manually labelled, which is time consuming.  And every time maintainers
need to @ a committer to add labels.
I am working on this label bot to automate/simplify this labeling issue
process and send weekly report to maintainers. Design proposal is on cwiki:
https://cwiki.apache.org/confluence/display/MXNET/Deep+
Learning+Based+GitHub+Label+Bot

Please feel free to let me know if you have
suggestions/requirements/expectations.

Thanks,
Cathy

"What does the Apache board do"

[Sebastian]

Hi,

I just came across a video where two of the directors of the ASF talk 
about what the board looks for in healthy apache projects. (Note that 
they look at top level projects only and things are a little different 
in the incubator). However, I still think this video contains many 
useful views, especially for the MXNet community:


https://www.youtube.com/watch?v=jm_whow_zxk

Best,
Sebastian

Re: About Becoming a Committer

[Yasser Zamani]

On 6/9/2018 12:45 AM, Sheng Zha wrote:
> There have been a couple of offline inquiries from contributors about
> becoming a committer. From those inquiries, it seems that there’s confusion
> in our community about how to become a committer, so I’d like to take this
> opportunity to clarify.
> 
> The guideline about becoming a committer can be found at
> https://cwiki.apache.org/confluence/display/MXNET/Becoming+a+Committer.

I think that page at above link is great but the problem is new visitors
cannot find it quickly then they ask privately from you. I myself was
looking for it at mxnet.incubator.apache.org, so clicked on
"Community->Contribute", the I read all page then I saw a link to wiki
on page i.e. "MXNet Confluence Wiki: Development" where I guessed I
might find something in wiki so clicked that. Then I saw "Becoming a
Committer" in left side wiki's menu.

I think we'll get fewer private inquiries on this if we add a direct
link about it at
https://mxnet.incubator.apache.org/community/contribute.html

Regards.