You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "john.tiger" <jo...@gmail.com> on 2012/09/18 17:04:20 UTC
no communication ? signs of a dying project
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!
Re: no communication ? signs of a dying project
Posted by Paul Davis <pa...@gmail.com>.
On Tue, Sep 18, 2012 at 10:25 AM, Jan Lehnardt <ja...@apache.org> wrote:
> Dear John,
>
> Thanks for caring about CouchDB.
>
> On Sep 18, 2012, at 17:04 , john.tiger <jo...@gmail.com> 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.
>
> That’s because the team had been working on https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=shortlog;h=refs/heads/docs before your post. Noah had
> alluded to that in the thread that was brought over to dev@.
>
Also, the JIRA issue for the docs import is here:
https://issues.apache.org/jira/browse/COUCHDB-1523
>
>> this is not how to build a successful contributor community.
>> Certainly not like active great projects like nodejs, inkscape, ....
>
> I’m sorry nobody replied to your message yet. This is a group of
> volunteers and everybody contributes in their own time. Out of
> experience, I'd say most emails will get an answer.
>
> Also, from experience, the best chance to get things moving here
> is starting, and showing some work. This usually gets other people
> excited and contributing. Like everywhere else :)
>
>
>> I read somewhere that Apache Foundation is where projects go to die.
>
> You mean like Lucene, Hadoop, Cassandra, httpd(!), PhoneGap/Cordova etc? :)
>
> It's a funny enough quip, but don’t believe everything the press says,
> or what you read on Twitter.
>
>
>> 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!
>
> I’m sure with the right set of contributions, we'll get there. Thanks
> again for caring about CouchDB and for offering to help out!
>
> Best
> Jan
> --
>
>
Re: no communication ?
Posted by "john.tiger" <jo...@gmail.com>.
On 09/18/2012 09:25 AM, Jan Lehnardt wrote:
> Also, from experience, the best chance to get things moving here is
> starting, and showing some work. This usually gets other people
> excited and contributing. Like everywhere else :)
thks for fast communication:)
sure, I'm just trying to get us involved - okay, thks for links (and
Paul too) - I just downloaded snapshot and xml - will try to get some
contribs forwarded - especially from the developer standpoint
Re: no communication ? signs of a dying project
Posted by Jan Lehnardt <ja...@apache.org>.
Dear John,
Thanks for caring about CouchDB.
On Sep 18, 2012, at 17:04 , john.tiger <jo...@gmail.com> 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.
That’s because the team had been working on https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=shortlog;h=refs/heads/docs before your post. Noah had
alluded to that in the thread that was brought over to dev@.
> this is not how to build a successful contributor community.
> Certainly not like active great projects like nodejs, inkscape, ....
I’m sorry nobody replied to your message yet. This is a group of
volunteers and everybody contributes in their own time. Out of
experience, I'd say most emails will get an answer.
Also, from experience, the best chance to get things moving here
is starting, and showing some work. This usually gets other people
excited and contributing. Like everywhere else :)
> I read somewhere that Apache Foundation is where projects go to die.
You mean like Lucene, Hadoop, Cassandra, httpd(!), PhoneGap/Cordova etc? :)
It's a funny enough quip, but don’t believe everything the press says,
or what you read on Twitter.
> 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!
I’m sure with the right set of contributions, we'll get there. Thanks
again for caring about CouchDB and for offering to help out!
Best
Jan
--
Re: no communication ? signs of a dying project
Posted by Octavian Damiean <ma...@gmail.com>.
I'd like t add that if you can't figure out yourself how to help then ask
on IRC or the mailing list. :)
On Wed, Sep 19, 2012 at 12:36 PM, Noah Slater <ns...@tumbolia.org> wrote:
> 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 <john.tigernassau@gmail.com
> >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!
> >
>
>
>
> --
> NS
>
Re: no communication ? signs of a dying project
Posted by Noah Slater <ns...@tumbolia.org>.
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 <jo...@gmail.com>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!
>
--
NS
Re: no communication ? signs of a dying project
Posted by Tim McNamara <pa...@timmcnamara.co.nz>.
On 19 September 2012 22:19, Noah Slater <ns...@tumbolia.org> wrote:
> On Tue, Sep 18, 2012 at 4:04 PM, john.tiger <jo...@gmail.com>wrote:
>
>> but it will not progress fast enough
>
>
> For what?
Isn't it obvious? For the imminent Mongo deathmatch.
Re: no communication ? signs of a dying project
Posted by Noah Slater <ns...@tumbolia.org>.
On Tue, Sep 18, 2012 at 4:04 PM, john.tiger <jo...@gmail.com>wrote:
> but it will not progress fast enough
For what?
--
NS