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 A44B32009F8 for ; Fri, 3 Jun 2016 12:07:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A2D83160A2A; Fri, 3 Jun 2016 10:07:07 +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 C336D160A25 for ; Fri, 3 Jun 2016 12:07:06 +0200 (CEST) Received: (qmail 39541 invoked by uid 500); 3 Jun 2016 10:07:05 -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 39530 invoked by uid 99); 3 Jun 2016 10:07:05 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jun 2016 10:07:05 +0000 Received: from [192.168.1.11] (unknown [147.46.125.39]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 4D45C1A0146 for ; Fri, 3 Jun 2016 10:07:03 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [PROPOSAL] Structure the Flink Open Source Development From: Chiwan Park In-Reply-To: Date: Fri, 3 Jun 2016 19:07:00 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: <2884AF3E-4101-4DE9-9B5B-E9E4C42FB7CA@apache.org> References: <574DD08B.1050309@apache.org> <1464752793491-11932.post@n3.nabble.com> <574EA024.4040204@apache.org> To: dev@flink.apache.org X-Mailer: Apple Mail (2.3124) archived-at: Fri, 03 Jun 2016 10:07:07 -0000 Hi all, +1 for shepherd I would like to add me to shepherd for FlinkML. Regards, Chiwan Park > On Jun 3, 2016, at 3:29 AM, Henry Saputra = wrote: >=20 > +1 for shepherd >=20 > I would prefer using that term rather than maintainer. It is being = used in > Incubator PMC to help them keeping healthy development in podlings. >=20 > The term "maintainer" kind of being scrutinized in ASF communities, in > recent episodes happening in Spark community. >=20 > - Henry >=20 > On Wed, Jun 1, 2016 at 12:00 PM, Stephan Ewen = wrote: >=20 >> I like the name "shepherd". It implies a non-authorative role, and = implies >> guidance, which is very fitting. >>=20 >> I also thing there is no problem with having a "component shepherd" = and a >> "pull request shepherd". >>=20 >> Stephan >>=20 >>=20 >> On Wed, Jun 1, 2016 at 7:11 PM, Fabian Hueske = wrote: >>=20 >>> I think calling the role maintainer is not a good idea. >>> The Spark community had a maintainer process which they just voted = to >>> remove. =46rom my understanding, a maintainer in Spark had a more = active >> role >>> than the role we are currently discussing. >>>=20 >>> I would prefer to not call the role "maintainer" to make clear that = the >>> responsibilities are different (less active) and mainly observing. >>>=20 >>> 2016-06-01 13:14 GMT+02:00 Ufuk Celebi : >>>=20 >>>> Thanks! I like the idea of renaming it. I'm fine with shepherd and = I >>>> also like Vasia's suggestion "champion". >>>>=20 >>>> I would like to add "Distributed checkpoints" as a separate = component >>>> to track development for check- and savepoints. >>>>=20 >>>>=20 >>>>=20 >>>> On Wed, Jun 1, 2016 at 10:59 AM, Aljoscha Krettek = >>=20 >>>> wrote: >>>>> Btw, in Jira, if we clean up our components we can also set a >> component >>>>> Lead that would get notified of issues for that component. >>>>>=20 >>>>> On Wed, 1 Jun 2016 at 10:43 Chesnay Schepler >>> wrote: >>>>>=20 >>>>>> I'd also go with maintainer. >>>>>>=20 >>>>>> On 01.06.2016 10:32, Aljoscha Krettek wrote: >>>>>>> Hi, >>>>>>> I think maintainer is also fine if we clearly specify that they >> are >>>> not >>>>>>> meant as dictators or gatekeepers of the component that they are >>>>>>> responsible for. >>>>>>>=20 >>>>>>> -Aljoscha >>>>>>>=20 >>>>>>> On Wed, 1 Jun 2016 at 09:48 Vasiliki Kalavri < >>>> vasilikikalavri@gmail.com> >>>>>>> wrote: >>>>>>>=20 >>>>>>>> Hi, >>>>>>>>=20 >>>>>>>> we could go for something like "sponsor" or "champion" :) >>>>>>>> I'm fine with the proposal. Good to see more than 1 person for >> both >>>>>> Gelly >>>>>>>> and Table API. >>>>>>>>=20 >>>>>>>> cheers, >>>>>>>> -V. >>>>>>>>=20 >>>>>>>> On 1 June 2016 at 05:46, Tzu-Li (Gordon) Tai = >>=20 >>>>>> wrote: >>>>>>>>=20 >>>>>>>>> I'd like to be added to the Streaming Connectors component >>> (already >>>>>>>> edited >>>>>>>>> Wiki) :) >>>>>>>>>=20 >>>>>>>>> Ah, naming, one of the hardest problems in programming :P Some >>>>>> comments: >>>>>>>>> I agree with Robert that the name "maintainers" will be = somewhat >>>>>>>> misleading >>>>>>>>> regarding the authoritative difference with committers / PMCs, >>>>>> especially >>>>>>>>> for future newcomers to the community who don't come across = the >>>>>> original >>>>>>>>> discussion on this thread. >>>>>>>>>=20 >>>>>>>>> Simone's suggestion of Overseer seems good. The name naturally >>>> matches >>>>>>>> its >>>>>>>>> role - >>>>>>>>> - A group of "Overseers" for components, who keeps an eye on >>> related >>>>>> mail >>>>>>>>> threads, known limitations and issues, JIRAs, open PRs, >> requested >>>>>>>> features, >>>>>>>>> and potential new overseers and committers, etc, for the >> component >>>>>>>>> (original >>>>>>>>> maintainer role). >>>>>>>>> - A "Shepherd" for individual PRs, assigned from the overseers >> of >>>> the >>>>>>>>> component with the aim to guide the submitting contributor. >>>> Overseers >>>>>>>>> typically pick up new PRs to shepherd themselves, or the = leading >>>>>> overseer >>>>>>>>> allocates an overseer to shepherd a PR which hasn't been = picked >> up >>>> yet >>>>>>>>> after >>>>>>>>> a certain period of time. >>>>>>>>>=20 >>>>>>>>> Or perhaps we can also simply go for "Shepherds" for = components >>> and >>>>>>>>> "Assigned Shepherd" for individual PRs? >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> -- >>>>>>>>> View this message in context: >>>>>>>>>=20 >>>>>>>>=20 >>>>>>=20 >>>>=20 >>>=20 >> = http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/PROPOSAL-St= ructure-the-Flink-Open-Source-Development-tp11598p11932.html >>>>>>>>> Sent from the Apache Flink Mailing List archive. mailing list >>>> archive >>>>>> at >>>>>>>>> Nabble.com. >>>>>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>=20 >>>=20 >>=20