Doh, didn't realize the Reply-To was not set. Sorry, Scott
-----Original Message----- From: Scott Sanders Sent: Friday, October 18, 2002 10:16 AM To: 'Sander Striker' Subject: RE: Granularity of Codebases? > > For example. Where I am from we have a small library for > dealing with > > Java > > Extensions (think .dlls or .sos with additional metadata). > When the component > > started it had 2-3 source files with a single purpose. > > Was it mature? Did it have a community? On the question of community, is the user base also considered community. For example, Geir attempted to bring PoolMan into Jakarta, but the 'community' perceived at that time was only one developer. The thousands of users did not count to anyone but Geir and a few other people (me). I would say that PoolMan was a healthy community (I chose to use it because it was the best component at the time, and I was getting my questions answered). Does that count as community? What about a codebase that is mature (jakarta-regexp), and doesn't really have any development momentum? > > It probably does not warrant it's own mailing list or it's own > > dedicated > > space. However it is a reusable focused component. > > It's a reusable component? It's usefull? Then it does > warrant both a ML and some webspace explaining what it does. > Without those, a community is bound to fall apart or will go > by unnoticed (so that it never grows). I would like to note here Sander, that jakarta-commons has only one development mailing list for all of the small projects, and it has worked out very well from the 'building a community perspective'. Not saying that separate mailing lists are bad, just stating MHO. Scott
