Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9AEED1124D for ; Thu, 3 Apr 2014 20:29:48 +0000 (UTC) Received: (qmail 92092 invoked by uid 500); 3 Apr 2014 20:29:47 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 91843 invoked by uid 500); 3 Apr 2014 20:29:46 -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 91835 invoked by uid 99); 3 Apr 2014 20:29:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 20:29:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mdrob@cloudera.com designates 209.85.219.41 as permitted sender) Received: from [209.85.219.41] (HELO mail-oa0-f41.google.com) (209.85.219.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 20:29:41 +0000 Received: by mail-oa0-f41.google.com with SMTP id j17so2612888oag.0 for ; Thu, 03 Apr 2014 13:29:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=eySepd92EBhSc4/l4ER/uDQfLpRXwzr1SAcIvT9NU4Q=; b=PKZph9Q5wsv5kig9ZUyrwLGL5srUgHtMSIUOO/6pHKBc5BdeTPhjvPyW2bhlt4nE+T yZ4SBf37ID7FJuqM3XbWcbUzOOgTsouYXzF/yDHAGgS3M3mTfPyXqzd4/Zvb2gxWAhF9 gXmX9bMV1H9D0FV5A1pP3d4XDe0bwnrNc3ODuzzv2i4Tgtofp44P2oVuWA1hqLe/c8WF RfJfS12hOxHVrSOSkpHnyRAzdU6pImEN0wZ9Efw1mvJIGTzR7RmDs484Zp1dzOoWUvEz D7Ahr4VdIEwlX0Ocaz5TaIih03y/O645nG23j19CodHNvY5gShorZxl48I/Fl7nKaULP Yvow== X-Gm-Message-State: ALoCoQnazS82oNTGusxdF8SR4JbNdGczpbz66baUe/u+g2tOon6wRxGcvT5TdRHYRJypLWXIURDd X-Received: by 10.60.40.39 with SMTP id u7mr6217033oek.56.1396556960718; Thu, 03 Apr 2014 13:29:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.170.135 with HTTP; Thu, 3 Apr 2014 13:29:00 -0700 (PDT) In-Reply-To: References: From: Mike Drob Date: Thu, 3 Apr 2014 13:29:00 -0700 Message-ID: Subject: Re: [VOTE] Accumulo Bylaws, vote 2 To: dev@accumulo.apache.org Content-Type: multipart/alternative; boundary=089e0139ffbe8d748a04f6294182 X-Virus-Checked: Checked by ClamAV on apache.org --089e0139ffbe8d748a04f6294182 Content-Type: text/plain; charset=ISO-8859-1 bhavanki: can you expand on why you didn't like consensus approval for the bylaws? On Thu, Apr 3, 2014 at 1:13 PM, Bill Havanki wrote: > I dug into the dev archives for how the approval definition got set. > Originally, from the ZooKeeper bylaws [1], modification required 2/3 > majority of ALL PMC members to +1 in order to pass. Billie didn't prefer > that since it isn't an ASF-defined vote, and suggested consensus [2] > (February 26). > > I didn't like that and preferred majority since (surprise!) I didn't like > the idea of a veto. I preferred majority approval. [next in thread after 2] > Billie said she was neutral about that [second in thread after 2]. So, I > set it to majority approval and said anyone can switch it to consensus, > that would be fine [3] (March 4). No one changed it. So, here we are. > > The ASF voting guidelines [4] only discuss vetoes in the context of code > modification. Its section on Procedural Votes is unhelpfully empty. > However, at the top it says: > > Votes on procedural issues follow the common format of majority rule unless > otherwise stated. That is, if there are more favourable votes than > unfavourable ones, the issue is considered to have passed -- regardless of > the number of votes in each category. (If the number of votes seems too > small to be representative of a community consensus, the issue is typically > not pursued. However, see the description of lazy consensus for a modifying > factor.) > > > When I called this vote, I decided that since the bylaws stated majority > approval for modifications, the vote should be majority approval. There was > time for the community to deliberate about it before the vote, so absent > any concern (that I recall seeing) it was the consistent choice. (In fact, > the first vote Mike called on March 10 was also majority approval.) > > That is my rationale for majority approval in this vote. > > Bill > > [1] http://zookeeper.apache.org/bylaws.html > [2] > > http://mail-archives.apache.org/mod_mbox/accumulo-dev/201402.mbox/%3CCAF1jEfDsHU_tG94TNs-=Mss65geDp2yvxEmpGR1KzQ5Gsb-+9A@mail.gmail.com%3E > [3] > > http://mail-archives.apache.org/mod_mbox/accumulo-dev/201403.mbox/%3CCAD-fFU+SX7aE0cMu5AC9xVR0OxwGeMm-V0O0rNpeQCnxuvAr0Q@mail.gmail.com%3E > [4] http://www.apache.org/foundation/voting.html > > > On Thu, Apr 3, 2014 at 4:03 PM, Christopher wrote: > > > Unfortunately, I think I'm going to have to change my vote to a -1, > > based on the point that John just brought up. > > > > After some thought, I'm not sure it makes sense for people to be bound > > by operating rules they did not agree to, especially for the initial > > adoption. I think consensus approval makes more sense for modifying > > the bylaws (and for the initial adoption of those bylaws) than does > > majority approval. > > > > -- > > Christopher L Tubbs II > > http://gravatar.com/ctubbsii > > > > > > On Thu, Apr 3, 2014 at 3:32 PM, John Vines wrote: > > > I'm also wondering if modifying bylaws, for now and in the future, > should > > > be consensus approval. Why is that scaled down to Majority? > > > > > > > > > On Thu, Apr 3, 2014 at 3:13 PM, John Vines wrote: > > > > > >> -1 > > >> > > >> There is still no clarity on code change actions, which I think need > to > > be > > >> resolved before it should pass. It seems to be ambiguous, > intentionally, > > >> with the intent to revise later. If that's the case, it should just be > > >> removed until a more definitive guideline can be put in place. Or just > > >> point at an existing CTR guideline. > > >> > > >> > > >> On Thu, Apr 3, 2014 at 2:18 PM, Bill Havanki < > bhavanki@clouderagovt.com > > >wrote: > > >> > > >>> Reminder to all: the bylaw vote ends at 10 AM EDT / 7 AM PDT tomorrow > > >>> morning. Majority approval is required. > > >>> > > >>> Thanks, > > >>> Bill > > >>> > > >>> > > >>> On Thu, Apr 3, 2014 at 2:13 PM, Mike Drob > wrote: > > >>> > > >>> > +1 > > >>> > > > >>> > > > >>> > On Wed, Apr 2, 2014 at 6:26 AM, Eric Newton > > > >>> wrote: > > >>> > > > >>> > > +1 > > >>> > > > > >>> > > Thank you all for working through something that makes me want to > > go > > >>> back > > >>> > > to reading gigabytes of debug logs. > > >>> > > > > >>> > > -Eric > > >>> > > > > >>> > > > > >>> > > > > >>> > > On Tue, Apr 1, 2014 at 3:10 PM, Billie Rinaldi < > billie@apache.org> > > >>> > wrote: > > >>> > > > > >>> > > > Hey everyone! We only have 3 more days to vote on Accumulo's > > bylaws > > >>> > ... > > >>> > > > > > >>> > > > > > >>> > > > On Fri, Mar 28, 2014 at 6:55 AM, Bill Havanki < > > >>> > bhavanki@clouderagovt.com > > >>> > > > >wrote: > > >>> > > > > > >>> > > > > Please vote on the proposed bylaws, as available at > > >>> > > > > > > >>> > > > > * > > >>> > > > > > > >>> > > > > > >>> > > > > >>> > > > >>> > > > https://svn.apache.org/viewvc/accumulo/site/trunk/content/bylaws.mdtext?revision=1582476&view=markup > > >>> > > > > < > > >>> > > > > > > >>> > > > > > >>> > > > > >>> > > > >>> > > > https://svn.apache.org/viewvc/accumulo/site/trunk/content/bylaws.mdtext?revision=1582476&view=markup > > >>> > > > > >* > > >>> > > > > > > >>> > > > > A nicer-to-read version is available at > > >>> > > > > > > >>> > > > > http://accumulo.apache.org/bylaws.html > > >>> > > > > > > >>> > > > > This vote will be open for 7 days, until 4 April 2014 14:00 > > UTC. > > >>> > > > > > > >>> > > > > Upon successful completion of this vote, the first line of > the > > >>> > document > > >>> > > > > body > > >>> > > > > will be replaced with "This is version 1 of the bylaws," and > > the > > >>> > > > statement > > >>> > > > > defining the document as a draft will be stricken. > > Additionally, a > > >>> > link > > >>> > > > to > > >>> > > > > the document will be added to the navigation menu. > > >>> > > > > > > >>> > > > > This vote requires majority approval to pass: at least 3 +1 > > votes > > >>> and > > >>> > > > more > > >>> > > > > +1 > > >>> > > > > than -1's. > > >>> > > > > > > >>> > > > > [ ] +1 - "I approve of these proposed bylaws and accept them > > for > > >>> the > > >>> > > > > Apache Accumulo > > >>> > > > > project." > > >>> > > > > [ ] +0 - "I neither approve nor disapprove of these proposed > > >>> bylaws, > > >>> > > but > > >>> > > > > accept them for the Apache Accumulo project." > > >>> > > > > [ ] -1 - "I do not approve of these proposed bylaws and do > not > > >>> accept > > >>> > > > them > > >>> > > > > for > > >>> > > > > the Apache Accumulo project because..." > > >>> > > > > > > >>> > > > > Thank you. > > >>> > > > > > > >>> > > > > -- > > >>> > > > > // Bill Havanki > > >>> > > > > // Solutions Architect, Cloudera Govt Solutions > > >>> > > > > // 443.686.9283 > > >>> > > > > > > >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > > >>> > > >>> -- > > >>> // Bill Havanki > > >>> // Solutions Architect, Cloudera Govt Solutions > > >>> // 443.686.9283 > > >>> > > >> > > >> > > >> > > >> -- > > >> Cheers > > >> ~John > > >> > > > > > > -- > // Bill Havanki > // Solutions Architect, Cloudera Govt Solutions > // 443.686.9283 > --089e0139ffbe8d748a04f6294182--