From dev-return-2327-archive-asf-public=cust-asf.ponee.io@mxnet.incubator.apache.org Wed Mar 7 19:49:28 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 25D17180656 for ; Wed, 7 Mar 2018 19:49:27 +0100 (CET) Received: (qmail 45730 invoked by uid 500); 7 Mar 2018 18:49:27 -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 45707 invoked by uid 99); 7 Mar 2018 18:49:26 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Mar 2018 18:49:26 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A4AE41A0394 for ; Wed, 7 Mar 2018 18:49:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.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] autolearn=disabled Authentication-Results: spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id p9ZDokJAtqAP for ; Wed, 7 Mar 2018 18:49:23 +0000 (UTC) Received: from mail-it0-f43.google.com (mail-it0-f43.google.com [209.85.214.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id D6B1A5F296 for ; Wed, 7 Mar 2018 18:49:22 +0000 (UTC) Received: by mail-it0-f43.google.com with SMTP id n128so17080805ith.1 for ; Wed, 07 Mar 2018 10:49:22 -0800 (PST) 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=jmCtjZd9DeEfwc5juOauLl0AeSGInMWuCLURfl+nHtA=; b=fv28WCgbTFEQH07DgVdzhs9YWCyanby5ZiOcovhdt4UZ2/FulX4eIkiQ7shpSEspmp ypcNSsSC4H49a9UIXI7aoablKwI35e8FX9yw200zaIFwUJex2NSURZBjgH1oIdmkrMZI BHdnmogTQB175Y9LXlAaMKjeM8xapUTWM/nQ+/JMq9vR20dz8YeihboKzvQu/Wtx0CM2 MfCTPdcBbtmt5LkfqlZuetVu9PezMXcDCAd6dmMnNQqORI8rcJ4ctL8/zhYW5jJa0qTt 3VfujRVyQmYlbEO6Zgs9Zq/0m37TnCMyOZxDi30RhXzVXPvwBRY2xmklGuiZXcavRR3M 9waw== 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=jmCtjZd9DeEfwc5juOauLl0AeSGInMWuCLURfl+nHtA=; b=SSXFkU7KMPOt4zpmsS2a4UC8+beBFfZ0jTNNM4C8grVL2mTXKo5yMN5WeUDsmSYIKq zUUoobnuqQnluukwZWtsPjuRz833ikznAgT0cBmU/eI3ccWzvq9lcbrYV7XQMEcwPkvl MwOcifymqa7pU7tubNCJwgQqKRck1SvUenKn8hzOeTQ8KwXctWvkyW/5KiHKtAiDvO3U g+XURXmebbOhV4NofongmcQVF3CZAVbActgs6gDoVqBgEn73A6orUFY8HB0j1XQGuWtS MPExQJuJRBlL/3jmQbytWcf5WNC4CJqg/iis70CQiJ3oAAwVGGz39f5YVHdaeo6PzOxx JrYA== X-Gm-Message-State: AElRT7GSCQi2/zzntIi2CKrsSonPim3HsEAVirsaDRP9g7JVvDn3w5lC G/D7ZkNGexdwug/82TQzT3HtrytcNXdaKoAVnkw= X-Google-Smtp-Source: AG47ELsOdQdHnAvkzUdqq/M4QlrPYbjN1uzo1XNA4L3Qth3538wrWzbwwK4+F5FUB+v+MDdWgLov79KiWbfvERwjjXc= X-Received: by 10.36.43.80 with SMTP id h77mr24335154ita.103.1520448561345; Wed, 07 Mar 2018 10:49:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.24.29 with HTTP; Wed, 7 Mar 2018 10:48:40 -0800 (PST) In-Reply-To: References: From: Naveen Swamy Date: Wed, 7 Mar 2018 10:48:40 -0800 Message-ID: Subject: Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests To: dev@mxnet.incubator.apache.org Content-Type: multipart/alternative; boundary="001a1147413865fb730566d7049a" --001a1147413865fb730566d7049a Content-Type: text/plain; charset="UTF-8" I am +1 for using JIRA. Managing bigger projects within MXNet on JIRA brings openness to the project. MXNet Users and the contributors also get a sense of where the project is heading. Bigger Tasks can be divided into sub-tasks which contributors can pick up small tasks based on their expertise on and contribute independently. On Wed, Mar 7, 2018 at 10:40 AM, Chris Olivier wrote: > The vote was discussed on private@ before the vote on dev@, and the vote > went on for a very long time. There was ZERO resistance. No one "snuck" > it in or "slipped it by". > > This, hopefully, phases out both SIM and tt, which are both are being used > in ways that aren't what they're even designed for, IMO. Trouble tickets > are being used as a backlog for my team, which is insane. > > I've actually sent out a couple of mails on dev about contact me if you > don't have access to JIRA. If you would like to participate in the > direction of the project, please keep up with the dev email list. > > I gave you contributor permissions on JIRA, btw. > . > > > > On Wed, Mar 7, 2018 at 10:17 AM, Aaron Markham > wrote: > > > I'm not quite sure if I have enough background on reasons for or against > > this to vote in the next round, but my two cents: I didn't see much > debate > > on why we need yet another tool for issues that we have to manually > > maintain...the vote kind of slid in there without many stakeholders > > realizing what they were being signed up for. I was thinking, sure, if > YOU > > want to make jira tickets, go right ahead. I have two internal ticketing > > systems to deal with already that assign tasks on MXNet, plus GitHub. > Jira > > would be four. Happy to make it work, but I'll need fifth tool to > aggregate > > communications and metrics between the other four tools! I'm only sort of > > joking. > > > > I saw Chris's response, and ok the public visibility part makes sense, > but > > does this phase out any other overhead? Does it integrate? Jira has > > integration options so maybe we can eliminate some overhead... Like > > something that hooks into the GitHub api and generates jira tickets on > the > > fly... I want to believe there's a plan that makes this all easier. > > > > What value I don't see is how we lower barriers to contribution and make > it > > more fluid for new users that could become contributors. What's the story > > and value proposition? > > > > Also, I don't see any docs on the website or on github on how to sign up > > for jira, or how to contribute according to this new requirement anywhere > > on the site. Myself and new contributors wouldn't know what the expected > > flow looks like because it's not really accessible. I now see the > > confluence wiki, but that's pretty much hidden from anyone browsing the > > site or github and looking to contribute. Why is this info on confluence > at > > all? Why not in the docs on github that are rendered to the website? Or > > conversely, why is some of the info on github and on the website, if it > is > > being maintained and current only on confluence? > > > > These are two separate issues really, but I think if you want buy-in, > this > > needs to be more transparent and obvious, and provide clear reasons and > > benefits to why you're asking for more overhead. > > > > Aaron > > > > On Mar 6, 2018 21:14, "Eric Xie" wrote: > > > > > -1 > > > > > > JIRA is ancient and arcane. This adds unnecessary overhead. > > > > > > On 2018/03/03 06:11:12, CodingCat wrote: > > > > This vote passes with 6 +1 votes (6 bindings) and no 0 or -1 votes. > > > > > > > > Binding +1: > > > > Chris Olivier > > > > Indhu Bharathi > > > > Suneel Marthi > > > > Yuan Tang > > > > Marco de Abreu > > > > Sebastian Schelter > > > > > > > > > > > > > > > > Vote thread: > > > > https://lists.apache.org/list.html?dev@mxnet.apache.org:lte= > > > 1M:tracking%20code%20changes%20with%20JIRA%20by%20associatin > > > g%20pull%20requests > > > > > > > > I will continue with pushing the content to wiki and take it into > > > practice > > > > > > > > > > --001a1147413865fb730566d7049a--