Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@couchdb.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: [VOTE] WHY/HOW/WHAT
From: Johs Ensby <johs@b2w.com>
In-Reply-To: 
 <CAPMhwa5xMhnE79vU0VHYDtQyEtUJpRODhFw+oEKwqYbZ3BfVkA@mail.gmail.com>
Date: Fri, 18 Sep 2015 06:57:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4698E4C8-5F82-4522-94BE-E54FDF86813F@b2w.com>
References: <598DB9A8-EC3C-4DA6-9C8E-FF776492FD05@apache.org>
 <CAHdjipKgu2ZuUBTjAX8Dcs9=FJXjxwqTPCDyz07LO2=9=w-0dA@mail.gmail.com>
 <9249618D-5CEA-4A1E-A97A-937C8C01F32E@b2w.com>
 <CADA9kr8nHO5JCU=ojVhbaqAGW8eQZLWcBacRR_a8YcnmMZymbw@mail.gmail.com>
 <CAHw0XrtmyTEXJifBX-pqAe3+dGhuro1ahg88mDxcN6-A09mr3A@mail.gmail.com>
 <4C16CD94-7F17-4140-ABC3-1C34F38C9F5A@apache.org>
 <5DD3530A-0EC3-46D7-8CE1-2CDF8CEBFAE0@b2w.com>
 <CADdZc96u+t5DnZ8qC-k0CM_7XCwerY_4z8BwbPYBbyzgiKVqJA@mail.gmail.com>
 <CADA9kr-LezW1a=n5ouqbzwirhDZV5SC_MOD8YCGbNDfW=mTZ=g@mail.gmail.com>
 <CAHw0Xrvw67WzpSyHFP7bgDebmAzrZJ_R1XqP3VhRvUSuqx1yfg@mail.gmail.com>
 <CAPMhwa5xMhnE79vU0VHYDtQyEtUJpRODhFw+oEKwqYbZ3BfVkA@mail.gmail.com>
To: marketing@couchdb.apache.org

Jan,
could you restart voting
or would you like to keep it open for more slogan entires, or run a =
discussion on the 10 present candidates first?
Johs

> On 18. sep. 2015, at 06.52, Giovanni Lenzi <g.lenzi@smileupps.com> =
wrote:
>=20
> I add:
> 8: database for the web!!!
> 9: not just a database
> 10: Not only a database
>=20
> #8 +1: I think this is still the best option because it does not refer =
to a
> specific feature, and has the element/target which couchdb is all
> about/around
>=20
> Respectfully Jan, for direction in establishing the future you may =
listen
> to yourself and/or active erlang devs only, but this direction simply =
don't
> have community consensus. And this conflicts with the apache way!!!
>=20
> Also imho it's a wrong approach due to some considerations:
> - active devs are active now... who knows until when? (and this is =
true for
> you too and the VC chair)
> - you don't know if tomorrow some erlang skilled couchapp lover won't =
get
> in and start working on the app part (to say the truth some of them =
were
> already active in the past, but they chose to left just because of
> this/yours direction)
> - you can't remove something that ALREADY exists which A LOT of people
> like, use and have businesses on top, just because you and a few =
people
> don't like it
>=20
> But above all:
> - you can't erase what Couchdb has been, what it is actually and what =
it
> COULD BE!
>> We need constructive ideas
>=20
> I picked up options, spread among previous posts. There are 10 of =
them:
>=20
> 1. Data where you need it.
> 2. Restful freedom.
> 3. The database that replicates.
> 4. Sync. Shard. REST.
> 5. Keeps data closer.
> 6. Data wherever you need it.
> 7. Data that sync.
>=20
> Two more, that are app-related, are dropped, also I dropped my own
> proposal, it was the weakest (
>=20
> #1 and #2 are equal to Jan=E2=80=98s list.
>=20
> ermouth