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 26ECC200B8E for ; Mon, 26 Sep 2016 20:08:33 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 25479160ACA; Mon, 26 Sep 2016 18:08:33 +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 3A5A1160AC8 for ; Mon, 26 Sep 2016 20:08:32 +0200 (CEST) Received: (qmail 45195 invoked by uid 500); 26 Sep 2016 18:08:31 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 45178 invoked by uid 99); 26 Sep 2016 18:08:30 -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; Mon, 26 Sep 2016 18:08:30 +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 36D85C14A4 for ; Mon, 26 Sep 2016 18:08:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.18 X-Spam-Level: * X-Spam-Status: No, score=1.18 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=mueller-bruehl.de Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id a_ODuEacxdmg for ; Mon, 26 Sep 2016 18:08:26 +0000 (UTC) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.220]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 5E1FA5F4E5 for ; Mon, 26 Sep 2016 18:08:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1474913299; l=15227; s=domk; d=mueller-bruehl.de; h=Content-Type:In-Reply-To:MIME-Version:Date:From:References:To: Subject; bh=qp0Mkn6sIunOJO4FYQQAXneS2CFBrQN4UPmb3Y76EiQ=; b=Q9JIgWC/+Z8DgGmMHqE5MWooaRqFu0ZZ7ICFYGvX22O9kDcoC8V4poWdcOVZPxo4bxq GcsEJFlfrHziJ7rwfcLspzV57v8y4l916+QVUk5sJPfTx9z51jeV3IR2lFSMT+knM8OdH NUeR60698bWNBLYn3iSFn0bCq/wDJ663Jd0= X-RZG-AUTH: :IWUHfUGtd7F0djazuwsAfG6F2/Z16Xt2es6n2xdZO/ZHmfHTHTTidfmV3cv/m7XxquxLjcxPb3PE8wR5Ww== X-RZG-CLASS-ID: mo00 Received: from [192.168.1.211] (static-87-79-70-153.netcologne.de [87.79.70.153]) by smtp.strato.de (RZmta 39.3 AUTH) with ESMTPSA id D01bf8s8QI8J3F1 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Mon, 26 Sep 2016 20:08:19 +0200 (CEST) Subject: Re: [DISCUSS] Apache NetBeans Incubator Proposal To: general@incubator.apache.org References: <1423019168.2058021.1474443275667@mail.yahoo.com> <7F952C1B-6256-4F8D-90F4-703DB7A5C7D0@wadechandler.com> From: =?UTF-8?Q?Michael_M=c3=bcller?= Message-ID: <0d337b3b-3588-237b-453c-374fb5c398af@mueller-bruehl.de> Date: Mon, 26 Sep 2016 20:08:19 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------EDA39CE0FB78C8723283D8AF" archived-at: Mon, 26 Sep 2016 18:08:33 -0000 --------------EDA39CE0FB78C8723283D8AF Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi GJ, due to technical problems I missed one day of the discussion. I'm going to catch up. If possible, please add to to the initial commiters. Herzliche Grüße - Best Regards, Michael Müller Brühl, Germany blog.mueller-bruehl.de it-rezension.de @muellermi Read my books "Web Development with Java and JSF": https://leanpub.com/jsf "Java Lambdas und (parallel) Streams" Deutsche Ausgabe: https://leanpub.com/lambdas-de "Java Lambdas and (parallel) Streams" English edition: https://leanpub.com/lambdas On 09/23/2016 03:30 PM, Geertjan Wielenga wrote: > OK. Before the vote, will work on making the initial contributors list as > complete as possible. > > What is the process for doing that? Do I simply make changes directly in > the proposal? Do I make the changes public here before adding them to the > proposal? Do I work directly with the mentors via e-mails to discuss and > then after than make the changes? > > Thanks, > > Geertjan > > On Fri, Sep 23, 2016 at 10:02 AM, John D. Ament > wrote: > >> Hi Bertrand, >> >> Responses in line. >> >> On Thu, Sep 22, 2016 at 11:54 PM Bertrand Delacretaz < >> bdelacretaz@apache.org> >> wrote: >> >>> Hi Geertjan, >>> >>> I won't have time to look at your whole message now, just a few >>> clarifications as far as committers/PMC is concerned. >>> >>> On Fri, Sep 23, 2016 at 7:50 AM, Geertjan Wielenga < >>> geertjan.wielenga@googlemail.com> wrote: >>>> ...Anyone on the list >>>> will, once the proposal has been voted on and accepted, automatically >> be >>>> contributors to the Apache NetBeans project... >>> They will be commiters to be precise. >>> >> Agreed, the way I interpretted Geertjan is that Netbeans contributor == ASF >> committer. They don't have the role of PMC/PPMC presently, so we'll see >> how that evolves. >> >> >>>> Anyone not on the list will >>>> need to be voted in by the initial contributors, which is a process >> that >>>> could be fast, but is still a process and can be avoided by inclusion >> in >>>> the initial contributors list... >>> It's a simple process, the incubating project could very well have one >> vote >>> for N people if that makes sense and they are all wanted. >>> >> Its simple but hard. And no, I don't think we want bulk votes. What if >> someone is +1 add Mark S and -1 add Bertrand D? At least when its come up >> to the IPMC previously, we've recommended against it. >> >> >>>> Everyone on the initial contributors list is >>>> automatically part of the PMC. >>> There's no PMC for an incubating project, just a PPMC as per >>> http://incubator.apache.org/guides/ppmc.html >>> >>> That group has no formal power, only the Incubator PMC can vote on the >>> podling's releases or make other decisions which are binding at the >>> foundation level. >>> >>> In practice, you are correct that the PPMC is a PMC in training, but >> really >>> in a podling being a PPMC member doesn't make a difference IMO. >>> >> It does. PPMC has one important job - vote on adding more people. We hope >> that they will learn to look at their releases very carefully while under >> incubation. >> >> >>>> ...Anyone on the list when the project leaves >>>> incubation gets write access to the project for the rest of their >> life... >>> That's correct, but there can be a difference between the committers and >>> PMC members once the project graduates. As a mentor, when graduating I >>> would not accept a PMC member who has not contributed during incubation >> for >>> example, whereas a committer that hasn't really been active during >>> incubation is harmless. >>> >>> Committers don't have formal power once the project graduates, and if >> they >>> don't behave their commits rights can easily be suspended, temporarily or >>> permanently. That very rarely happens, just mentioning it to clarify the >>> risks. >>> >> That's... odd to say the least. I'm not aware of any specific cases, >> doesn't mean it hasn't' happened, but I can't think of any cases where it >> has (other than one special case recently of someone being asked out of the >> organization...) >> >> >>> In summary, what you don't want in an Apache project is poisonous PMC >>> members, so in my view to be on the PMC once graduating people will have >> to >>> demonstrate during incubation that they are making positive contributions >>> to it - just being on the initial list of committers doesn't count >> towards >>> that, in my book. >>> >>>> ...If the above is accurate, we do need to work on the initial >>> contributors >>>> list prior to voting on the proposal, quite aside from the infra >>> assessment... >>> >>> I still don't think that's required and should be avoided if it delays >> the >>> vote for NetBeans acceptance, as the list of committers can be modified >>> during incubation with just a bit of additional work. >>> >> I don't think this will add a lot of work. I even gave him the idea of >> just generating a script of past committers based on commit history. >> >> >>> If you still want do expand the list during incubation, best is to come >> up >>> with a list of additional names that the existing NetBeans community >> feels >>> deserve to be on that list (maybe based on votes on the existing NetBeans >>> community's channels), and have the NetBeans mentors accept that new >> list. >> Agreed 100%. If someone hasn't added anything in a while, has no interest >> in developing more, and the community doesn't see much benefit, they >> shouldn't be on the list. However, if that person does start contributing, >> please pay close attention to see if they're interested in coming back. >> >> >>> -Bertrand >>> --------------EDA39CE0FB78C8723283D8AF--