From dev-return-19521-archive-asf-public=cust-asf.ponee.io@accumulo.apache.org Thu Feb 15 04:30:01 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 6F5F2180621 for ; Thu, 15 Feb 2018 04:30:00 +0100 (CET) Received: (qmail 68546 invoked by uid 500); 15 Feb 2018 03:29:59 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 68535 invoked by uid 99); 15 Feb 2018 03:29:59 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Feb 2018 03:29:59 +0000 Received: from mail-ua0-f179.google.com (mail-ua0-f179.google.com [209.85.217.179]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 4508E4F5 for ; Thu, 15 Feb 2018 03:29:57 +0000 (UTC) Received: by mail-ua0-f179.google.com with SMTP id 47so15037905uau.9 for ; Wed, 14 Feb 2018 19:29:57 -0800 (PST) X-Gm-Message-State: APf1xPCdqLecMITN5BwhweRRn3EvsqEZZls4TI1p0dgV/aFkENizGOmQ 0Z0Te7WVoSIV/HH9QMkFzGo7mnIWvE223eKEK5s= X-Google-Smtp-Source: AH8x224AEi/EJMDniyrII+7vFqkG0EYKcm0b7rJfQ25H2mwMxj+tBktXgvYdBOZozZaTt/208A1Q8YEWW74QXfKhPuQ= X-Received: by 10.159.49.135 with SMTP id v7mr1141911uad.17.1518665397106; Wed, 14 Feb 2018 19:29:57 -0800 (PST) MIME-Version: 1.0 References: <9144fd5f-7dcd-e8a7-f8e8-e85d55cb9a80@apache.org> In-Reply-To: From: Christopher Date: Thu, 15 Feb 2018 03:29:46 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Additional options for issue tracking To: dev@accumulo.apache.org Content-Type: multipart/alternative; boundary="001a114561d486fdec056537d7db" --001a114561d486fdec056537d7db Content-Type: text/plain; charset="UTF-8" Can you elaborate on what kind of human controls you mean? What if a user finds the GH issues and creates an issue there? What action should the developers take? On Wed, Feb 14, 2018 at 10:27 PM Josh Elser wrote: > I didn't ask for automated controls here -- human controls are fine. > > I have already said I am -1 on two concurrent issue trackers. If > developers want to evaluate them, that's fine. > > On 2/14/18 10:12 PM, Christopher wrote: > > I don't think we have the ability to lock out non-committers from > creating > > new GH issues if we enable them, nor do I think it would make sense to do > > so, since that's a valuable use case to consider during any trial period > > before shutting off JIRA. > > > > As for switching immediately to GH issues for non-primary repo (-website, > > -examples, -docker, etc...) I think that makes sense since those are > > already confusing when filed in the JIRA mixed in with the main repo's > > issues. > > > > On Wed, Feb 14, 2018 at 9:25 PM Josh Elser wrote: > > > >> I am OK with committers ONLY using GH issues on all repos (with clear > >> guidance as to what the heck the project is doing) or doing a > >> full-switch on the other repos. > >> > >> On 2/14/18 7:00 PM, Mike Miller wrote: > >>> We could do a trial period of GitHub issues for the accumulo sub-repos > >>> (accumulo-website, accumulo-examples...) then after a month or two > decide > >>> to switch or not. That way we won't have duplicate issues or the > >> confusion > >>> of having 2 trackers for one repository. > >>> > >>> On Wed, Feb 14, 2018 at 6:12 PM, Mike Walch wrote: > >>> > >>>> +1 I think it makes sense to try out GitHub before shutting off JIRA. > >> This > >>>> period could be limited to a month or two. > >>>> > >>>> On Wed, Feb 14, 2018 at 5:59 PM, Christopher > >> wrote: > >>>> > >>>>> What if we had an interim transition period, tentatively using GitHub > >> to > >>>>> determine it's suitability for our workflows, and shut off JIRA > later? > >>>>> > >>>>> On Wed, Feb 14, 2018 at 5:51 PM Josh Elser > wrote: > >>>>> > >>>>>> I disagree with Mike in that I don't find JIRA to be so painful that > >> it > >>>>>> necessitates us changing, but I wouldn't block a move to GH issues > if > >>>> we > >>>>>> turn off our JIRA use. > >>>>>> > >>>>>> On 2/14/18 4:29 PM, Mike Drob wrote: > >>>>>>> @josh - How do you feel about move from JIRA to GH Issues > completely? > >>>>>>> > >>>>>>> On Wed, Feb 14, 2018 at 3:26 PM, Josh Elser > >>>> wrote: > >>>>>>> > >>>>>>>> I believe I already stated -1 the last time this was brought up. > >>>>>>>> > >>>>>>>> Using two issue trackers is silly. > >>>>>>>> > >>>>>>>> > >>>>>>>> On 2/14/18 3:30 PM, Mike Walch wrote: > >>>>>>>> > >>>>>>>>> I want to enable GitHub issues for Accumulo's repos. This is not > to > >>>>>>>>> replace > >>>>>>>>> JIRA but to give contributors more options for issue tracking. > >>>> Unless > >>>>>>>>> there > >>>>>>>>> are objections, I will create an infra ticket this week. > >>>>>>>>> > >>>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > > --001a114561d486fdec056537d7db--