From dev-return-21974-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Sat Apr 14 17:25:40 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 9502B9126 for ; Sat, 14 Apr 2012 17:25:40 +0000 (UTC) Received: (qmail 96738 invoked by uid 500); 14 Apr 2012 17:25:40 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 96701 invoked by uid 500); 14 Apr 2012 17:25:40 -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 96691 invoked by uid 99); 14 Apr 2012 17:25:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Apr 2012 17:25:40 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dionne@dionne-associates.com designates 67.222.38.55 as permitted sender) Received: from [67.222.38.55] (HELO oproxy5-pub.bluehost.com) (67.222.38.55) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 14 Apr 2012 17:25:31 +0000 Received: (qmail 20381 invoked by uid 0); 14 Apr 2012 17:25:10 -0000 Received: from unknown (HELO host183.hostmonster.com) (74.220.207.183) by cpoproxy2.bluehost.com with SMTP; 14 Apr 2012 17:25:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dionne-associates.com; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=FBfGoLfM3+Q0e5MrVUnplgRYuSyObxeDELjRKEoXFkc=; b=MAiZ7s/SopkEcsWw9SB3x5zHHdioGq80K+g/tK2j4ai+AVGxi2Fvr5reNgbFUgSkwimCO2qrjgzi/AdreoALPjI0yHmJUfk4KuWNHRRjdUGOL6hGUouVbLFEgJUCqQ4d; Received: from adsl-99-36-6-194.dsl.wlfrct.sbcglobal.net ([99.36.6.194] helo=[192.168.1.115]) by host183.hostmonster.com with esmtpa (Exim 4.76) (envelope-from ) id 1SJ6ij-0006cI-Vk for dev@couchdb.apache.org; Sat, 14 Apr 2012 11:25:10 -0600 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1257) Subject: Re: Help shape the future of CouchDB: your voice needed! From: Bob Dionne In-Reply-To: Date: Sat, 14 Apr 2012 13:25:08 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <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> To: dev@couchdb.apache.org X-Mailer: Apple Mail (2.1257) X-Identified-User: {2551:host183.hostmonster.com:dionneas:dionne-associates.com} {sentby:smtp auth 99.36.6.194 authed with dionne@dionne-associates.com} 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 internal refactoring concerns and so forth. >>=20 >> It might help for everyone to see the list of features (here's a = cleaned up version I got from BobN) [1]. As Benoit suggests, we need to = sort/categorize them first before attaching priorities. >>=20 >> One thing we might think of is the areas they might be grouped in, = along the line of teams as Jan suggested at the summit. >=20 > 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 = folks think it can help make for more progress. > But yes we should organize > the things in different topics. >=20 >>=20 >> I'm happy to maintain this list as we drill down into the specifics, = summarize email threads, and IRC chats. Some of these, .eg. moving = metadata out of the docs, could easily require a lot of detailed = discussion as they hit many areas of the code, so we should flesh out = the details. >>=20 >=20 > I was thinking we could start a wiki and organize things in a table or > so . Thoughts? >=20 > - beno=EEt