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 \(2104\))
Subject: Re: [VOTE] WHY/HOW/WHAT
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: <598DB9A8-EC3C-4DA6-9C8E-FF776492FD05@apache.org>
Date: Tue, 15 Sep 2015 21:57:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C60CAC78-B560-40BF-9A98-D20FE2CC07CE@apache.org>
References: <598DB9A8-EC3C-4DA6-9C8E-FF776492FD05@apache.org>
To: marketing@couchdb.apache.org


> On 15 Sep 2015, at 21:51, Jan Lehnardt <jan@apache.org> wrote:
>=20
> Hi all,
>=20
> as promised, here=E2=80=99s the vote for our new Slogan, Mission =
Statement, and Description.
>=20
> We have two contestants.
>=20
> Before I show them to you, here are the rules:
>=20
> 1. These aren=E2=80=99t final-copy-edit versions, but rough drafts =
that convey ideas. After voting, we=E2=80=99ll go through them with a =
fine-toothed comb to get things all shiny.
>=20
> 2. The proposals don=E2=80=99t mean to capture a laundry list of your =
favourite features of CouchDB. They are supposed to express the focal =
point that our community gathers around, the thing that we all have in =
common, what excites us all about CouchDB. Vote accordingly.
>=20
> 3. This emails contains two proposals. Vote by replying to this email =
with your vote just under each proposal where it says =E2=80=9CYour Vote =
Here=E2=80=9D.
>=20
> 4. Vote with +1 (I support this), +/-0 (I=E2=80=99m indifferent, but =
no harm done either way), -1 (I don=E2=80=99t like this, for reasons A, =
B and C, (and please do include your reasons)).
>=20
> 5. You are welcome to qualify your vote with your take on either =
proposal.
>=20
>=20
> A note: Johs, I took some inspiration from your WHAT-part, I hope you =
don=E2=80=99t mind ;) =E2=80=94  I think we are essentially voting on =
WHY and HOW anyway, as the WHAT is roughly the same idea.
>=20
> Without further ado, here are our proposals.
>=20
> * * *
>=20
> Proposal #1:
>=20
> Slogan: Data where you need it. (WHY)
>=20
> Mission Statement: Apache CouchDB lets you access your data where you =
need it by defining the Couch Replication Protocol that is implemented =
by a variety of projects and products that span every imaginable =
computing environment from distributed server-clusters, over mobile =
phones to web browsers. (HOW)
>=20
> Description: Store your data safely, on your own servers, or with any =
leading cloud provider. Your web- and native applications love CouchDB, =
because it speaks JSON natively and supports binary attachments for all =
your data storage needs. The Couch Replication Protocol lets your data =
flow seamlessly between server clusters to mobile phones and web =
browsers, enabling a compelling, offline-first, user-experience while =
maintaining high performance and strong reliability. CouchDB comes with =
a developer-friendly query language, and optionally MapReduce for =
simple, efficient, and comprehensive data retrieval. (WHAT)
>=20
> Your Vote Here

+1

I believe the WHY captures the one thing that we all share of the things =
that excite us about CouchDB and what embodies the core potential of =
CouchDB. The HOW and WHAT parts will need some copy-editing to read a =
litte nicer, but I think content-wise they capture what most people will =
find appealing when they look at CouchDB.


>=20
> * * *
>=20
> Proposal #2:
>=20
> Slogan: Restful freedom (WHY)
>=20
> Mission Statement: Data that sync (HOW)
>=20
> Description:=09
> Store your data safely, on your own servers or with any leading cloud =
provider. Your web applications can follow the data if you want since =
CouchDB speaks JSON with any file type attached. It lets you run your =
JavaScript on the server or in the browser. You can start with the =
smallest of technology stacks and grow to serve millions of users -- =
following a learning curve that doesn't break. Keep your data in sync =
and where your users need it to be, on the device of their preference, =
online or offline. Share, combine, present, receive and update documents =
via master-to-master replication and let web based services monitor =
changes for additional processing. (WHAT)
>=20
> Your Vote Here

-1

Aside from the (intentional) grammar-nit in the HOW that I can=E2=80=99t =
get beyond, I think the WHY, while it does express what we are about, =
doesn=E2=80=99t quite capture what we are about in a way that addresses =
our end-users needs or pains. It would be more fitting as for a =
community-internal, say, event or something like that.

Best
Jan
--