Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates
 209.85.217.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <91DAAC41-2AE8-44F0-88A4-FFFDC927E277@dionne-associates.com>
References: <20120414002434.GA22219@atypical.net>
	<1334416226.2951.1.camel@devil>
	<91DAAC41-2AE8-44F0-88A4-FFFDC927E277@dionne-associates.com>
Date: Sat, 14 Apr 2012 19:11:08 +0200
Message-ID: 
 <CAJNb-9qHWP_Og5hsotWtqBCAu-4nQG3eyWdrmRJzTeKDu2MS2Q@mail.gmail.com>
Subject: Re: Help shape the future of CouchDB: your voice needed!
From: Benoit Chesneau <bchesneau@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 14, 2012 at 6:30 PM, Bob Dionne
<dionne@dionne-associates.com> 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 int=
ernal refactoring concerns and so forth.
>
> 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/catego=
rize them first before attaching priorities.
>
> 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.

We are actually all agree on the need to have focus points. I still
strongly disagree with this idea of team. But yes we should organize
the things in different topics.

>
> I'm happy to maintain this list as we drill down into the specifics, summ=
arize 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.
>

I was thinking we could start a wiki and organize things in a table or
so . Thoughts?

- beno=EEt