You are viewing a plain text version of this content. The canonical link for it is here.
Posted to marketing@couchdb.apache.org by Jan Lehnardt <ja...@apache.org> on 2015/09/09 17:45:40 UTC
Re: Brainstorm: A new CouchDB tag-line?
I’d like to get this wrapped up and I propose a similar process to what we did for the logo:
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.
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@
3. From the vote result on dev@, the PMC then makes a decision on the final set.
It’d be great if we get this rounded up by ApacheCon EU (that’s Sept 28), and because of that, I propose the following schedule:
marketing@ vote on Sept 15 (next Tuesday), gives us just under a week to drum up a few alternatives
dev@ vote on Sept 18 right after the marketing@ vote closes. There is no more discussion at this point, this is an automatic procedure.
PMC starts deciding from Sept 21, right after the dev@ vote and we’ll try to get this wrapped by Sept 25, so we have a few days to spare, and time to prepare materials for the 28th.
All aboard?
Best
Jan
--
> On 29 Aug 2015, at 11:56, Jan Lehnardt <ja...@apache.org> wrote:
>
> (repost in the right thread, sorry about that)
>
> Thanks for getting this discussion going again, Joan!
>
> Here is where we discussed this last fall: Thread “New motto?”: http://apache.markmail.org/thread/6k6qtc65vtnse5ls (incomplete results, because the MarkMail interface is weird, but should get you the main parts)
>
> 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)
>
> Noah summed up our discussion back then (http://markmail.org/message/h2dm233yjuphtufw):
>
>> WHY -- Getting your data where ever you need it (mobile, geolocations, cloud, etc)
>
>> HOW -- Sync protocol (with CouchDB as the reference implementation)
>
>> WHAT -- Erlang, MapReduce, CouchDB Query, REST, JSON, JavaScript, etc., etc.
>
>
> 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.
>
> Let’s attempt to organise this a little:
>
> Project name: Apache CouchDB
>
> Nickname: CouchDB
>
> Slogan: Data where you need it. (WHY)
>
> 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)
>
> 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)
>
> * * *
>
> Let’s collect variations of this and counter examples, but let’s 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).
>
>
> * * *
>
> FWIW: PouchDB nicked the “The database that syncs” 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’d be happy to listen and hear a proposal).
>
> * * *
>
> Thanks!
> Jan
> --
>> On 10 Aug 2015, at 16:06, Joan Touzet <wo...@apache.org> wrote:
>>
>> Hey everyone,
>>
>> 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.
>>
>> Our current tag-line for CouchDB is pretty unwieldy:
>>
>> "Apache CouchDB is a database that uses JSON for documents,
>> JavaScript for MapReduce indexes, and regular HTTP for its API"
>>
>> With the addition of mango, it's also inaccurate. I'm sure we can do
>> better!
>>
>> Previously I remember seeing the suggestion:
>>
>> "Apache CouchDB: The database that {replicates|syncs}."
>>
>> 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.
>>
>>
>> Here's the taglines of some of our "competitors":
>>
>> "The Apache Cassandra database is the right choice when you need
>> scalability and high availability without compromising performance."
>>
>> "Apache HBase™ is the Hadoop database, a distributed, scalable, big
>> data store."
>>
>> "The Apache™ Hadoop® project develops open-source software for reliable,
>> scalable, distributed computing."
>>
>> "CouchBase 3.0: A distributed database engineered for performance,
>> scalability, and simplified administration."
>>
>> "MongoDB: Agility, scalability, performance. Pick three."
>>
>> "Redis is an open source, BSD licensed, advanced key-value cache and
>> store."
>>
>> "Riak KV is a distributed NoSQL database that is highly available,
>> scalable and easy to operate"
>>
>> "ElasticSearch: Search & Analyze Data in Real Time"
>>
>>
>> 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).
>>
>> -Joan
>>
>>
>> Disclaimer: This is brainstorming only. The discussion may or may not
>> lead to a new CouchDB tagline. Please, no negativity.
>
> --
> Professional Support for Apache CouchDB:
> http://www.neighbourhood.ie/couchdb-support/
>
--
Professional Support for Apache CouchDB:
http://www.neighbourhood.ie/couchdb-support/
Re: Brainstorm: A new CouchDB tag-line?
Posted by Jan Lehnardt <ja...@apache.org>.
Sorry for the delay, the vote goes out momentarily.
Best
Jan
--
> On 14 Sep 2015, at 13:56, Jan Lehnardt <ja...@apache.org> wrote:
>
> *nudge* everybody, get your proposals in.
>
> I plan to start a vote on this around this time tomorrow.
>
> Best
> Jan
> --
>
>> On 09 Sep 2015, at 22:00, Johs Ensby <jo...@b2w.com> wrote:
>>
>> WHY Restful freedom
>> HOW Data that sync
>>
>> WHAT
>> 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.
>>
>> Johs:)
>>
>>
>>> On 9. sep. 2015, at 21.02, Joan Touzet <wo...@apache.org> wrote:
>>>
>>> +1
>>>
>>> ----- Original Message -----
>>>> From: "Jan Lehnardt" <ja...@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?
>>>>
>>>> I’d like to get this wrapped up and I propose a similar process to
>>>> what we did for the logo:
>>>>
>>>> 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.
>>>>
>>>> 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@
>>>>
>>>> 3. From the vote result on dev@, the PMC then makes a decision on the
>>>> final set.
>>>>
>>>> It’d be great if we get this rounded up by ApacheCon EU (that’s Sept
>>>> 28), and because of that, I propose the following schedule:
>>>>
>>>> marketing@ vote on Sept 15 (next Tuesday), gives us just under a week
>>>> to drum up a few alternatives
>>>>
>>>> dev@ vote on Sept 18 right after the marketing@ vote closes. There is
>>>> no more discussion at this point, this is an automatic procedure.
>>>>
>>>> PMC starts deciding from Sept 21, right after the dev@ vote and we’ll
>>>> try to get this wrapped by Sept 25, so we have a few days to spare,
>>>> and time to prepare materials for the 28th.
>>>>
>>>> All aboard?
>>>>
>>>> Best
>>>> Jan
>>>> --
>>>>
>>>>
>>>>> On 29 Aug 2015, at 11:56, Jan Lehnardt <ja...@apache.org> wrote:
>>>>>
>>>>> (repost in the right thread, sorry about that)
>>>>>
>>>>> Thanks for getting this discussion going again, Joan!
>>>>>
>>>>> Here is where we discussed this last fall: Thread “New motto?”:
>>>>> http://apache.markmail.org/thread/6k6qtc65vtnse5ls (incomplete
>>>>> results, because the MarkMail interface is weird, but should get
>>>>> you the main parts)
>>>>>
>>>>> 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)
>>>>>
>>>>> Noah summed up our discussion back then
>>>>> (http://markmail.org/message/h2dm233yjuphtufw):
>>>>>
>>>>>> WHY -- Getting your data where ever you need it (mobile,
>>>>>> geolocations, cloud, etc)
>>>>>
>>>>>> HOW -- Sync protocol (with CouchDB as the reference
>>>>>> implementation)
>>>>>
>>>>>> WHAT -- Erlang, MapReduce, CouchDB Query, REST, JSON, JavaScript,
>>>>>> etc., etc.
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>> Let’s attempt to organise this a little:
>>>>>
>>>>> Project name: Apache CouchDB
>>>>>
>>>>> Nickname: CouchDB
>>>>>
>>>>> Slogan: Data where you need it. (WHY)
>>>>>
>>>>> 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)
>>>>>
>>>>> 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)
>>>>>
>>>>> * * *
>>>>>
>>>>> Let’s collect variations of this and counter examples, but let’s
>>>>> 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).
>>>>>
>>>>>
>>>>> * * *
>>>>>
>>>>> FWIW: PouchDB nicked the “The database that syncs” 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’d be happy
>>>>> to listen and hear a proposal).
>>>>>
>>>>> * * *
>>>>>
>>>>> Thanks!
>>>>> Jan
>>>>> --
>>>>>> On 10 Aug 2015, at 16:06, Joan Touzet <wo...@apache.org> wrote:
>>>>>>
>>>>>> Hey everyone,
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> Our current tag-line for CouchDB is pretty unwieldy:
>>>>>>
>>>>>> "Apache CouchDB is a database that uses JSON for documents,
>>>>>> JavaScript for MapReduce indexes, and regular HTTP for its
>>>>>> API"
>>>>>>
>>>>>> With the addition of mango, it's also inaccurate. I'm sure we can
>>>>>> do
>>>>>> better!
>>>>>>
>>>>>> Previously I remember seeing the suggestion:
>>>>>>
>>>>>> "Apache CouchDB: The database that {replicates|syncs}."
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>>
>>>>>> Here's the taglines of some of our "competitors":
>>>>>>
>>>>>> "The Apache Cassandra database is the right choice when you need
>>>>>> scalability and high availability without compromising
>>>>>> performance."
>>>>>>
>>>>>> "Apache HBase™ is the Hadoop database, a distributed, scalable,
>>>>>> big
>>>>>> data store."
>>>>>>
>>>>>> "The Apache™ Hadoop® project develops open-source software for
>>>>>> reliable,
>>>>>> scalable, distributed computing."
>>>>>>
>>>>>> "CouchBase 3.0: A distributed database engineered for performance,
>>>>>> scalability, and simplified administration."
>>>>>>
>>>>>> "MongoDB: Agility, scalability, performance. Pick three."
>>>>>>
>>>>>> "Redis is an open source, BSD licensed, advanced key-value cache
>>>>>> and
>>>>>> store."
>>>>>>
>>>>>> "Riak KV is a distributed NoSQL database that is highly available,
>>>>>> scalable and easy to operate"
>>>>>>
>>>>>> "ElasticSearch: Search & Analyze Data in Real Time"
>>>>>>
>>>>>>
>>>>>> 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).
>>>>>>
>>>>>> -Joan
>>>>>>
>>>>>>
>>>>>> Disclaimer: This is brainstorming only. The discussion may or may
>>>>>> not
>>>>>> lead to a new CouchDB tagline. Please, no negativity.
>>>>>
>>>>> --
>>>>> Professional Support for Apache CouchDB:
>>>>> http://www.neighbourhood.ie/couchdb-support/
>>>>>
>>>>
>>>> --
>>>> Professional Support for Apache CouchDB:
>>>> http://www.neighbourhood.ie/couchdb-support/
>>>>
>>>>
>>
>
> --
> Professional Support for Apache CouchDB:
> http://www.neighbourhood.ie/couchdb-support/
>
--
Professional Support for Apache CouchDB:
http://www.neighbourhood.ie/couchdb-support/
Re: Brainstorm: A new CouchDB tag-line?
Posted by Jan Lehnardt <ja...@apache.org>.
*nudge* everybody, get your proposals in.
I plan to start a vote on this around this time tomorrow.
Best
Jan
--
> On 09 Sep 2015, at 22:00, Johs Ensby <jo...@b2w.com> wrote:
>
> WHY Restful freedom
> HOW Data that sync
>
> WHAT
> 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.
>
> Johs:)
>
>
>> On 9. sep. 2015, at 21.02, Joan Touzet <wo...@apache.org> wrote:
>>
>> +1
>>
>> ----- Original Message -----
>>> From: "Jan Lehnardt" <ja...@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?
>>>
>>> I’d like to get this wrapped up and I propose a similar process to
>>> what we did for the logo:
>>>
>>> 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.
>>>
>>> 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@
>>>
>>> 3. From the vote result on dev@, the PMC then makes a decision on the
>>> final set.
>>>
>>> It’d be great if we get this rounded up by ApacheCon EU (that’s Sept
>>> 28), and because of that, I propose the following schedule:
>>>
>>> marketing@ vote on Sept 15 (next Tuesday), gives us just under a week
>>> to drum up a few alternatives
>>>
>>> dev@ vote on Sept 18 right after the marketing@ vote closes. There is
>>> no more discussion at this point, this is an automatic procedure.
>>>
>>> PMC starts deciding from Sept 21, right after the dev@ vote and we’ll
>>> try to get this wrapped by Sept 25, so we have a few days to spare,
>>> and time to prepare materials for the 28th.
>>>
>>> All aboard?
>>>
>>> Best
>>> Jan
>>> --
>>>
>>>
>>>> On 29 Aug 2015, at 11:56, Jan Lehnardt <ja...@apache.org> wrote:
>>>>
>>>> (repost in the right thread, sorry about that)
>>>>
>>>> Thanks for getting this discussion going again, Joan!
>>>>
>>>> Here is where we discussed this last fall: Thread “New motto?”:
>>>> http://apache.markmail.org/thread/6k6qtc65vtnse5ls (incomplete
>>>> results, because the MarkMail interface is weird, but should get
>>>> you the main parts)
>>>>
>>>> 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)
>>>>
>>>> Noah summed up our discussion back then
>>>> (http://markmail.org/message/h2dm233yjuphtufw):
>>>>
>>>>> WHY -- Getting your data where ever you need it (mobile,
>>>>> geolocations, cloud, etc)
>>>>
>>>>> HOW -- Sync protocol (with CouchDB as the reference
>>>>> implementation)
>>>>
>>>>> WHAT -- Erlang, MapReduce, CouchDB Query, REST, JSON, JavaScript,
>>>>> etc., etc.
>>>>
>>>>
>>>> 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.
>>>>
>>>> Let’s attempt to organise this a little:
>>>>
>>>> Project name: Apache CouchDB
>>>>
>>>> Nickname: CouchDB
>>>>
>>>> Slogan: Data where you need it. (WHY)
>>>>
>>>> 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)
>>>>
>>>> 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)
>>>>
>>>> * * *
>>>>
>>>> Let’s collect variations of this and counter examples, but let’s
>>>> 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).
>>>>
>>>>
>>>> * * *
>>>>
>>>> FWIW: PouchDB nicked the “The database that syncs” 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’d be happy
>>>> to listen and hear a proposal).
>>>>
>>>> * * *
>>>>
>>>> Thanks!
>>>> Jan
>>>> --
>>>>> On 10 Aug 2015, at 16:06, Joan Touzet <wo...@apache.org> wrote:
>>>>>
>>>>> Hey everyone,
>>>>>
>>>>> 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.
>>>>>
>>>>> Our current tag-line for CouchDB is pretty unwieldy:
>>>>>
>>>>> "Apache CouchDB is a database that uses JSON for documents,
>>>>> JavaScript for MapReduce indexes, and regular HTTP for its
>>>>> API"
>>>>>
>>>>> With the addition of mango, it's also inaccurate. I'm sure we can
>>>>> do
>>>>> better!
>>>>>
>>>>> Previously I remember seeing the suggestion:
>>>>>
>>>>> "Apache CouchDB: The database that {replicates|syncs}."
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> Here's the taglines of some of our "competitors":
>>>>>
>>>>> "The Apache Cassandra database is the right choice when you need
>>>>> scalability and high availability without compromising
>>>>> performance."
>>>>>
>>>>> "Apache HBase™ is the Hadoop database, a distributed, scalable,
>>>>> big
>>>>> data store."
>>>>>
>>>>> "The Apache™ Hadoop® project develops open-source software for
>>>>> reliable,
>>>>> scalable, distributed computing."
>>>>>
>>>>> "CouchBase 3.0: A distributed database engineered for performance,
>>>>> scalability, and simplified administration."
>>>>>
>>>>> "MongoDB: Agility, scalability, performance. Pick three."
>>>>>
>>>>> "Redis is an open source, BSD licensed, advanced key-value cache
>>>>> and
>>>>> store."
>>>>>
>>>>> "Riak KV is a distributed NoSQL database that is highly available,
>>>>> scalable and easy to operate"
>>>>>
>>>>> "ElasticSearch: Search & Analyze Data in Real Time"
>>>>>
>>>>>
>>>>> 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).
>>>>>
>>>>> -Joan
>>>>>
>>>>>
>>>>> Disclaimer: This is brainstorming only. The discussion may or may
>>>>> not
>>>>> lead to a new CouchDB tagline. Please, no negativity.
>>>>
>>>> --
>>>> Professional Support for Apache CouchDB:
>>>> http://www.neighbourhood.ie/couchdb-support/
>>>>
>>>
>>> --
>>> Professional Support for Apache CouchDB:
>>> http://www.neighbourhood.ie/couchdb-support/
>>>
>>>
>
--
Professional Support for Apache CouchDB:
http://www.neighbourhood.ie/couchdb-support/
Re: Brainstorm: A new CouchDB tag-line?
Posted by Johs Ensby <jo...@b2w.com>.
WHY Restful freedom
HOW Data that sync
WHAT
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.
Johs:)
> On 9. sep. 2015, at 21.02, Joan Touzet <wo...@apache.org> wrote:
>
> +1
>
> ----- Original Message -----
>> From: "Jan Lehnardt" <ja...@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?
>>
>> I’d like to get this wrapped up and I propose a similar process to
>> what we did for the logo:
>>
>> 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.
>>
>> 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@
>>
>> 3. From the vote result on dev@, the PMC then makes a decision on the
>> final set.
>>
>> It’d be great if we get this rounded up by ApacheCon EU (that’s Sept
>> 28), and because of that, I propose the following schedule:
>>
>> marketing@ vote on Sept 15 (next Tuesday), gives us just under a week
>> to drum up a few alternatives
>>
>> dev@ vote on Sept 18 right after the marketing@ vote closes. There is
>> no more discussion at this point, this is an automatic procedure.
>>
>> PMC starts deciding from Sept 21, right after the dev@ vote and we’ll
>> try to get this wrapped by Sept 25, so we have a few days to spare,
>> and time to prepare materials for the 28th.
>>
>> All aboard?
>>
>> Best
>> Jan
>> --
>>
>>
>>> On 29 Aug 2015, at 11:56, Jan Lehnardt <ja...@apache.org> wrote:
>>>
>>> (repost in the right thread, sorry about that)
>>>
>>> Thanks for getting this discussion going again, Joan!
>>>
>>> Here is where we discussed this last fall: Thread “New motto?”:
>>> http://apache.markmail.org/thread/6k6qtc65vtnse5ls (incomplete
>>> results, because the MarkMail interface is weird, but should get
>>> you the main parts)
>>>
>>> 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)
>>>
>>> Noah summed up our discussion back then
>>> (http://markmail.org/message/h2dm233yjuphtufw):
>>>
>>>> WHY -- Getting your data where ever you need it (mobile,
>>>> geolocations, cloud, etc)
>>>
>>>> HOW -- Sync protocol (with CouchDB as the reference
>>>> implementation)
>>>
>>>> WHAT -- Erlang, MapReduce, CouchDB Query, REST, JSON, JavaScript,
>>>> etc., etc.
>>>
>>>
>>> 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.
>>>
>>> Let’s attempt to organise this a little:
>>>
>>> Project name: Apache CouchDB
>>>
>>> Nickname: CouchDB
>>>
>>> Slogan: Data where you need it. (WHY)
>>>
>>> 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)
>>>
>>> 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)
>>>
>>> * * *
>>>
>>> Let’s collect variations of this and counter examples, but let’s
>>> 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).
>>>
>>>
>>> * * *
>>>
>>> FWIW: PouchDB nicked the “The database that syncs” 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’d be happy
>>> to listen and hear a proposal).
>>>
>>> * * *
>>>
>>> Thanks!
>>> Jan
>>> --
>>>> On 10 Aug 2015, at 16:06, Joan Touzet <wo...@apache.org> wrote:
>>>>
>>>> Hey everyone,
>>>>
>>>> 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.
>>>>
>>>> Our current tag-line for CouchDB is pretty unwieldy:
>>>>
>>>> "Apache CouchDB is a database that uses JSON for documents,
>>>> JavaScript for MapReduce indexes, and regular HTTP for its
>>>> API"
>>>>
>>>> With the addition of mango, it's also inaccurate. I'm sure we can
>>>> do
>>>> better!
>>>>
>>>> Previously I remember seeing the suggestion:
>>>>
>>>> "Apache CouchDB: The database that {replicates|syncs}."
>>>>
>>>> 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.
>>>>
>>>>
>>>> Here's the taglines of some of our "competitors":
>>>>
>>>> "The Apache Cassandra database is the right choice when you need
>>>> scalability and high availability without compromising
>>>> performance."
>>>>
>>>> "Apache HBase™ is the Hadoop database, a distributed, scalable,
>>>> big
>>>> data store."
>>>>
>>>> "The Apache™ Hadoop® project develops open-source software for
>>>> reliable,
>>>> scalable, distributed computing."
>>>>
>>>> "CouchBase 3.0: A distributed database engineered for performance,
>>>> scalability, and simplified administration."
>>>>
>>>> "MongoDB: Agility, scalability, performance. Pick three."
>>>>
>>>> "Redis is an open source, BSD licensed, advanced key-value cache
>>>> and
>>>> store."
>>>>
>>>> "Riak KV is a distributed NoSQL database that is highly available,
>>>> scalable and easy to operate"
>>>>
>>>> "ElasticSearch: Search & Analyze Data in Real Time"
>>>>
>>>>
>>>> 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).
>>>>
>>>> -Joan
>>>>
>>>>
>>>> Disclaimer: This is brainstorming only. The discussion may or may
>>>> not
>>>> lead to a new CouchDB tagline. Please, no negativity.
>>>
>>> --
>>> Professional Support for Apache CouchDB:
>>> http://www.neighbourhood.ie/couchdb-support/
>>>
>>
>> --
>> Professional Support for Apache CouchDB:
>> http://www.neighbourhood.ie/couchdb-support/
>>
>>
Re: Brainstorm: A new CouchDB tag-line?
Posted by Joan Touzet <wo...@apache.org>.
+1
----- Original Message -----
> From: "Jan Lehnardt" <ja...@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?
>
> I’d like to get this wrapped up and I propose a similar process to
> what we did for the logo:
>
> 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.
>
> 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@
>
> 3. From the vote result on dev@, the PMC then makes a decision on the
> final set.
>
> It’d be great if we get this rounded up by ApacheCon EU (that’s Sept
> 28), and because of that, I propose the following schedule:
>
> marketing@ vote on Sept 15 (next Tuesday), gives us just under a week
> to drum up a few alternatives
>
> dev@ vote on Sept 18 right after the marketing@ vote closes. There is
> no more discussion at this point, this is an automatic procedure.
>
> PMC starts deciding from Sept 21, right after the dev@ vote and we’ll
> try to get this wrapped by Sept 25, so we have a few days to spare,
> and time to prepare materials for the 28th.
>
> All aboard?
>
> Best
> Jan
> --
>
>
> > On 29 Aug 2015, at 11:56, Jan Lehnardt <ja...@apache.org> wrote:
> >
> > (repost in the right thread, sorry about that)
> >
> > Thanks for getting this discussion going again, Joan!
> >
> > Here is where we discussed this last fall: Thread “New motto?”:
> > http://apache.markmail.org/thread/6k6qtc65vtnse5ls (incomplete
> > results, because the MarkMail interface is weird, but should get
> > you the main parts)
> >
> > 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)
> >
> > Noah summed up our discussion back then
> > (http://markmail.org/message/h2dm233yjuphtufw):
> >
> >> WHY -- Getting your data where ever you need it (mobile,
> >> geolocations, cloud, etc)
> >
> >> HOW -- Sync protocol (with CouchDB as the reference
> >> implementation)
> >
> >> WHAT -- Erlang, MapReduce, CouchDB Query, REST, JSON, JavaScript,
> >> etc., etc.
> >
> >
> > 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.
> >
> > Let’s attempt to organise this a little:
> >
> > Project name: Apache CouchDB
> >
> > Nickname: CouchDB
> >
> > Slogan: Data where you need it. (WHY)
> >
> > 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)
> >
> > 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)
> >
> > * * *
> >
> > Let’s collect variations of this and counter examples, but let’s
> > 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).
> >
> >
> > * * *
> >
> > FWIW: PouchDB nicked the “The database that syncs” 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’d be happy
> > to listen and hear a proposal).
> >
> > * * *
> >
> > Thanks!
> > Jan
> > --
> >> On 10 Aug 2015, at 16:06, Joan Touzet <wo...@apache.org> wrote:
> >>
> >> Hey everyone,
> >>
> >> 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.
> >>
> >> Our current tag-line for CouchDB is pretty unwieldy:
> >>
> >> "Apache CouchDB is a database that uses JSON for documents,
> >> JavaScript for MapReduce indexes, and regular HTTP for its
> >> API"
> >>
> >> With the addition of mango, it's also inaccurate. I'm sure we can
> >> do
> >> better!
> >>
> >> Previously I remember seeing the suggestion:
> >>
> >> "Apache CouchDB: The database that {replicates|syncs}."
> >>
> >> 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.
> >>
> >>
> >> Here's the taglines of some of our "competitors":
> >>
> >> "The Apache Cassandra database is the right choice when you need
> >> scalability and high availability without compromising
> >> performance."
> >>
> >> "Apache HBase™ is the Hadoop database, a distributed, scalable,
> >> big
> >> data store."
> >>
> >> "The Apache™ Hadoop® project develops open-source software for
> >> reliable,
> >> scalable, distributed computing."
> >>
> >> "CouchBase 3.0: A distributed database engineered for performance,
> >> scalability, and simplified administration."
> >>
> >> "MongoDB: Agility, scalability, performance. Pick three."
> >>
> >> "Redis is an open source, BSD licensed, advanced key-value cache
> >> and
> >> store."
> >>
> >> "Riak KV is a distributed NoSQL database that is highly available,
> >> scalable and easy to operate"
> >>
> >> "ElasticSearch: Search & Analyze Data in Real Time"
> >>
> >>
> >> 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).
> >>
> >> -Joan
> >>
> >>
> >> Disclaimer: This is brainstorming only. The discussion may or may
> >> not
> >> lead to a new CouchDB tagline. Please, no negativity.
> >
> > --
> > Professional Support for Apache CouchDB:
> > http://www.neighbourhood.ie/couchdb-support/
> >
>
> --
> Professional Support for Apache CouchDB:
> http://www.neighbourhood.ie/couchdb-support/
>
>