Brett Bonfield writes
I think Jonathan and Nicole nailed it with community health,
I beg to differ.
If you requiree a healthy community to start working with a piece of
software, how do you want a grassroots project to start? Obviously a
small project will start with one or two
Thomas,
That's why I added in 'user' to the community. If there is an active
communication medium with one or two developers communicating with the
user community than there is health there. So I always say to look at
the developer user community to make sure it's active as one of the
gauges of
Something I tried to write about in my article in LJ, is, yes, every
project needs to start somewhere. But you need to evaluate your own
capacity, and compare that against the maturity of the software and the
community. You need more internal capacity to deal with immature
software with an
On Tue, 29 Dec 2009, Thomas Krichel wrote:
Requiring an upfront healthy community is particurly problematic is
a small community such as digital library work.
On the other kind, there is widely adopted software that I got
cajoled into maintaining, that consider bad. Apache is one of
them.
A few lessons learned while monitoring the vuFIND community:
Documentation needs to be evolving and accurate. Someone needs to OWN that
responsibility and keep documentation up to date (and vuFIND are so lucky to
have Demian Katz!). UNIX/man is not the best example for this.
Developer
Nicole Engard writes
That's why I added in 'user' to the community.
No matter how many people use Apache based web sites, it
does not make it Apache software better.
Telling people to use what others are using is just simple
propaganda to stifle competition.
Cheers,
On 12/29/09 7:40 AM, Thomas Krichel wrote:
Brett Bonfield writes
I think Jonathan and Nicole nailed it with community health,
I beg to differ.
If you requiree a healthy community to start working with a piece of
software, how do you want a grassroots project to start? Obviously
I think you may find yourself somewhat in the minority in thinking
Apache is bad software. (I certainly have my complaints about it, but in
general I find it more robust, flexible, and bug-free than just about
any other software I work with).
But aside from getting into a war about some
Francis Kayiwa wrote:
IMHO good open source software is driven by people with an itch to fix.
The community develops and can be cultivated around this itch rather
than world domination. The project _MUST_ well documented [0] ideally
actively maintained. The support of this software will
On Tue, 29 Dec 2009, Jonathan Rochkind wrote:
I think you may find yourself somewhat in the minority in thinking Apache is
bad software. (I certainly have my complaints about it, but in general I find
it more robust, flexible, and bug-free than just about any other software I
work with).
I feel like I'm being misunderstood. I'm not saying if a lot of people use
it it. must be good. I'm saying if there is 1 developer listening to his 1+
users in an open community forum (actual forum, mailing list, chat room,
etc) then the product is healthier than the open source product with no
Telling people to use what others are using is just simple propaganda to
stifle competition
+++
Respectfully, inviting people to an open discussion is exactly the opposite
of telling people and propaganda
12 matches
Mail list logo
