From dev-return-3734-archive-asf-public=cust-asf.ponee.io@mxnet.incubator.apache.org Tue Jul 24 07:13:34 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 9F408180626 for ; Tue, 24 Jul 2018 07:13:33 +0200 (CEST) Received: (qmail 99027 invoked by uid 500); 24 Jul 2018 05:13:32 -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 98998 invoked by uid 99); 24 Jul 2018 05:13:31 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jul 2018 05:13:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 70D821806A2 for ; Tue, 24 Jul 2018 05:13:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 8eI8CmS458VP for ; Tue, 24 Jul 2018 05:13:29 +0000 (UTC) Received: from mail-yw0-f194.google.com (mail-yw0-f194.google.com [209.85.161.194]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id A50BE5F27E for ; Tue, 24 Jul 2018 05:13:28 +0000 (UTC) Received: by mail-yw0-f194.google.com with SMTP id z143-v6so1096512ywa.7 for ; Mon, 23 Jul 2018 22:13:28 -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=pBa+v89sGPcIm02CAQDxT5vrQ7xIXp0Iiep5izFXjlo=; b=Wdnxv4Oe81VzajeiC20gpknXyTFy/v1dCgU8APhWkwnVB58YyXtniVmhkQuAcTYXJB K7z5Kf23pTrVpEB/EZRvWEVaVta1iCFr/0k9myNiFJD7ZseXuTC/tWede3k/JbNfEZ1A HyHFNKT7DrKoBXfhjRJ/gyZxZmIjnCr/k7IJUg0wN4DUyRIeQmaAMAbbHbp7C+/79z19 GrhNJtkEAtkGV5uAZJI50bydBsniZkMGFh0okbvwx2EJ5uFYC7UpzMdEL/c7PpnKUk4F XOzVqyhhiimzu+ak7Wammhr6j29IqTjvWC5mueYs0yoNqEtVxxqVOcPsWc4w1lWYVE+3 YZrg== 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=pBa+v89sGPcIm02CAQDxT5vrQ7xIXp0Iiep5izFXjlo=; b=Vtm1Rqx6hQDPIt4gZ+e6LDokBEKMwubaS4tzdaCFcIzgnMFv24/+N1vgQ0YtDFxsQH 4T87VykAYDHTBImm5gX7sfqaYd2HFpigB987h7PkiNcg+UaPhb+lSFANopnbQ6DTlMdY 4RvybOa3GzTG2aWUPRQI6LorD7sPrMW+MerLdyfKsMYCp/4s0A07vDvmN9od3gmKeL0o t+pSnMs+eVTycUUnOvK43nt9NxAHGYbmFuEp9r0oSKx0CrKPx2eYTPVN2AQg8c31s5VV 4y9iDxSZD75q2msctq9yo+QleNI2KOHUsjt/NPWiamFaeOZK4pdkBUELmxv75Wj/AEu1 Sklw== X-Gm-Message-State: AOUpUlH7Jo1PXXnsZ0mBGIQEzQ4dQt9lkyd+Ec419JoIDVGHiOzW0jR4 h4VtpW7zDqz4KL5cNNplPGtEbTn5FeUlFN4F8UnAf9a8 X-Google-Smtp-Source: AAOMgpc9djbNjHvMQE3d98z00IQg0yznv83EP/3Afn4QiRU/cpZUNudRoQPbo4JBywiXnmrGNGCvwItKNI56RigURAc= X-Received: by 2002:a81:59c6:: with SMTP id n189-v6mr8172765ywb.30.1532409207243; Mon, 23 Jul 2018 22:13:27 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a81:a397:0:0:0:0:0 with HTTP; Mon, 23 Jul 2018 22:12:46 -0700 (PDT) In-Reply-To: References: <6a660f8c-1e2d-e01d-9087-0f310ade3413@apache.org> From: Naveen Swamy Date: Mon, 23 Jul 2018 22:12:46 -0700 Message-ID: Subject: Re: Request for feedback: proposal for MXNet SDK Office hours To: dev@mxnet.incubator.apache.org Content-Type: multipart/alternative; boundary="00000000000072c9320571b7d2b2" --00000000000072c9320571b7d2b2 Content-Type: text/plain; charset="UTF-8" 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. Typical flow for process is like this: - at least 24 hours before office hours session user signs up for one of 2 slots (each slot is 30 minutes) by filing jira issue. In that issue user will provide questions/concerns and relevant details pertaining to subject. - before or on a day *preceding* office hours session the developer who leads office-hours for that week reviews existing queue of filed issues and investigates 1 or 2 filed for upcoming session. The goal is to prepare for session as much as possible in advance. - Every week one of the Apache MXNet community members (committer/developer) could drive this effort in each area that is offered is support with. - if necessary they could to engage SME that has a lot of expertise in area relevant to question/issue filed. - at a scheduled time the developer leading office hours dials into meeting bridge and verifies that corresponding user has joined the line. - if by the end of time slot issue/question has not been fully addressed, developer would propose to take further conversation to the public forum(dev@ list or JIRA). This way office hours slots won't spill over and both slots could be accommodated for. - if any of the questions have not been fully addressed during session, developer will follow up and address outstanding scope of issue/question. Corresponding jira issue filed for session should be used as the outlet for following up. - one possible follow up could end up being new feature request or bug fix. If that is the case - developers would convert corresponding office hours issue into normal GitHub issue. - We request SMEs to help in following up by the issues. - At the end of the office hours conversation, developer who helped the user would summarize their interaction on the JIRA filed. On Mon, Jul 23, 2018 at 10:04 PM, Sheng Zha wrote: > 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 mentor to create issue > after discussion, instead of "just create". Thanks. > > -sz > > On Mon, Jul 23, 2018 at 7:36 PM, Naveen Swamy wrote: > > > 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 the wiki. This is a valid feedback and > I > > have fixed the PROPOSAL. > > I propose the office hours under discussion should be explicitly called > > "Apache MXNet Office hours". > > > > Also, Apache INFRA asked to create INFRA tickets only through mentors > > > > Can one of the mentors kindly help take this ticket forward. > > > > Thanks, Naveen > > > > > > > > > > On Thu, Jul 19, 2018 at 10:01 AM, Pedro Larroy < > > pedro.larroy.lists@gmail.com > > > wrote: > > > > > 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 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 offered, we might be able to find > contributors > > > > willing to do this in different parts of the world regardless of > their > > > day > > > > job or not. > > > > > > > > On Thu, Jul 19, 2018 at 9:21 AM, Sheng Zha > wrote: > > > > > > > > > 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 Drost-Fromm < > > isabel@apache.org > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > --00000000000072c9320571b7d2b2--