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 C992D200CBD for ; Thu, 6 Jul 2017 16:55:32 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C7EB6166990; Thu, 6 Jul 2017 14:55:32 +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 19EDD16698E for ; Thu, 6 Jul 2017 16:55:31 +0200 (CEST) Received: (qmail 30096 invoked by uid 500); 6 Jul 2017 14:55:31 -0000 Mailing-List: contact dev-help@fluo.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fluo.incubator.apache.org Delivered-To: mailing list dev@fluo.incubator.apache.org Received: (qmail 30085 invoked by uid 99); 6 Jul 2017 14:55:31 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jul 2017 14:55:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id C05FCC023D for ; Thu, 6 Jul 2017 14:55:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.022 X-Spam-Level: X-Spam-Status: No, score=-5.022 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id bSD98cbUnmfE for ; Thu, 6 Jul 2017 14:55:26 +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 1F2295F6C6 for ; Thu, 6 Jul 2017 14:55:24 +0000 (UTC) Received: (qmail 27044 invoked by uid 99); 6 Jul 2017 14:55:24 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jul 2017 14:55:24 +0000 Received: from hw10447.local (unknown [167.102.188.146]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 903F21A0029; Thu, 6 Jul 2017 14:55:23 +0000 (UTC) Subject: Re: [DISCUSS] Fluo graduation as TLP To: general@incubator.apache.org References: <26438284-f463-e133-1e7d-3f2207106f5d@apache.org> <93E7498F-4755-4568-A860-013C802377E8@comcast.net> From: Josh Elser Message-ID: <0d891adc-377c-c2d8-bf4b-324238d0c340@apache.org> Date: Thu, 6 Jul 2017 10:55:21 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:54.0) Gecko/20100101 Thunderbird/54.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: Thu, 06 Jul 2017 14:55:33 -0000 Thanks, John. Consider this mentor +1 then. On 7/5/17 7:03 PM, John D. Ament wrote: > For what it's worth, I have no concerns with Fluo's graduation based on the > conversation here. > > John > > On Wed, Jul 5, 2017 at 7:02 PM Josh Elser wrote: > >> >> >> On 7/5/17 1:51 PM, Dave Fisher wrote: >>> Hi Josh, >>> >>> I have some questions: >>> >>>> On Jul 5, 2017, at 10:18 AM, Josh Elser wrote: >>>> >>>> As a mentor, I consciously avoided an explicit "+1" until we got some >> IPMC discussion. Let me expand: >>>> >>>> The current members of Fluo are great, get the Apache Way, and are >> self-sufficient. I have no concerns over them operating as a TLP -- I think >> they are ready. However, they have only added a single committer and I see >> none in the pipeline -- Fluo is defined by the current committers. >>> >>> (1) Seems to be a niche project as you state below which is just within >> the range of 5 contributors. Am I wrong? >> >> Yup, that sounds about right. I'm notice three of them being the most >> active, but I tend to not watch that closely. >> >>>> My hesitation is balancing the Incubators goal of "pushing podlings to >> graduate" and ensuring adequate diversity in the podling. This is >> especially difficult for Fluo as they're "niche on niche" (it's a difficult >> dist-sys problem/software, and not many people use the tech they're >> building on top of given my view of the world). >>>> >>>> I realize that this discussion could easily spiral out of control, >> turning into some meta-discussion about Incubator goals. I want to avoid >> that. >>>> >>>> I'm looking for some feelings from other IPMC folks about how to >> approach the Fluo podling given their specific circumstances. If other >> people are also hesitant, I would also be interested in suggestions about >> what we would concretely change (because I don't know what to suggest that >> "fix" the diversity issue for them that isn't changing the core of their >> project). If people aren't worried, I'm happy to give an explicit +1. >>> >>> (2) Has any consideration been given to becoming a project within >> Accumulo? Or are the goals of Fluo distinct from and not wholly dependent >> on Accumulo? >>> >>> (3) Corollary - it seems a large number of Fluo Initial Committers were >> also Accumulo PMC. (I not intentionally rehashing any prior conversation.) >>> >> >> Will leave Christopher's response to (thoroughly) answer this ;) >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >> For additional commands, e-mail: general-help@incubator.apache.org >> >> >