Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-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 23BD7101C5 for ; Thu, 9 May 2013 02:02:58 +0000 (UTC) Received: (qmail 80740 invoked by uid 500); 9 May 2013 02:02:57 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 80705 invoked by uid 500); 9 May 2013 02:02:57 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 80691 invoked by uid 99); 9 May 2013 02:02:57 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 May 2013 02:02:57 +0000 Received: from localhost (HELO mail-ie0-f174.google.com) (127.0.0.1) (smtp-auth username nslater, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 May 2013 02:02:57 +0000 Received: by mail-ie0-f174.google.com with SMTP id 10so4509519ied.19 for ; Wed, 08 May 2013 19:02:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=/jY26H1M2kJuxwIjvy1sZrSqM2yX+IPzkgN7dRPS3iY=; b=aPnTHDmoCbRs3PMAiwT/MBX1oEYdZplaFpNraxVr+wiGqgCxNoeftRt2cTUCXIbUXp tPEMdqOz0ofXOkTZjBG+QJ1/vwdTfPxzA46gNm1lV5YcisQgEMLGXOqbjGVyj80T/2BS lVcNue/BoUFgi/bUhUVINRst4Xhwpurot72RG6UtRZtfKr1L1CW9P8FZVu3G4rJSUi2V 68AYdT4XSIREtIatazM5C+Q26MZnHlVqAwvjvfXGzXOyh4IVTJJbChHMDCwCOTANRxlb fZygZsGvbaARzI0qq9TH8LfOwnzS0Bc4vhN3Wj9UmTMmnBDhu116+I/BwPgh6E1hU+tn MJ5A== MIME-Version: 1.0 X-Received: by 10.42.61.137 with SMTP id u9mr3206182ich.33.1368064976298; Wed, 08 May 2013 19:02:56 -0700 (PDT) Received: by 10.50.57.114 with HTTP; Wed, 8 May 2013 19:02:56 -0700 (PDT) X-Originating-IP: [178.250.115.206] In-Reply-To: References: Date: Thu, 9 May 2013 03:02:56 +0100 Message-ID: Subject: Re: [DISCUSS] dont't abuse of "lazy concensus" on mail tagged [DISCUSS] From: Noah Slater To: Noah Slater Cc: "dev@couchdb.apache.org" Content-Type: multipart/alternative; boundary=20cf302237e7f1558104dc3f7228 X-Gm-Message-State: ALoCoQmHVmh5xVVwAH9mNBSEhJ+3lrSFKts2KKrbe7rYbwLVEGh8MeFnvjZCaodfBXZ4ZJt6OSyi --20cf302237e7f1558104dc3f7228 Content-Type: text/plain; charset=ISO-8859-1 On 9 May 2013 01:02, Noah Slater wrote: > > I would be happy to use the subject tag PROPOSAL when lazy consensus is > being used, to separate these threads out from general DISCUSS threads. > Please note, however, that in my mental model of how Apache works, a > DISCUSS thread *is* a discussion that will default to lazy consensus. That > is how I have always used that tag. If you think it's confusing, let's > propose a new tag. > I will note, actually, that the tag I put in the email thread is besides the point. That's just a matter of courtesy. The default model that we operate under is that if I announce my intentions to the dev@ list, then you have 72 hours to object. This works for two reasons: 1) People are elected to committer, primarily, because we *trust* them. That means we trust them to act in the best interests of the project. 2) If you care about this stuff, you need to be monitoring dev@ and you need to be voicing your objections. If you are not doing this, you cannot expect the project to slow down to suit your pace. There are some things that are too important to leave to lazy consensus. For those things, we should explicitly say "okay, if you're trying to do X then you need a formal vote with majority approval". It sounds to me like you've been caught off-guard because a few decisions have been made and you didn't have time to contribute. I would suggest two things. 1) Set up email filters so that DISCUSS, VOTE, NOTICE threads get priority in your inbox. 2) Come up with a list of things you think we should not leave to lazy consensus. So no, I don't think anybody has "abused" anything. Unless you mean to suggest that somebody is being tricky and is trying to "slip something past". That would be a very serious allegation, so you should make that explicit if you believe it to be the case. Again, if you have some exceptions in mind (releases, new committers, new PMC members, new chairs are all good examples) please bring them to the list, and we can start our first draft of the by-laws. -- NS --20cf302237e7f1558104dc3f7228--