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 A46EA200CA5 for ; Sat, 10 Jun 2017 16:05:31 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A30D9160BDA; Sat, 10 Jun 2017 14:05:31 +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 E97D4160BD7 for ; Sat, 10 Jun 2017 16:05:30 +0200 (CEST) Received: (qmail 49198 invoked by uid 500); 10 Jun 2017 14:05:30 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 49187 invoked by uid 99); 10 Jun 2017 14:05:30 -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, 10 Jun 2017 14:05:29 +0000 Received: from [192.168.2.104] (p57A8ADF6.dip0.t-ipconnect.de [87.168.173.246]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 8C4B81A0048 for ; Sat, 10 Jun 2017 14:05:27 +0000 (UTC) Subject: Re: [DISCUSS] GitBox To: dev@flink.apache.org References: From: Chesnay Schepler Message-ID: <7f3aa4bb-b03d-c327-8f3e-d9029c6360d8@apache.org> Date: Sat, 10 Jun 2017 16:05:27 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US archived-at: Sat, 10 Jun 2017 14:05:31 -0000 What are the downsides of this? Actually, is there any ASF resource that outlines what this would enable? In one of the threads i saw said that this would also allow committers to close PR's, assign labels and such. This sounds very interesting to me for the main repo actually. On 09.06.2017 17:41, Greg Hogan wrote: > Robert has an open PR from March. I’ve found, for example, PRs adding links to talks or slides left open for months. > > I’d suggest Fluo is to Accumulo as flink-web is to the flink repo, and that migration looks to be satisfactory. > > >> On Jun 9, 2017, at 11:15 AM, Ted Yu wrote: >> >> bq. better track the oft-neglected contributions >> >> Do you have estimate on how many contributions were not paid attention in >> the current infrastructure. >> >> Looking at #2, it seems Accumulo community hasn't reached consensus yet. >> >> Cheers >> >> On Fri, Jun 9, 2017 at 7:54 AM, Greg Hogan wrote: >> >>> All, >>> >>> ASF now has available (and maybe mandatory for new projects or repos) >>> GitBox [0] which enables bi-directional sync to GitHub and links >>> committers' accounts, allowing for greater use of GitHub functionality by >>> contributors and for committers to perform many tasks otherwise requiring >>> INFRA tickets. >>> >>> I'd like to propose moving flink-web [1] to GitBox, using GitHub issues, >>> and enabling notifications to the mailing lists. Apache Accumulo has >>> recently discussed [2] this topic with a list of benefits after migrating >>> Fluo. By migrating flink-web we can better track the oft-neglected >>> contributions and also test the waters for future migrations (perhaps for >>> the future sub-projects). >>> >>> [0] https://gitbox.apache.org/ >>> [1] https://github.com/apache/flink-web/pulls >>> [2] >>> http://apache-accumulo.1065345.n5.nabble.com/DISCUSS- >>> GitBox-tp21160p21497.html >>> >>> Greg