couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <>
Subject Re: Introducing CouchDB Ltd.
Date Sun, 08 Mar 2009 21:14:05 GMT
Hi Dave,

On 8 Mar 2009, at 22:04, Dave butlerdi wrote:

> It looks like this
> Very inclusive, giving a wide range of optios, and showing off many   
> of the
> possible support options available. I think that as a means
> of garnering support for a technology this is far better than a single
> startup.

I don't see why we can't set this up as well. At the moment, we only
have the "In The Wild" wiki page which is less fancy and is not exactly
the same thing, but CouchDB is not Rails (just yet :-).

> Again, not adverse to commercialisation, as there are many firms that
> require support, however the name and the manner in which it has  
> been done
> is as I said before, in my opinion counter productive to the  
> promotion of the
> project to a wide range of developers and users alike.

We hoped to be judged "good mannered" by discussing this publicly
instead of presenting a situation set in stone*. Given that we replied  
the naming issue rather immediately, why do you think our plans are
counter-productive? I hope we can clear your doubts.

*note that still redirects to


> On Sun, Mar 8, 2009 at 8:32 PM, Dean Landolt <>  
> wrote:
>> On Sun, Mar 8, 2009 at 2:23 PM, Dave butlerdi <>  
>> wrote:
>>> Was quite suprised to see CouchDB Ltd on the slides from the Hadoop
>> meeting
>>> in Berlin. Was unable to get up there but really think that this  
>>> is a bad
>>> move.
>> I work for a company *very *unfriendly to (rather, more unfamiliar  
>> with)
>> open-source. Having commercial entities behind specific software  
>> projects
>> lends them a legitimacy to many people. If you're arguing that  
>> CouchDB Ltd.
>> may be an endorsement or misleading name, that's one thing, but I  
>> fail to
>> see the poor taste behind announcing any and all commercial endeavors
>> behind
>> couch.
>>> You are an Apache project and this just seems counter productive.  
>>> I also
>>> think that several other projects have become entailed  of this  
>>> type of
>>> behaviour and had problems with Apache in the end.
>> Can you give an example? As an IP geek I'm always interested in  
>> reading
>> about how these kinds of things go wrong.
>>> I do not commit, not am I interested in commercialising my  
>>> experience
>> with
>>> the product,  but use Couch. However, to use the project name for
>>> commercail
>>> gain by a few does seem wrong. Why not follow the Ruby/Rails  
>>> example and
>>> set
>>> up a community effort for the provision of services under the  
>>> CouchDB
>> name.
>> Can you expound on what you mean by that? I'm unfamiliar with the  
>> rails
>> community -- what does a "community effort for the provision of  
>> services"
>> look like?
> -- 
> Regards
> Dave Butler
> butlerdi-at-pharm2phork-dot-org
> Also on Skype as butlerdi
> Get Skype here
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
> **********************************************************************

View raw message