From dev-return-21982-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Sun Apr 15 06:02:05 2012 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 0E7F2950F for ; Sun, 15 Apr 2012 06:02:05 +0000 (UTC) Received: (qmail 44857 invoked by uid 500); 15 Apr 2012 06:02:04 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 44773 invoked by uid 500); 15 Apr 2012 06:02:02 -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 44752 invoked by uid 99); 15 Apr 2012 06:02:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Apr 2012 06:02:02 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.216.52] (HELO mail-qa0-f52.google.com) (209.85.216.52) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Apr 2012 06:01:55 +0000 Received: by qabg40 with SMTP id g40so3333657qab.11 for ; Sat, 14 Apr 2012 23:01:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding:x-gm-message-state; bh=kPUS7vYGcTtTtvjy5FkbTxzl5kmUaMRemRn2dOes8oc=; b=a1HPeWknZ9Nb7UJ5eewsmZySjJNLe2PkIBqSmpjF2iENhFM5cURH394UsWDWZwGbdL SUgYk3CHTNzMJR5G1c1HmTUQgqE/uI09JDJYyoCx2S7X1QHTA3tI20nDHpbn7Q8IXk+g WywviIW59fBCtpv2wBsjg/64p7WRM/U9GQkTBgdSEGpVpYnmuQXWbRqwLg8ItfKOArn/ oCjuM+rrK8anFTh7VUAJanv3BzuhDqRj+lCDKUR8BfG4XmoKH6/yVeSRc3F5YJBPV747 /Tsf85ZAV2ZNa2tpL+QT2tUWaZYW67JXrrRNpL+HqqOO1oCaqQ0i+h0YQscXk0jRJFJ4 Ta2A== MIME-Version: 1.0 Received: by 10.229.102.88 with SMTP id f24mr2812420qco.117.1334469692948; Sat, 14 Apr 2012 23:01:32 -0700 (PDT) Received: by 10.224.215.70 with HTTP; Sat, 14 Apr 2012 23:01:32 -0700 (PDT) In-Reply-To: <7E769DE7-6A96-4001-BCF0-5652446C7C50@dionne-associates.com> References: <20120414002434.GA22219@atypical.net> <1334416226.2951.1.camel@devil> <91DAAC41-2AE8-44F0-88A4-FFFDC927E277@dionne-associates.com> <7E769DE7-6A96-4001-BCF0-5652446C7C50@dionne-associates.com> Date: Sun, 15 Apr 2012 18:01:32 +1200 Message-ID: Subject: Re: Help shape the future of CouchDB: your voice needed! From: Tim McNamara To: dev@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkQMu8bAM1QuNPExsRXE6m9ItF0mBwE5FbTZN1iGE54YroPA4Rw/2VGrgHxMrxL+rxDbNXl One of the good reasons for this format (although I have no idea if it is why it's why it was chosen) is that there are some good statistics behind pairwise comparison. On 15 April 2012 05:25, Bob Dionne wrote: > > On Apr 14, 2012, at 1:11 PM, Benoit Chesneau wrote: > >> On Sat, Apr 14, 2012 at 6:30 PM, Bob Dionne >> wrote: >>> I kind of agree, though I think voting is neat. I'd like to think most = of these features are influenced by experiences with users in addition to i= nternal refactoring concerns and so forth. >>> >>> It might help for everyone to see the list of features (here's a cleane= d up version I got from BobN) [1]. As Benoit suggests, we need to sort/cate= gorize them first before attaching priorities. >>> >>> One thing we might think of is the areas they might be grouped in, alon= g the line of teams as Jan suggested at the summit. >> >> We are actually all agree on the need to have focus points. I still >> strongly disagree with this idea of team. > > I'm not a big fan of teams either, but willing to go along if enough folk= s think it can help make for more progress. > > >> But yes we should organize >> the things in different topics. >> >>> >>> I'm happy to maintain this list as we drill down into the specifics, su= mmarize email threads, and IRC chats. Some of these, .eg. moving metadata o= ut of the docs, could easily require a lot of detailed discussion as they h= it many areas of the code, so we should flesh out the details. >>> >> >> I was thinking we could start a wiki and organize things in a table or >> so . Thoughts? >> >> - beno=C3=AEt >