From dev-return-3583-archive-asf-public=cust-asf.ponee.io@mxnet.incubator.apache.org Fri Jul 13 07:20:21 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 24183180626 for ; Fri, 13 Jul 2018 07:20:20 +0200 (CEST) Received: (qmail 24440 invoked by uid 500); 13 Jul 2018 05:20:20 -0000 Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mxnet.incubator.apache.org Delivered-To: mailing list dev@mxnet.incubator.apache.org Received: (qmail 24308 invoked by uid 99); 13 Jul 2018 05:20:19 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jul 2018 05:20:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 1C9A9C00DB for ; Fri, 13 Jul 2018 05:20:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.869 X-Spam-Level: ** X-Spam-Status: No, score=2.869 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_REPLY=1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 0KSL_Q1AeHBU for ; Fri, 13 Jul 2018 05:20:17 +0000 (UTC) Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 2EFE25F404 for ; Fri, 13 Jul 2018 05:20:17 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id q11-v6so34494368oic.12 for ; Thu, 12 Jul 2018 22:20:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=/a/h5xiDvzs18KGvHnbbUyiRR0AMX+MmQSg4/QA4jzs=; b=MNIo7BRpwYEXFDlQwXwHWwrTjoBhKa5JGdUEiR1bCBxA1YrG3tVgWKO1udi1bHtN6v 1mNZtlHbD8KrDdvs+jskRR0PwpTIS9qtgmrR5itxIWH4doRIO22fHiSFlKkttproDbLL pcFn4a1T8xO7hIQ+xEYZDZ8V/XvL85HK0VC+wtm77Nt/B6H6WRkpk53cw4ie9nX3SG4C sbJtmYC8Gu8mImKRYfz+7WJUlIqjFAjDnQqF7qixEOAHidqlY2GYnLPokR75LjgthI4I I3Mt8N0FM7eInnWM1iqGA2psBxtnUPB5eZZkSo+FzJZ2QnD1xUCW3YLzrowSEzvtWqdu wP/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=/a/h5xiDvzs18KGvHnbbUyiRR0AMX+MmQSg4/QA4jzs=; b=tExk5QPNbBeBqGKZ8vuNY37WfoutKW72qf0aKt2jjPyFuParEUEEpO2VshgHQkneJq 1AoO9k7MgqAltBbJtseQ0dC5s+UHE0V8nsZQg9p/5UolDF4pXL7stpkyxuUUv4AozdD0 QUioUe5vYx/S+rawCO/LbUNT9ReInXzmFKDofw2AN7tSe1DWWzWa82LcO2RYeUUpuu/J WBUmcOFj63DkylP78vjQuNI9Fo7/xq+R2LCZEnWk24YKWFaTZvgJaRFZxaq1bxIh8PjX +WuZDU3KCfG/AXIhvxkyjP2RqDoGfypBZkKTT/m79fT9QS/TN+EaY/tjDS4jxjvURvmz xITA== X-Gm-Message-State: AOUpUlEkofGkYMSrCgsbZRgKOCueCaTY6IJpMXztEKaG1txmVHNUE2BE ulOUxiWhTwAfHGuQSPC9YIcMot5zZxxswwgVFB8= X-Google-Smtp-Source: AAOMgpcumptJyzQMuoPaSfHrv3R8uqzyVdvpmVOXiMNhtXsrvhTsVxusG21W3tbtjvKjCS6clowCM0Isy6a4Cebllrw= X-Received: by 2002:aca:603:: with SMTP id 3-v6mr5705118oig.103.1531459216010; Thu, 12 Jul 2018 22:20:16 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:2aaa:0:0:0:0:0 with HTTP; Thu, 12 Jul 2018 22:20:15 -0700 (PDT) In-Reply-To: References: From: Yuelin Zhang Date: Thu, 12 Jul 2018 22:20:15 -0700 Message-ID: Subject: Re: Access Permission of MXNet label bot To: dev@mxnet.incubator.apache.org Content-Type: multipart/alternative; boundary="0000000000008ef44c0570daa2c2" --0000000000008ef44c0570daa2c2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That's a very good solution! I will provide documentations about how to run/test/maintain it. Will reach out to see how can we collaborate on it. Thanks, Cathy On Thu, Jul 12, 2018 at 4:09 PM, Naveen Swamy wrote: > +1 to running it inside a controlled environment. > > On Thu, Jul 12, 2018 at 11:32 AM, Qing Lan wrote: > > > I think putting in the Infra can be a really good solution. > > We do not expose the credential to the outside and we can make sure it > can > > be run in a timely manner. > > > > Thanks, > > Qing > > > > =EF=BB=BFOn 7/12/18, 11:11 AM, "Marco de Abreu" INVALID> > > wrote: > > > > Hello Cathy, > > > > unfortunately, we're not allowed to use bot accounts at Apache. > > > > An option we have is that we run your bot in our infrastructure wit= h > > the > > credentials of a committer with the permission you have mentioned. > The > > only > > restriction would be that you would not be able to access that serv= er > > because the credentials are confidential user data of a committer. > > Would > > this work for you? > > > > Best regards, > > Marco > > > > On Thu, Jul 12, 2018 at 8:57 PM Yuelin Zhang < > > zhangyuelinchina@gmail.com> > > wrote: > > > > > Hi, > > > > > > I am working to improve the GitHub issue triage process by creati= ng > > a label > > > bot(more info here > > > < > > > https://cwiki.apache.org/confluence/display/MXNET/Deep+ > > Learning+Based+GitHub+Label+Bot > > > > > > > on > > > the cwiki), I have initial version of label bot ready. I would li= ke > > to get > > > some opinions about access permission of MXNet label bot. > > > > > > Right now, all issues in MXNet repo are manually labeled. The > > process looks > > > like below: > > > First, contributors/committers go through the issues to triage th= em > > and > > > suggest labels and add comment on the issue requesting @committer > to > > add > > > labels. > > > > > > This process will cause notification spam to both committers and > > users. The > > > long gap between user creating an issue and we labelling them wil= l > > cause > > > the process time consuming and not very smooth. > > > > > > We want to simplify/automate this issue labeling process. Right n= ow > > an > > > initial version of the label bot which can: > > > > > > 1. Send issue report daily. This report will show how many > issue > > > open/closed, list uncommented/unlabeled issues and show an pie > > chart of > > > labels added in a week. Sample report here > > > < > > > https://cwiki.apache.org/confluence/display/MXNET/Deep+ > > Learning+Based+GitHub+Label+Bot#DeepLearningBasedGitHubLabelBo > > t-SampleIssueReport > > > > > > > . > > > 2. Generate a spread sheet of unlabeled issues with recommend= ed > > labels. > > > A contributor will open the sheet and fill in labels with > > reference of > > > bot's recommendations. In this case, contributor can deal with > all > > > unlabeled issues at a time. Sample sheet here > > > < > > > https://cwiki.apache.org/confluence/display/MXNET/Deep+ > > Learning+Based+GitHub+Label+Bot#DeepLearningBasedGitHubLabelBo > > t-SampleSpreadSheet > > > > > > > . > > > 3. Read labels filled in that sheet and apply labels to GitHu= b > > issues. > > > (tested on my personal Github repo) > > > > > > > > > This bot can be triggered daily so that all issues will be labele= d > > in one > > > day without notification spam. > > > > > > *However, this bot doesn't have access to add labels. We have tw= o > > > options:* > > > > > > - Use a committer's Oauth token with limited scope. So far > according > > to my > > > research, the most limited scope is "public_repo", this contains > > access to > > > code. Except this one, Github doesn't have smaller scope availabl= e > > to add > > > labels. Available scopes here > > > < > > > https://developer.github.com/apps/building-oauth-apps/ > > understanding-scopes-for-oauth-apps/ > > > > > > > . > > > > > > - Create a bot account having minimum permissions. For this, we > will > > need > > > an account to be created from Apache Infrastructure with proper > > access and > > > they can control the access for the account through secret manage= r > > > > userguide/intro.html> . > > > Having a bot account is beneficial for future work, not only for > > labelling > > > but also other automatic processes. > > > > > > Please let me know if you have any other ideas to do this. > > > > > > Thanks, > > > Cathy > > > > > > > > > > --0000000000008ef44c0570daa2c2--