Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 11658200B65 for ; Wed, 3 Aug 2016 02:53:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0FDA2160AA8; Wed, 3 Aug 2016 00:53:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 32696160A76 for ; Wed, 3 Aug 2016 02:53:13 +0200 (CEST) Received: (qmail 58633 invoked by uid 500); 3 Aug 2016 00:53:12 -0000 Mailing-List: contact dev-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list dev@airflow.incubator.apache.org Received: (qmail 58621 invoked by uid 99); 3 Aug 2016 00:53:12 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Aug 2016 00:53:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EE0DECF4FD for ; Wed, 3 Aug 2016 00:53:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.263 X-Spam-Level: X-Spam-Status: No, score=-3.263 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.243] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id foDHiswsW2Kw for ; Wed, 3 Aug 2016 00:53:09 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id CEFC45FAEE for ; Wed, 3 Aug 2016 00:53:08 +0000 (UTC) Received: (qmail 58616 invoked by uid 99); 3 Aug 2016 00:53:08 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Aug 2016 00:53:08 +0000 Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id B8B511A00E9 for ; Wed, 3 Aug 2016 00:53:07 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id l65so260652204oib.1 for ; Tue, 02 Aug 2016 17:53:07 -0700 (PDT) X-Gm-Message-State: AEkoouu722SOOvtBa3SgfN3L0MRG5pit9fBR15IcMagtom24PvFA3wNW8JDOu8QaZBr0o6Q4e1M/BFBBQbGW3A== X-Received: by 10.202.234.86 with SMTP id i83mr39291957oih.177.1470185586972; Tue, 02 Aug 2016 17:53:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.55.132 with HTTP; Tue, 2 Aug 2016 17:53:06 -0700 (PDT) In-Reply-To: References: <5B3FB659-D828-425D-9A69-8B3550E68847@gmail.com> From: siddharth anand Date: Tue, 2 Aug 2016 17:53:06 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Projects using GitHub issues To: dev@airflow.incubator.apache.org Content-Type: multipart/alternative; boundary=001a113d522eaabc9f05392041e6 archived-at: Wed, 03 Aug 2016 00:53:14 -0000 --001a113d522eaabc9f05392041e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Mentors, Any updates here? I looked at the thread that Chris R had pasted to kick off this discussion. The thread meandered. I saw a comment from Jim J stating : Recall that issue trackers have not been, traditionally, held under the requirement of being under ASF infra nor infra control. If people wish to use external, 3rd party issue/bug trackers, they are taking on the risks themselves, as far as SLAs, historical access, etc... Does this mean that it's up to us to pick GH Issues? -s On Wed, Jun 29, 2016 at 9:29 AM, Maxime Beauchemin < maximebeauchemin@gmail.com> wrote: > Oh right! Problem solved. I assumed wrong since I probably tried to edit > someone else's title before and assumed I had lost all title editing > rights... > > Max > > On Wed, Jun 29, 2016 at 9:25 AM, Bolke de Bruin wrote= : > > > You can edit your own pr titles just fine I think? I do it all the time > at > > least. > > > > Sent from my iPhone > > > > > On 29 jun. 2016, at 18:09, Maxime Beauchemin < > maximebeauchemin@gmail.com> > > wrote: > > > > > > Somewhat related: Jira is down at the moment > > > > > > I'm ready to send a PR just now and knowing that I can't create the > JIRA > > issue, I can't get an ID for it. And I know I won't be able to edit the > > title of my GH PR later since I don't have admin rights in GH. Checkmat= e. > > > > > > ----------------- > > > > > > > > > =E2=80=8B > > > > > >> On Tue, Jun 28, 2016 at 9:48 AM, Maxime Beauchemin < > > maximebeauchemin@gmail.com> wrote: > > >> Awesome! Somehow consistent and well integrated tools make quite a > > difference. > > >> > > >> For first time or casual contributors it's annoying to create a JIRA > > account to create a single issue to get an ID to paste into the GH PR, > then > > it can be unclear where to have the discussion. I hate to have to > > walkthrough teammates (new contributors) through this process. > > >> > > >> I understand why Gnu doesn't like GH, I get it, it's the philosophic= al > > principle at the root of Gnu that is incompatible with GH. But Apache > > choosing Atlassian is probably because that was the best option 5 or 10 > > years ago. Consistency across Apache projects is great, but consistency > > with the open source movement is more important to me. > > >> > > >> Max > > >> > > >> > > >>> On Tue, Jun 28, 2016 at 8:51 AM, Jeremiah Lowin > > wrote: > > >>> Thanks for the heads up Chris! > > >>> > > >>> On Tue, Jun 28, 2016 at 10:21 AM Chris Riccomini < > > criccomini@apache.org> > > >>> wrote: > > >>> > > >>> > FYI- it sounds like there's some discussion about allowing GH > issues > > >>> > instead of JIRA. > > >>> > > > >>> > ---------- Forwarded message ---------- > > >>> > From: John D. Ament > > >>> > Date: Tue, Jun 28, 2016 at 7:17 AM > > >>> > Subject: Projects using GitHub issues > > >>> > To: "general@incubator.apache.org" > > >>> > > > >>> > > > >>> > All, > > >>> > > > >>> > I started a discussion on legal discuss, as I was told VP Legal > > approved > > >>> > using GitHub issues. I have no specific concerns, other than > > ensuring that > > >>> > permissions are propagated. > > >>> > > > >>> > > > >>> > > > > https://lists.apache.org/thread.html/d2cb0eed30d72976a2f54893f132c1fe300a= 86d2fdbce1422763c9f0@%3Clegal-discuss.apache.org%3E > > >>> > > > >>> > Its clear to me that legal-discuss isn't where this should start, > so > > I'm > > >>> > not sure why VP Legal approved. Anyways, I wanted to get opinion= s > > from the > > >>> > incubator on who should be discussing this issue. > > >>> > > > >>> > John > > >>> > > > >> > > > > > > --001a113d522eaabc9f05392041e6--