Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED61AE3FF for ; Fri, 8 Feb 2013 03:52:58 +0000 (UTC) Received: (qmail 19803 invoked by uid 500); 8 Feb 2013 03:52:57 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 19598 invoked by uid 500); 8 Feb 2013 03:52:57 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 19550 invoked by uid 99); 8 Feb 2013 03:52:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2013 03:52:55 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rohityadav89@gmail.com designates 209.85.210.176 as permitted sender) Received: from [209.85.210.176] (HELO mail-ia0-f176.google.com) (209.85.210.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2013 03:52:49 +0000 Received: by mail-ia0-f176.google.com with SMTP id i18so3683008iac.7 for ; Thu, 07 Feb 2013 19:52:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=WclmroErsA3ihyG1UPSQa4yutPFfSD6vmZYAFSU5uo0=; b=ceD7AyEmYpF/LbEv+342e7+LwlWzIfO5dWMBl0b/2iCVVy0XAja4pbxAfXt0x3PSGq qwRJbN+ik0tnYBgl1GmgVK3HPCB3dsOOhhXBJwb2ofoL6RunyOfDDaPxeZmYIf3pZ1Ro 2+9stVb/XRZXBY0m/Om7LfshDchfMNDEC56xV96Tyh1PeI2MjlzQuWglKMq8Lq54wy2o rljtpO9mumeUlhqG+gesK3mdccP0ByV0hnoPgJlXm5KLj8+NJeLwr/feqW5Wms4iy6OS PdspGwpLuMi2mp3ZqLUNz4gMj1MmOsa+n24pvSbUekcSV3S/1rLQ5reg8JaIg7BrrPPq E2uA== X-Received: by 10.50.214.97 with SMTP id nz1mr7782106igc.36.1360295549092; Thu, 07 Feb 2013 19:52:29 -0800 (PST) MIME-Version: 1.0 Sender: rohityadav89@gmail.com Received: by 10.50.111.16 with HTTP; Thu, 7 Feb 2013 19:52:08 -0800 (PST) In-Reply-To: <20130208022545.GB52695@USLT-205755.sungardas.corp> References: <20130208022545.GB52695@USLT-205755.sungardas.corp> From: Rohit Yadav Date: Fri, 8 Feb 2013 09:22:08 +0530 X-Google-Sender-Auth: _AwEKY4J24pKmWOdYqLDxonlcRk Message-ID: Subject: Re: [VOTE] Revert back to old mailing list mechanism, which would add "Reply-To: mailing list" to every mail it send out To: Chip Childers Cc: Sheng Yang , Alex Huang , Brett Porter , Animesh Chaturvedi , David Nalley , Edison Su , runseb@gmail.com, dkulp@apache.org, htrippaers@schubergphilis.com, shadowsor@gmail.com, somikbehera@vmware.com, frank.zhang@citrix.com, wido@widodh.nl, "cloudstack-dev@incubator.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org +1 the old way On Fri, Feb 8, 2013 at 7:55 AM, Chip Childers wrote: > On Thu, Feb 07, 2013 at 04:00:46PM -0800, Sheng Yang wrote: >> Hi all, >> >> I'd like to call for a vote for reverting back to the old mailing list >> mechanism, which would add "Reply-To: mailing list" to every mail it >> send out. > > +1 (binding) > > Point of order question: > > I'd like to ask exactly which type of vote we believe we are holding > here. Not to be the "rules guy", but isn't this a technical decision? > If so, the bylaws we agreed to were that technical decisions are > only put to a formal vote in circumstances where discussion was unable > to achieve consensus. I guess that's what you believe has happened. > > That being said, we've basically started a vote that you could immediate > close down. You've cast a -1 vote, and technical decisions are formally > voted on using the lazy consensus (at least 3 +1 binding votes, and no > binding -1 votes). Based on that, and the wording of this vote, the vote > itself is procedurally meaningless. It's more useful as a continuation > of the conversation thread. > > The more appropriate vote would be to assume that the questions were > being raised, based on a technical change to the mailing list. Effectively, > the state that we were in is the baseline (prior to the change), and several > people have expressed opinions that are against that original technical decision. > > -chip