Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D4C409875 for ; Mon, 20 Feb 2012 11:54:52 +0000 (UTC) Received: (qmail 30278 invoked by uid 500); 20 Feb 2012 11:54:52 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 30242 invoked by uid 500); 20 Feb 2012 11:54:52 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 30232 invoked by uid 99); 20 Feb 2012 11:54:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Feb 2012 11:54:52 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rurd4me@gmail.com designates 209.85.215.180 as permitted sender) Received: from [209.85.215.180] (HELO mail-ey0-f180.google.com) (209.85.215.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Feb 2012 11:54:46 +0000 Received: by eaad14 with SMTP id d14so2239375eaa.11 for ; Mon, 20 Feb 2012 03:54:25 -0800 (PST) Received-SPF: pass (google.com: domain of rurd4me@gmail.com designates 10.14.126.68 as permitted sender) client-ip=10.14.126.68; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rurd4me@gmail.com designates 10.14.126.68 as permitted sender) smtp.mail=rurd4me@gmail.com; dkim=pass header.i=rurd4me@gmail.com Received: from mr.google.com ([10.14.126.68]) by 10.14.126.68 with SMTP id a44mr10497190eei.101.1329738865455 (num_hops = 1); Mon, 20 Feb 2012 03:54:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=NqtasV71cMrOLWZIBF87wxEyR2M/eP8rRfX1pAEmums=; b=VBU87A4v+RQGyBgInnlXW1LRQ0zAyZv5dtd6Jidwx2josgqC42pcVRvOKi/sRNf1nv QLQZ/BiycF1tnIxhy4PaDI4l8jTMvkl1Bp/a7e6blfBACEKv1g9u7/WjdE6OlTKRNnEf R0AqTme7A8UTbefP9/IPoF9wvOYt51kWENtsM= Received: by 10.14.126.68 with SMTP id a44mr8349394eei.101.1329738864151; Mon, 20 Feb 2012 03:54:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.202.2 with HTTP; Mon, 20 Feb 2012 03:54:04 -0800 (PST) In-Reply-To: References: From: Jonathan Porta Date: Mon, 20 Feb 2012 04:54:04 -0700 Message-ID: Subject: Re: Couchbase trademark issues To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 I know that I am new around here, but, I will still hand out my opinion, which is not legal advice. :) CouchDB is a brand, just like Apple, Google and countless others. If you a person is involved with the project, it is likely that the branding is not going to strongly influence their decisions to use or not use the product. If, however, a person lacks any pre-existing relationship with a brand, that individual is going to be greatly influenced by the presence of similar/confusing brands in the marketplace. Arguably, this causes immeasurable harm to a brand's image as well as it's adoption in the community. Great software like CouchDB exists to be shared and adopted by others. Anything that, intentionally or unintentionally, limits those abilities is quite harmful to the project. It seems like Couchbase is eliminating some of the confusion by consolidating their product line. I would be interested to see what legal has to say about it. It would also be a good idea to see what can be done in conjunction with Couchbase to help eliminate these issues. They publicly acknowledged the confusion [1], so, they may be willing to work on a solution. [1] http://blog.couchbase.com/couchbase-2011-year-review Jonathan Porta On Mon, Feb 20, 2012 at 4:19 AM, Noah Slater wrote: > On Mon, Feb 20, 2012 at 10:54 AM, Dirkjan Ochtman wrote: > >> +1, but we/you should probably try to be non-confrontational about it. >> > > Just to clarify, based on this, and some off-list feedback. I'm not asking > for legal advice, that's what the legal list is for. They very well may > turn around and say that we have not a leg to stand on. > > I was asking what other people feel about the issue at hand. There is > obviously an issue. But how important is it and what should we do about it? > Is it a short-term problem? If that's the case, community and good-will > might be our tool. Or is it a long-term problem? In which case, we might > want to consider other, more direct, measures.