From kato-dev-return-55-apmail-incubator-kato-dev-archive=incubator.apache.org@incubator.apache.org Tue Mar 03 16:50:46 2009 Return-Path: Delivered-To: apmail-incubator-kato-dev-archive@minotaur.apache.org Received: (qmail 9054 invoked from network); 3 Mar 2009 16:50:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2009 16:50:45 -0000 Received: (qmail 16395 invoked by uid 500); 3 Mar 2009 16:50:45 -0000 Delivered-To: apmail-incubator-kato-dev-archive@incubator.apache.org Received: (qmail 16376 invoked by uid 500); 3 Mar 2009 16:50:45 -0000 Mailing-List: contact kato-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: kato-dev@incubator.apache.org Delivered-To: mailing list kato-dev@incubator.apache.org Received: (qmail 16365 invoked by uid 99); 3 Mar 2009 16:50:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 08:50:45 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ant.elder@gmail.com designates 209.85.218.165 as permitted sender) Received: from [209.85.218.165] (HELO mail-bw0-f165.google.com) (209.85.218.165) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 16:50:39 +0000 Received: by bwz9 with SMTP id 9so2478582bwz.12 for ; Tue, 03 Mar 2009 08:50:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:date:message-id :subject:from:to:content-type; bh=WWU5HEWPqv86BY+/RXOFZU+GmZuHyL85sD26m7Jfnzg=; b=npq0Jj/xM/a15IGw+AoBSNQLB7l9eg03Cha7XB90CUJRuUJCj2/q2fL3GHQAzUvSTk /wOxJjLUNSTZwO43524smfCO+3jAAKUTcO/imxUHKp/+xryFR3ti59UkazKHO83p8bwO 79Qp+SPXsPYnAqOPJzUfStUdRF2cfymTPVGQI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; b=ovjcZlbzvjxbUSn7aIz/0yhnCUBO2bzXhlx8BIunqn0tKFFiFvOwlpUH0A4CA/sr5H w/a/KEWAxDwMSMbBqvMC04zDz0yuFJBqWVq2CRNyi2Fo0uqqxztmnzR/j6jKad10yrYG c3p+S3rgjRhpixh4kdTfSWw7tzSKt8YaohPXg= MIME-Version: 1.0 Received: by 10.181.223.2 with SMTP id a2mr2612563bkr.1.1236099017470; Tue, 03 Mar 2009 08:50:17 -0800 (PST) Reply-To: antelder@apache.org Date: Tue, 3 Mar 2009 16:50:17 +0000 Message-ID: <71e1b5740903030850v36734705wb51d1d628a22e7ae@mail.gmail.com> Subject: Voting and getting things done From: ant elder To: kato-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=001636c5b779d7f4a7046439ba33 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5b779d7f4a7046439ba33 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I thought it might be worthwhile commenting about voting in Apache projects. There are times when you need to officially record a decision and you can do that with a vote, for example, you can't make a release till there has been a vote which needs at least three binding +1s for it to pass. Many other times you need to make decisions but the formality and overhead of a vote isn't necessary. One approach with less overhead is to just go ahead and do something then afterwards if necessary post to the dev list mentioning what you did, if there are comments you can iterate around making changes till everyone is happy. Another alternative is to use lazy consensus and say on the dev list that you're planning on doing something in a few days if no one replies with any comments or objections. There are policies defining when a formal vote is mandatory, when there is no policy you need to make a judgement call, big changes that impact multiple people probably should at least be mentioned first, less significant changes you can probably just go right ahead and do. For most things it can be quicker and easier not to have a vote. ...ant --001636c5b779d7f4a7046439ba33--