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 64882200CF2 for ; Sat, 19 Aug 2017 04:30:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 62F2116DB53; Sat, 19 Aug 2017 02:30:35 +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 CF30B16DB52 for ; Sat, 19 Aug 2017 04:30:34 +0200 (CEST) Received: (qmail 79404 invoked by uid 500); 19 Aug 2017 02:30:34 -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 79393 invoked by uid 99); 19 Aug 2017 02:30:33 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Aug 2017 02:30:33 +0000 Received: from hw10447.local (outbound.hortonworks.com [192.175.27.2]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 1ED661A04D8 for ; Sat, 19 Aug 2017 02:30:32 +0000 (UTC) Subject: Re: [DISCUSS] GitBox To: dev@accumulo.apache.org References: From: Josh Elser Message-ID: Date: Fri, 18 Aug 2017 22:30:30 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:56.0) Gecko/20100101 Thunderbird/56.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit archived-at: Sat, 19 Aug 2017 02:30:35 -0000 My biggest concern was the confusion around the enabling of GH issues that would accompany this. As long as we're not trying to do project management in two places concurrently, I don't care either way. On 8/18/17 4:51 PM, Mike Drob wrote: > What has changed about the state of Accumulo or GitBox since the last time > we had this discussion? Not saying no here, curious as to why you think we > should revisit though. > > On Fri, Aug 18, 2017 at 3:36 PM, Mike Walch wrote: > >> I think we should revisit the discussion of using Apache GitBox for >> Accumulo. If you are unfamiliar with it, GitBox enables better GitHub >> integration for Apache projects. With GitBox, committers can label GitHub >> pull requests, squash and merge them using the GitHub UI, and close them if >> they become stale. I think a move to GitBox will help us do a better job of >> reviewing and merging pull requests so that contributions are looked at in >> a timely manner. The only downside to this move is that the git url for >> Accumulo will change. >> >> Does anyone have objections to this? >> >