> On 30 Oct 2014, at 17:33 , Noah Slater <nsla...@apache.org> wrote: > > The confusion with Couchbase is large, widespread, and shows no signs > of resolving itself any time soon. This issue is constantly coming up > on social media, in person, and so on.
Because of the logo? I hardly think so. Best Jan -- > > On 30 October 2014 17:04, Andy Wenk <andyw...@apache.org> wrote: >> On 30 October 2014 16:47, Noah Slater <nsla...@apache.org> wrote: >> >>> Clear up massive brand confusion with Couchbase, basically. >>> >> >> I am not sure how big this special issue is because I clearly see the >> situation from CouchDB. If we have a look to the people on the ML who think >> it's Couchbase, that's very minimal ... I would prefer to keep the name and >> clarify the situation as often as possible >> >> >> >> >>> >>> On 30 October 2014 16:35, Andy Wenk <andyw...@apache.org> wrote: >>>> sure - IF we want to rename then with 2.0. But before I give my whatever >>>> vote, I would like to know which advantages you expect to get with a >>> rename >>>> .... as of now - I can only think of negative aspects ... >>>> >>>> On 30 October 2014 16:08, Jason Smith <jason.h.sm...@gmail.com> wrote: >>>> >>>>> Love it. Get away from the WhateverDB thing. Just stake out an arbitrary >>>>> mark from which we build clear, unambiguous IP. >>>>> >>>>> My proposal (as long as we are brainstorming names): >>>>> >>>>> Eight Ball >>>>> >>>>> Tagline: Whatever you do. Don't get more eight ball! >>>>> >>>>> More seriously, yes, a name change has lots of problems. But it is worth >>>>> re-considering Noah's point that now is the best time to do it, if it >>> is to >>>>> be done. >>>>> >>>>> On Thu, Oct 30, 2014 at 10:02 PM, Noah Slater <nsla...@apache.org> >>> wrote: >>>>> >>>>>> I've been wanting to rename it SleepyDB for a while now. (cf. Max >>>>>> Ogden's SLEEP protocol.) >>>>>> >>>>>> On 30 October 2014 11:43, Kevin Coombes <kevin.r.coom...@gmail.com> >>>>> wrote: >>>>>>> Definitely -1 on changing the name. It's already "cooked" into >>>>> everything >>>>>>> associated with the project. There are links (and hard copy >>> references) >>>>>> to >>>>>>> the name and the web site(s) all over the place. How long do you >>> want >>>>> to >>>>>> be >>>>>>> forced to maintain DNS or HTTP entries to forward users from the >>>>> current >>>>>>> names to whatever you might pick for new ones? >>>>>>> >>>>>>> I would be perfectly happy to see a new logo however. And the last >>>>> time I >>>>>>> looked, there were a lot more colors than just red or blue.... >>>>>>> >>>>>>> Kevin >>>>>>> On Oct 30, 2014 6:11 AM, "Brad Noble" <br...@us.ibm.com> wrote: >>>>>>> >>>>>>>> *SyncDB* >>>>>>>> The database that syncs. >>>>>>>> >>>>>>>> Logo would embody that idea. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> [image: Inactive hide details for Jason Smith ---10/30/2014 >>> 04:40:26 >>>>>>>> AM---On Thu, Oct 30, 2014 at 12:52 AM, Noah Slater <nslater@apache >>>>>> ]Jason >>>>>>>> Smith ---10/30/2014 04:40:26 AM---On Thu, Oct 30, 2014 at 12:52 AM, >>>>> Noah >>>>>>>> Slater <nsla...@apache.org> wrote: > Blue is nice. :) But the >>>>>>>> >>>>>>>> From: Jason Smith <jason.h.sm...@gmail.com> >>>>>>>> To: "dev@couchdb.apache.org" <dev@couchdb.apache.org> >>>>>>>> Date: 10/30/2014 04:40 AM >>>>>>>> Subject: Re: [DISCUSS] Improved CouchDB logo >>>>>>>> ------------------------------ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Oct 30, 2014 at 12:52 AM, Noah Slater <nsla...@apache.org> >>>>>> wrote: >>>>>>>> >>>>>>>>> Blue is nice. :) But then that tempts me to change the name too. >>> I >>>>>>>>> mean, if we're ever going to do this, now is the time. It's >>>>> important >>>>>>>>> to note though that we have a very STRONG brand, and changing it >>> in >>>>> a >>>>>>>>> big will be expensive. >>>>>>>>> >>>>>>>> >>>>>>>> Change the name! Change the name! >>>>>>>> >>>>>>>> Like all transitions, it seems scary. But once it's done we will >>> all >>>>>> wonder >>>>>>>> what we were so worried about. >>>>>>>> >>>>>>>> The brand is strong, but the question is, how much of that strength >>>>> can >>>>>> we >>>>>>>> keep, and how much do we lose. >>>>>>>> >>>>>>>> I think we will keep nearly all of it, plus we will get tons of >>>>>> attention >>>>>>>> with a 2.0 release and name change. And as if that already isn't >>>>>> enough, we >>>>>>>> get the opportunity to walk away from a ton of branding baggage and >>>>>>>> trademark problems. >>>>>>>> >>>>>>>> Change the name! >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Noah Slater >>>>>> https://twitter.com/nslater >>>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Andy Wenk >>>> Hamburg - Germany >>>> RockIt! >>>> >>>> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 >>>> >>>> https://people.apache.org/keys/committer/andywenk.asc >>> >>> >>> >>> -- >>> Noah Slater >>> https://twitter.com/nslater >>> >> >> >> >> -- >> Andy Wenk >> Hamburg - Germany >> RockIt! >> >> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 >> >> https://people.apache.org/keys/committer/andywenk.asc > > > > -- > Noah Slater > https://twitter.com/nslater
