Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@couchdb.apache.org
Date: Tue, 15 Sep 2015 22:45:56 -0400 (EDT)
From: Joan Touzet <wohali@apache.org>
Reply-To: Joan Touzet <wohali@apache.org>
To: marketing@couchdb.apache.org
Message-ID: <22938574.2453.1442371554698.JavaMail.Joan@RITA>
In-Reply-To: <17A91E0A-B094-4FBF-8554-959E9F2DD5B2@apache.org>
Subject: Re: [VOTE] WHY/HOW/WHAT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

My vote and reasoning matches Michelle's. Would be happy to see
more options and an additional vote, if people prefer.

-Joan

----- Original Message -----
> From: "Michelle Phung" <michellep@apache.org>
> To: marketing@couchdb.apache.org
> Sent: Tuesday, September 15, 2015 4:07:54 PM
> Subject: Re: [VOTE] WHY/HOW/WHAT
>=20
> #1: +1
> #2: -1
> reasons are inline
>=20
> -michellep
>=20
> > On Sep 15, 2015, at 3:51 PM, Jan Lehnardt <jan@apache.org> wrote:
> >=20
> > Hi all,
> >=20
> > as promised, here=E2=80=99s the vote for our new Slogan, Mission Statem=
ent,
> > 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=9CYo=
ur
> > 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
> seems straight-forward, language flows well
> > * * *
> >=20
> > Proposal #2:
> >=20
> > Slogan: Restful freedom (WHY)
> >=20
> > Mission Statement: Data that sync (HOW)
> >=20
> > Description:
> > 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
> don=E2=80=99t like the word =E2=80=9Cleading=E2=80=9D, (seems unnecessary=
, and doesn=E2=80=99t denote
> anything) (this is in both descriptions btw)
> many colloquialisms
> "Share, combine, present, receive and update=E2=80=9D is too long a list
> dislike the word =E2=80=98if=E2=80=99 used in the description, (making as=
sumptions)
>=20
> > * * *
> >=20
> > Thanks!
> > Jan
> > --
> >=20
> >=20
>=20
>=20