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 9A319F781 for ; Thu, 9 May 2013 16:00:15 +0000 (UTC) Received: (qmail 98218 invoked by uid 500); 9 May 2013 16:00:15 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 98190 invoked by uid 500); 9 May 2013 16:00:15 -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 98177 invoked by uid 99); 9 May 2013 16:00:15 -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 16:00:15 +0000 Received: from localhost (HELO mail-wg0-f41.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 16:00:14 +0000 Received: by mail-wg0-f41.google.com with SMTP id y10so6474466wgg.2 for ; Thu, 09 May 2013 09:00:12 -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=WE+tU6+6zb78fK/ROPqIYuKZSC/tRWuzKBhoS7yacIY=; b=GZU5k5L9JrDyPwnohWH8HISVN8KHIKvgI+MCvzrHwMH3QMZ/cKPD80sKaqaaHICTk4 svOZ0pm8rg1gA/XrvvafBh2nQ2ACBfN6sQUxnWDYlJkcYVbYO/AS2sc0516DhxOSGhCE paroDEhS0tmBJjyqOO4whX3gJ5N5ITn4TIqBKyScmj67c4Q3f/UPmkIVDjs5DnXll1Hn 2MDFWY/uXWZ74QaNGqN+5+lv54FUMMHm2W0r/5q9FpXabMhE/0mvFlZlLQ5/vWNRezPY oCxYSYdShtNu3CSEiyE6RKwGVVtdM+0qOxDifU3McKNrkaD/TLqMpkPTRx4AImHpZSxE t5TQ== MIME-Version: 1.0 X-Received: by 10.194.61.10 with SMTP id l10mr19051117wjr.32.1368115212358; Thu, 09 May 2013 09:00:12 -0700 (PDT) Received: by 10.217.82.69 with HTTP; Thu, 9 May 2013 09:00:12 -0700 (PDT) X-Originating-IP: [79.97.124.139] In-Reply-To: References: Date: Thu, 9 May 2013 17:00:12 +0100 Message-ID: Subject: Re: [DISCUSS] dont't abuse of "lazy concensus" on mail tagged [DISCUSS] From: Noah Slater To: Randall Leeds Cc: "dev@couchdb.apache.org" , Noah Slater Content-Type: multipart/alternative; boundary=047d7ba97e043eadb504dc4b25fc X-Gm-Message-State: ALoCoQngybYbCS6eEf+higTmIkDEjoUWk2J740Pv2ebJFR1Zxsj/VRh2j4R+YEVXx1CWYAiM4H0r --047d7ba97e043eadb504dc4b25fc Content-Type: text/plain; charset=ISO-8859-1 On 9 May 2013 03:59, Randall Leeds wrote: > > However, to restate my position, DISCUSS had a suggestion to me that > something > warranted discussion. Your recent threads on workflow all were great. We > should > circle back and conclude them. When something warrants good discussion, > it's > worthwhile to get as much input as we can, and thus it suggests a longer > window > would be appropriate to me. > Totally agreed! I think if anybody had attempted to use lazy consensus on that thread, they would have been met with a swift objection. So, in many cases, it's a judgement call. But I think you can be sure that mistakes will be corrected for. Also, it's important for us all to remember that everything is reversible If something doesn't work, or some change gets committed that breaks CouchDB, we just revert it, or change things back to how they were. > 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. > > Sounds like we need a well-understood set of these. > > If we can just enumerate them all I'd be happy to clean it up and make > a definitions file. > > Noah, is this included in your idea of bylaws, or is this a separate > document? > Hmm. I guess it would be good to standardise them. Not sure you'd want to make them a requirement. But perhaps just include them as suggestions. LIke a set of best practices. Totally open to possibilities here! -- NS --047d7ba97e043eadb504dc4b25fc--