couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From roger.moff...@gmail.com
Subject Re: Couchbase trademark issues
Date Tue, 13 Mar 2012 14:12:50 GMT
I know I kicked this all off on dev a few weeks ago so I'd just like to say
that from my perspective, as a developer using the product in production
systems and trying to sell it to other clients as a suitable technology to
use, Robert has it spot on.

Roger


On 13 March 2012 13:52, Robert Newson <rnewson@apache.org> wrote:

> I don't believe any CouchDB committer or PMC member has any interest
> in changing the project name.
>
> I personally feel, as you do, that it's the other products that must
> clearly distinguish themselves from CouchDB. The company and product
> called "Couchbase" clearly confuses the community, who reasonably, but
> erroneously, believe that it's related to CouchDB (the truth, now, is
> that couchdb is an important but internal component). Sponsoring the
> "CouchConf" conferences which talks about "Couch NoSQL technology" but
> also "the Couchbase technology" is similarly confusing, especially as
> "CouchConf"'s in the past were about Apache CouchDB and things
> compatible or complementary to it.
>
> For my part, the ideal solution would be for Couchbase to rename its
> product and conferences to not imply that they are about CouchDB, to
> me that means not using the word 'couch'. I understand that the
> trademark we hold is on 'Apache CouchDB' and that we cannot assert any
> rights over the word 'couch', but I don't think anyone can deny that
> confusion caused is real. Since the Couchbase product is not CouchDB
> compatible it's surprising that it hasn't been rebranded for marketing
> reasons already.
>
> B.
>
> On 13 March 2012 04:01, Shane Curcuru <asf@shanecurcuru.org> wrote:
> > (Whoops! Apologies for mixed up subjects and poor threading; I'm not on
> > dev@)
> >
> > I just wanted to add one other comment about this previous note:
> >
> > James Hayton wrote on Feb 20, 2012:
> >>
> >> Maybe a crazy idea, but since the end result of any legal stuff would
> >> be somebody changing the name of something, why doesn't Apache
> >> CouchDB just re brand itself? I mean we need a website makeover,
> >> etc... Why don't we just ditch the name and come up with something
> >> better with a new vision, new leadership, etc... Lets put a few
> >> features in that people have been asking for, include the big couch
> >> code (clustering), create a new website and call it something
> >> different. (CouchDB 2.0 Becomes AwesomeDB lol)
> >>
> >> I understand that alot of people have quite a bit invested in the
> >> name CouchDB, at this may not be something realistic, but this just
> >> seems like at least another option we should discuss.
> >>
> >> Just my .02.
> >>
> >> James
> >
> >
> > If the bulk of the Apache CouchDB PMC truly wanted to consider a rename
> (and
> > discussed and [VOTE]d on the matter, then we'd certainly help that to
> > happen.  The PMC *is* who gets to decide the project direction.
> >
> > But I'm confident that's *not* the case, since several folks have spoken
> out
> > against it.  I personally think it would be a really bad idea to change
> the
> > CouchDB name - especially since CouchDB is arguably the first project
> that
> > gave such brand recognition to the "Couch" name in the noSQL database
> arena.
> >
> > In most trademark issues, I'd think more people would ask why the
> > *follow-on* products don't change their names, rather than the original
> > product.  But in this case, I'm hoping that the pain of renaming is not
> > necessary, and we can reduce user confusion by both improving our own
> story,
> > as well as asking other Couch-named products to better differentiate
> > themselves and better give us - this PMC, the committers, and the ASF -
> the
> > credit we deserve for building and shipping Apache CouchDB itself in the
> > first place.
> >
> > - Shane
> >
>

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