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 <[email protected]> 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 <[email protected] > > > wrote: > > > Hi, > > > > Currently there are many issues on Incubator-MXNet > > <https://github.com/apache/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 > > > > > > >
