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 2D45F994E for ; Tue, 21 Feb 2012 00:28:47 +0000 (UTC) Received: (qmail 11840 invoked by uid 500); 21 Feb 2012 00:28:46 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 11802 invoked by uid 500); 21 Feb 2012 00:28:46 -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 11794 invoked by uid 99); 21 Feb 2012 00:28:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 00:28:46 +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 (nike.apache.org: domain of randall.leeds@gmail.com designates 209.85.210.52 as permitted sender) Received: from [209.85.210.52] (HELO mail-pz0-f52.google.com) (209.85.210.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 00:28:40 +0000 Received: by dado14 with SMTP id o14so8428067dad.11 for ; Mon, 20 Feb 2012 16:28:19 -0800 (PST) Received-SPF: pass (google.com: domain of randall.leeds@gmail.com designates 10.68.203.130 as permitted sender) client-ip=10.68.203.130; Authentication-Results: mr.google.com; spf=pass (google.com: domain of randall.leeds@gmail.com designates 10.68.203.130 as permitted sender) smtp.mail=randall.leeds@gmail.com; dkim=pass header.i=randall.leeds@gmail.com Received: from mr.google.com ([10.68.203.130]) by 10.68.203.130 with SMTP id kq2mr60857660pbc.136.1329784099245 (num_hops = 1); Mon, 20 Feb 2012 16:28:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=qk5dvtJfNMu9lSX0vO0simb7yNu7pmvgDhlpqgsdr2Q=; b=Cp6DcQLubpgSotL/6hWzjjufpO7oOqMhVzMZNitYJbYkx5+mJlZEHgwkQn6ofPxoNo m2yfbXGnA+vdmND4+6czzysrIUgSzTPENoRrBGQJbFfjsg0p64w0BR4dLR6Vu+DfAcwf 7yvnXQFxeIcTBwV3P9IJEYwp9+Gl/9C/id9y4= MIME-Version: 1.0 Received: by 10.68.203.130 with SMTP id kq2mr50558697pbc.136.1329784099208; Mon, 20 Feb 2012 16:28:19 -0800 (PST) Received: by 10.68.221.98 with HTTP; Mon, 20 Feb 2012 16:28:19 -0800 (PST) In-Reply-To: References: <6FF0CC13-1EB5-4488-AB47-74DD132EA398@gmail.com> <3335C56A-1A37-4E40-BA64-9CFA5860F4D8@purplebulldog.com> Date: Mon, 20 Feb 2012 16:28:19 -0800 Message-ID: Subject: Re: Couchbase trademark issues From: Randall Leeds To: dev@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Feb 20, 2012 at 16:21, Jason Smith wrote: > ## Facts > > * CouchOne built products and services promoting CouchDB for one year > * Couchbase did the same, plus held events, for about one year > * Couchbase pivoted their products and branding a scant ten weeks ago. > * The pivot announcement acknowledges the confusion and lays plans to > address it. > * Couchbase's DB sync product is un-confusingly named Mobile SyncPoint > and uses the Couch replication protocol > * Couchbase employs several CouchDB committers > > ^^ Kindly restrict responses to fact only, thanks. > > ## Opinions > > * The confusion is a recent, manageable, phenomenon. Its peak (or > depth) is at most ten weeks old, less if you consider holidays. > * It will blow over. > * ASF committers at Couchbase are admirable. They all keep their > mouths shut. Some of them quietly commit code (to CouchDB or GeoCouch) > day-in, day-out. > > Like a lifelong friendship that's hit a rough patch, the rewards of a > years-long relationship outweigh the cost of the transgression. > > The key word from Benoit's emails is "gentlemen." Good summary. I agree with all the facts. On the opinion that it will blow over, we must do our part to help (that's all the other issues for other threads that Noah mentioned). CouchBase should figure out what they can do as well, and they should share those plans with us so we can all reduce confusion together.