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: Brainstorm: A new CouchDB tag-line?
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: <64AA3206-0877-495C-83E2-4159C6BE2EE9@apache.org>
Date: Tue, 15 Sep 2015 21:40:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <048E3CD4-F54C-4871-B372-E9126E52FB3C@apache.org>
References: <20350143.1154.1441825321707.JavaMail.Joan@RITA>
 <404FC399-D26F-43EC-B7FA-8BC6EE75756E@b2w.com>
 <64AA3206-0877-495C-83E2-4159C6BE2EE9@apache.org>
To: marketing@couchdb.apache.org

Sorry for the delay, the vote goes out momentarily.

Best
Jan
--

> On 14 Sep 2015, at 13:56, Jan Lehnardt <jan@apache.org> wrote:
>=20
> *nudge* everybody, get your proposals in.
>=20
> I plan to start a vote on this around this time tomorrow.
>=20
> Best
> Jan
> --
>=20
>> On 09 Sep 2015, at 22:00, Johs Ensby <johs@b2w.com> wrote:
>>=20
>> WHY	Restful freedom
>> HOW	Data that sync
>>=20
>> WHAT=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.=20
>>=20
>> Johs:)
>>=20
>>=20
>>> On 9. sep. 2015, at 21.02, Joan Touzet <wohali@apache.org> wrote:
>>>=20
>>> +1
>>>=20
>>> ----- Original Message -----
>>>> From: "Jan Lehnardt" <jan@apache.org>
>>>> To: marketing@couchdb.apache.org
>>>> Cc: private@couchdb.apache.org
>>>> Sent: Wednesday, September 9, 2015 11:45:40 AM
>>>> Subject: Re: Brainstorm: A new CouchDB tag-line?
>>>>=20
>>>> I=E2=80=99d like to get this wrapped up and I propose a similar =
process to
>>>> what we did for the logo:
>>>>=20
>>>> 1. Have us (marketing@) come up with a few alternative approaches
>>>> (all addressing WHY, HOW, WHAT, split out in a Slogan (WHY), =
Mission
>>>> Statement (HOW) and Description (WHAT) that we can use all over our
>>>> messaging.
>>>>=20
>>>> 2. Put the candidates to a vote here on marketing@, the top 5-10 =
(if
>>>> we get that many) then go to a vote on dev@
>>>>=20
>>>> 3. =46rom the vote result on dev@, the PMC then makes a decision on =
the
>>>> final set.
>>>>=20
>>>> It=E2=80=99d be great if we get this rounded up by ApacheCon EU =
(that=E2=80=99s Sept
>>>> 28), and because of that, I propose the following schedule:
>>>>=20
>>>> marketing@ vote on Sept 15 (next Tuesday), gives us just under a =
week
>>>> to drum up a few alternatives
>>>>=20
>>>> dev@ vote on Sept 18 right after the marketing@ vote closes. There =
is
>>>> no more discussion at this point, this is an automatic procedure.
>>>>=20
>>>> PMC starts deciding from Sept 21, right after the dev@ vote and =
we=E2=80=99ll
>>>> try to get this wrapped by Sept 25, so we have a few days to spare,
>>>> and time to prepare materials for the 28th.
>>>>=20
>>>> All aboard?
>>>>=20
>>>> Best
>>>> Jan
>>>> --
>>>>=20
>>>>=20
>>>>> On 29 Aug 2015, at 11:56, Jan Lehnardt <jan@apache.org> wrote:
>>>>>=20
>>>>> (repost in the right thread, sorry about that)
>>>>>=20
>>>>> Thanks for getting this discussion going again, Joan!
>>>>>=20
>>>>> Here is where we discussed this last fall: Thread =E2=80=9CNew =
motto?=E2=80=9D:
>>>>> http://apache.markmail.org/thread/6k6qtc65vtnse5ls (incomplete
>>>>> results, because the MarkMail interface is weird, but should get
>>>>> you the main parts)
>>>>>=20
>>>>> In there, we follow the search for our WHY, which defines our HOW
>>>>> and that in turn defines our WHAT (context
>>>>> http://markmail.org/message/346bxv4v3sq7ofoj)
>>>>>=20
>>>>> Noah summed up our discussion back then
>>>>> (http://markmail.org/message/h2dm233yjuphtufw):
>>>>>=20
>>>>>> WHY -- Getting your data where ever you need it (mobile,
>>>>>> geolocations, cloud, etc)
>>>>>=20
>>>>>> HOW -- Sync protocol (with CouchDB as the reference
>>>>>> implementation)
>>>>>=20
>>>>>> WHAT -- Erlang, MapReduce, CouchDB Query, REST, JSON, JavaScript,
>>>>>> etc., etc.
>>>>>=20
>>>>>=20
>>>>> The slogan we are looking for now is addressing the WHY and the =
WHY
>>>>> only. The HOW and the WHAT also deserve treatment though, but
>>>>> these need to live elsewhere.
>>>>>=20
>>>>> Let=E2=80=99s attempt to organise this a little:
>>>>>=20
>>>>> Project name: Apache CouchDB
>>>>>=20
>>>>> Nickname: CouchDB
>>>>>=20
>>>>> Slogan: Data where you need it. (WHY)
>>>>>=20
>>>>> Mission Statement: Apache CouchDB aims to foster an ecosystem of
>>>>> software that can flexibly share data with each other by defining
>>>>> a universal synchronisation protocol. (HOW)
>>>>>=20
>>>>> Description: CouchDB is the focal point of the Couch Sync Protocol
>>>>> suite which is implemented by an ecosystem of projects that all
>>>>> work in concert to fulfil a universal vision: being able to share
>>>>> and access data where it has the most value, from cross
>>>>> data-center cluster to mobile phones. CouchDB is an
>>>>> Erlang-implementation of the Couch Sync Protocol with a strong
>>>>> focus on reliability, durability and scaling. CouchDB uses HTTP
>>>>> for its API, JSON for documents, and a developer-friendly query
>>>>> language and optionally MapReduce for efficient data retrieval.
>>>>> (WHAT)
>>>>>=20
>>>>> * * *
>>>>>=20
>>>>> Let=E2=80=99s collect variations of this and counter examples, but =
let=E2=80=99s
>>>>> keep the same form:
>>>>> 1. Address the WHY, HOW and WHAT
>>>>> 2. Define: Name, Nickname, Slogan, Mission Statement and
>>>>> Description (we can rename the labels later, for now it is
>>>>> important to get the copy text for the WHY, HOW and WHAT right).
>>>>>=20
>>>>>=20
>>>>> * * *
>>>>>=20
>>>>> FWIW: PouchDB nicked the =E2=80=9CThe database that syncs=E2=80=9D =
from an email of
>>>>> mine on dev@ two years ago, when this was discussed first (and
>>>>> kudos to them for realising it is a great slogan and running with
>>>>> it!). I see no harm in the two projects sharing this, or
>>>>> coordinating, e.g. CouchDB: The database that syncs. PouchDB: The
>>>>> JavaScript database that syncs, or somesuch. (not saying this is a
>>>>> proposal of mine, but if anyone wants to advocate it, I=E2=80=99d =
be happy
>>>>> to listen and hear a proposal).
>>>>>=20
>>>>> * * *
>>>>>=20
>>>>> Thanks!
>>>>> Jan
>>>>> --
>>>>>> On 10 Aug 2015, at 16:06, Joan Touzet <wohali@apache.org> wrote:
>>>>>>=20
>>>>>> Hey everyone,
>>>>>>=20
>>>>>> I don't know where we landed on this discussion last time, but =
I'm
>>>>>> fairly sure we didn't come to any sort of agreement.
>>>>>>=20
>>>>>> Our current tag-line for CouchDB is pretty unwieldy:
>>>>>>=20
>>>>>> "Apache CouchDB is a database that uses JSON for documents,
>>>>>>  JavaScript for MapReduce indexes, and regular HTTP for its
>>>>>>  API"
>>>>>>=20
>>>>>> With the addition of mango, it's also inaccurate. I'm sure we can
>>>>>> do
>>>>>> better!
>>>>>>=20
>>>>>> Previously I remember seeing the suggestion:
>>>>>>=20
>>>>>> "Apache CouchDB: The database that {replicates|syncs}."
>>>>>>=20
>>>>>> I'm finding that really snappy. If you had to pick a single
>>>>>> feature that
>>>>>> CouchDB does better than anyone else, it's the multi-master
>>>>>> replication.
>>>>>> It does leave out a lot of great things we do, though.
>>>>>>=20
>>>>>>=20
>>>>>> Here's the taglines of some of our "competitors":
>>>>>>=20
>>>>>> "The Apache Cassandra database is the right choice when you need
>>>>>> scalability and high availability without compromising
>>>>>> performance."
>>>>>>=20
>>>>>> "Apache HBase=E2=84=A2 is the Hadoop database, a distributed, =
scalable,
>>>>>> big
>>>>>> data store."
>>>>>>=20
>>>>>> "The Apache=E2=84=A2 Hadoop=C2=AE project develops open-source =
software for
>>>>>> reliable,
>>>>>> scalable, distributed computing."
>>>>>>=20
>>>>>> "CouchBase 3.0: A distributed database engineered for =
performance,
>>>>>> scalability, and simplified administration."
>>>>>>=20
>>>>>> "MongoDB: Agility, scalability, performance. Pick three."
>>>>>>=20
>>>>>> "Redis is an open source, BSD licensed, advanced key-value cache
>>>>>> and
>>>>>> store."
>>>>>>=20
>>>>>> "Riak KV is a distributed NoSQL database that is highly =
available,
>>>>>> scalable and easy to operate"
>>>>>>=20
>>>>>> "ElasticSearch: Search & Analyze Data in Real Time"
>>>>>>=20
>>>>>>=20
>>>>>> What other ideas do you have for a tagline for CouchDB? The only
>>>>>> rules
>>>>>> are: one sentence, the shorter the better, and focused on
>>>>>> CouchDB's
>>>>>> unique strength(s).
>>>>>>=20
>>>>>> -Joan
>>>>>>=20
>>>>>>=20
>>>>>> Disclaimer: This is brainstorming only. The discussion may or may
>>>>>> not
>>>>>> lead to a new CouchDB tagline. Please, no negativity.
>>>>>=20
>>>>> --
>>>>> Professional Support for Apache CouchDB:
>>>>> http://www.neighbourhood.ie/couchdb-support/
>>>>>=20
>>>>=20
>>>> --
>>>> Professional Support for Apache CouchDB:
>>>> http://www.neighbourhood.ie/couchdb-support/
>>>>=20
>>>>=20
>>=20
>=20
> --=20
> Professional Support for Apache CouchDB:
> http://www.neighbourhood.ie/couchdb-support/
>=20

--=20
Professional Support for Apache CouchDB:
http://www.neighbourhood.ie/couchdb-support/