The "Time to Relax" is not only tagline, but also the goal to aim for. If you are not relaxed with CouchDB, probably, you just doing something wrong or should file an issue about (: -- ,,,^..^,,,
On Tue, Oct 28, 2014 at 6:26 PM, Eric B <[email protected]> wrote: > On Tue, Oct 28, 2014 at 11:03 AM, Joan Touzet <[email protected]> wrote: > >> A minority of individuals suggested that it may be time to change >> the logo, the tagline and even the project name for various reasons. >> If we're considering any of these steps, now would be the time to >> figure that out -- prior to the impending 2.0 beta and release. >> >> I'd like to steer discussion towards these points and away from >> the topic of logo acceptability -- it's become clear to me that >> there is no further useful discussion possible on that topic. >> > > As a fairly newcomer to CouchDB, I'd like to contribute by giving my > viewpoint and insight into the discussion to date. To be clear, I am not > personally offended by the logo. But to be entirely fair (and hopefully > no one will take offense at this), I don't particularly care too much about > it either. I don't make technical decisions based on graphics, but rather > what the product provides. > > To that extent, I chose CouchDB due to its feature set, community, and > platform availability. I wanted something that I could use in a > distributed manner without too much hassles. CouchDB offered me a solution > for this. The fact that the tag line was "CouchDB and Relax" really meant > nothing to me either. > > Coming from a RDBMS background, already moving to NoSQL has its challenges > in design and approach. Using CouchDB as a persistence engine (and not an > actual web-server) to a Java application means that it's HTTP API doesn't > really impact me either (all access is wrapped in a library). > > So from my perspective, the tagline "...Relax..." isn't really even > accurate. If anything, CouchDB has less "standard" support in Java (ie: > no Spring libraries, etc) and makes it less "relaxing" than something like > MongoDB which has a big Spring following. > > If the goal is to rethink the name/logo/tagline, then perhaps a more > appropriate approach would be to target its feature set: (random examples > purely to illustrate my point): "Easy NoSQL for the web" or "Distributed > NoSQL made simple" or something more directed. > > But the primary goal, I believe, is to first decide whether anything > _needs_ to be changed. As others have already mentioned, something will > always offend someone somewhere, in some different language or culture. > That being said, the question should rather be if the product/community has > outgrown the tagline, and if so, what a new tagline/name should be. > > Thanks, > > Eric
