couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <>
Subject Re: no communication ? signs of a dying project
Date Wed, 19 Sep 2012 10:36:46 GMT
As a follow up...

CouchDB is in no rush to keep up with anything. Slow and steady wins the
race. We've at Apache for five years, and we'll be here for five years
more. We don't measure ourselves against other projects. That's a quick
route to mediocrity.

Sorry that you didn't get responses as quickly as you were expecting. As
Jan points out, we're all doing this because we're passionate about the
project. Nobody is paid to work on CouchDB. So a little patience is needed.

But also, CouchDB is a do-ocracy. People who do things are the people who
shape the project. Telling other people they should do stuff does not have
a history of working out so great. So if you think newbies should be
responded to faster, try doing it yourself, and getting others to pitch in.
Some sort of triage team might even form around that effort. And if you
think the docs could go faster, hop on to IRC, send a few more emails,
figure out how you can help, and get stuck in.

To quote Gandhi, "be the change you want to see in the project."

Welcome to the team. ;)

On Tue, Sep 18, 2012 at 4:04 PM, john.tiger <>wrote:

> I've tried to get things going on documentation (probably the biggest
> reason couchdb is not more popular) - I put an initial outline forward -
> then nothing - no response.  this is not how to build a successful
> contributor community.  Certainly not like active great projects like
> nodejs, inkscape, ....
> I read somewhere that Apache Foundation is where projects go to die.  I
> hope this is not the case with couchdb but if there is no communication and
> no community, the project will die.   Perhaps there is a small team that is
> being sponsored and trying to do it themselves, but it will not progress
> fast enough (and disregards the whole idea of why open source works).
>  Let's move this forward - let's have some communication!


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message