I do find the product name confusing, and it seems beyond question that it confuses our community. So, we could navel gaze over whether it meets the "probability of confusion" threshold if we want to, but it seems unnecessary given the genuine confusion being expressed already.
Perhaps we should approach Couchbase, and the CouchDB committers who work there, notably our Chair, whether they would voluntarily rename their product to avoid any further confusion first? For full disclosure, I should note that I work with Cloudant, who produce BigCouch. I don't see the same confusion happening between "CouchDB" and "BigCouch" but it would be unfair not to ask the same question about it than we are asking about "Couchbase". My sense is that the community is not confused about the difference between CouchDB and BigCouch and, given the intention to contribute BigCouch to the CouchDB project, there will soon be no distinction at all. However, I think it's only fair that we consider both products. Since Couchbase is no longer compatible, the name is pretty obviously misleading. I understand how it got here but I think it should be remedied. B. On 20 February 2012 11:19, Noah Slater <[email protected]> wrote: > On Mon, Feb 20, 2012 at 10:54 AM, Dirkjan Ochtman <[email protected]>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.
