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 BA9C39BF5 for ; Mon, 20 Feb 2012 10:52:49 +0000 (UTC) Received: (qmail 92345 invoked by uid 500); 20 Feb 2012 10:52:49 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 92307 invoked by uid 500); 20 Feb 2012 10:52:49 -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 92298 invoked by uid 99); 20 Feb 2012 10:52:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Feb 2012 10:52:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nslater@tumbolia.org designates 209.85.215.52 as permitted sender) Received: from [209.85.215.52] (HELO mail-lpp01m010-f52.google.com) (209.85.215.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Feb 2012 10:52:40 +0000 Received: by lagy4 with SMTP id y4so8252220lag.11 for ; Mon, 20 Feb 2012 02:52:20 -0800 (PST) Received-SPF: pass (google.com: domain of nslater@tumbolia.org designates 10.112.44.1 as permitted sender) client-ip=10.112.44.1; Authentication-Results: mr.google.com; spf=pass (google.com: domain of nslater@tumbolia.org designates 10.112.44.1 as permitted sender) smtp.mail=nslater@tumbolia.org; dkim=pass header.i=nslater@tumbolia.org Received: from mr.google.com ([10.112.44.1]) by 10.112.44.1 with SMTP id a1mr7289240lbm.67.1329735139991 (num_hops = 1); Mon, 20 Feb 2012 02:52:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tumbolia.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=wS9uuP3T3MYHf/3RlZpHlGnn+9vXzckWiW32VXtz1T8=; b=PCiRkCd+v1Dg+1X3rD+YtH5MVYdg4lKsiXlo9h9/v0JFEMNSnjAWr++BCK359c+AE0 PcnGIgi/QpN+UGktsiNpUriMQWSAbqHSnXfHP7x95DlaonFkGciJT8xx/7a9PPpRACxB ljViif8SnL2MvJgAtQROweUyO1XRiFC/UxSo0= MIME-Version: 1.0 Received: by 10.112.44.1 with SMTP id a1mr6084996lbm.67.1329735139892; Mon, 20 Feb 2012 02:52:19 -0800 (PST) Received: by 10.112.20.8 with HTTP; Mon, 20 Feb 2012 02:52:19 -0800 (PST) X-Originating-IP: [178.250.115.206] Date: Mon, 20 Feb 2012 10:52:19 +0000 Message-ID: Subject: Couchbase trademark issues From: Noah Slater To: CouchDB Developers Content-Type: multipart/alternative; boundary=bcaec554dd48a89f8504b96316ac X-Gm-Message-State: ALoCoQkeYnrH1XnNU8uC0mvuXHxsnloTY4OS06dmdm8Rce1d6+WTnySCHyrBPJ8XKnQH2/7KOQq6 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec554dd48a89f8504b96316ac Content-Type: text/plain; charset=ISO-8859-1 Hey, A recent thread [1] on the dev list has concerned me quite a lot. What are your thoughts? Obviously, we have some image problems to address with our own site, but I hope to get to that after the 1.2.0 release. But I am concerned that Couchbase may be infringing the CouchDB trademark, and I'm wondering what to do about it. The ASF trademark policy [2] states that some "uses of another person's trademark are nominative fair use, but some uses are simply infringing. Indeed, if a trademark is used in such a way that the relevant consuming public will likely be confused or mistaken about the source of a product or service sold or provided using the mark in question, then likelihood of confusion exists and the mark has been infringed." Three things seem to be causing this confusion: - Damien works for Couchbase, and has recently abandoned CouchDB. - Damien has publicly announced that he sees Couchbase as "the future of CouchDB." - Couchbase uses the word "Couch" in it's name. - Couchbase ships a backwards incompatible CouchDB-like product. Based on the data I have available to me, the combination of these factors may be causing people less familiar with the project to assume that CouchDB is moribund, and that Damien Katz and the Couchbase company he works for, along with their CouchDB-like product suite, are the logical successors to CouchDB. I think, therefor, that the use of the word "Couch" in Couchbase may be infringing, and that if it were changed, some of this confusion might be averted. I am prepared to take this to legal, but I wanted some feedback on it first. Thanks, N [1] http://s.apache.org/g0N [2] http://www.apache.org/foundation/marks/ --bcaec554dd48a89f8504b96316ac--