couchdb-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giovanni Lenzi <>
Date Wed, 16 Sep 2015 09:56:58 GMT
#1: 0
#2: 0

I think that speaking of couchdb as a data container only, doesn't capture
the essence of couchdb... probably it was at version 0.1, but not at
current stage. Also it isn't a distinguishing feature.

> * what went wrong?  * how and where do we collect ideas about a slogan?
Both slogan don't capture what CouchDB is for all of us. Everyone
personally cares different different features of CouchDB.  I remember there
were two different positions in the past:
1. couchdb is a database server with the best replication protocol around
2. couchdb is the above but with a lot of distinguishing features, that
others simply don't have. As Harald said: "* is a Webserver * an
Web-App-Engine * a HTTP/HTTPS speaking Any-Device- and * a Any-File
Replicator", but maybe even more..

What went wrong is that we are still stuck in this dilemma. I like #2 and I
personally think it is just an enlarged view of #1. This means it should
theorically have consensus of all, but unfortunately this is not the case.
Just wondering: could we have a vote on these two sentences before
proceeding with the slogan?

For the Slogan voting process:

> Let the web site description be the WHAT for now

Agree with Alexander and Johs that current description suits very well for
the WHAT, because it summarize well all CouchDB features.

>Seems that ol consisting only of slogans can be very compact, well
>readable, easy to vote and can attract more attention.

Agree 100% with ermouth. There were some slogan options in the past, why
not adding them to this list, vote for the WHY and then find a HOW for
that? Could be much more easy than finding the WHY/HOW/WHAT packaged


2015-09-16 9:56 GMT+02:00 Andy Wenk <>:

> Hi all,
> I suggest to stop the vote at this pint because obviously
> * we do not seem to get any positiv consensus
> * more ideas have arisen and people want to show them
> I am not sure why this happens because there was a very long discussion
> about the slogan. So I have the feeling, we have done sth. wrong. Before we
> start again, we should clarify these points in my opinion:
> * what went wrong?
> * how and where do we collect ideas about a slogan?
> * should we create a simple template which info we need? I think this
> already there in Jan's initial email. Imo this should be a form where
> everybody fills in his ideas.
> * how do we discuss these ideas - I suggest NOT on the ML (I know that this
> might break rules but if it doesn't work ... ?)
> * what is the schedule? As we had along a thread already, I suggest to not
> schedule it longer than two weeks
> I am a bit confused why this vote is going in this direction. To say it
> clearly: what did we discuss if most of the proposals are voted with -1?
> But on the other hand, this is a community process and I am happy to learn
> from it ("there are no errors - there is only experience we made what helps
> us to learn")
> What do you think?
> Jan - thanks a lot for starting the vote. You did this with the best
> intentions!
> All the best
> Andy
> On 16 September 2015 at 08:38, Johs Ensby <> wrote:
> > Hi,
> > I think using the present official description is a good idea, use this
> as
> > the briefing then try and get more proposals on the slogan/mission
> > > On 16. sep. 2015, at 07.28, Alexander Shorin <> wrote:
> > >
> > > CouchDB is a database that completely embraces the web. Store your
> > > data with JSON documents. Access your documents and query your indexes
> > > with your web browser, via HTTP. Index, combine, and transform your
> > > documents with JavaScript. CouchDB works well with modern web and
> > > mobile apps. You can even serve web apps directly out of CouchDB. And
> > > you can distribute your data, or your apps, efficiently using
> > > CouchDB’s incremental replication. CouchDB supports master-master
> > > setups with automatic conflict detection.
> > >
> > > P.S. I'm not sure how it should be, but for me Mission should be
> > > actionless statement. Mission is something you aimed to reach, it's a
> > > goal, the holy grail. "Data that sync" is not a mission, it's a
> > > feature and even incorrect because data itself cannot sync (;
> > I agree on this
> >
> > 'Data that sync' is at best a slogan candidate assuming that the data is
> > what the target group care about and that the syncing is the key
> > differentiator.
> > Mission need to more like a raison d'etre
> > The "what" description will explain and inform, and the one above is good
> >
> > A comment on how hard it seems to agree on any of this...
> >
> > When you position a solution that does not fit into conventional
> > categories, the quest is really about pinpointing what is different,
> using
> > existing terms and concepts.
> > In branding this is the classic dilemma,
> >
> > identity is about belonging and uniqueness at the same time;
> > you need to reference what is in people's mind already to position
> > something as new and unique.
> >
> > If people cannot place it in between what is already in their head you
> > have no hook, if it fits into a well established category it will be
> > another grey mouse, just smaller. Both ways you loose.
> > A technique used in positioning is triangulation, you pick two well known
> > "fix points" and use them to explain your position.
> > Company C can position itself by comparing itself to company A and B, if
> > both are very good alternatives and thus convey, "we are as good as A and
> > B, but we are different, come have a look."
> >
> > If there is a new round on the slogan quest, I would suggest the
> following
> > pre-round:
> > Let the web site description be the WHAT for now
> > Discuss what 2 words need to be in the slogan or mission to connect
> > CouchDB to well established and valuable concepts.
> >
> > Johs
> >
> >
> --
> Andy Wenk
> Hamburg - Germany
> RockIt!
> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588

Giovanni Lenzi
Smileupps Cloud App Store

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message