What about moving HiveMind out of the Jakarta Commons? I know this is a controversial suggestion, but here me out a little.
I think HiveMind is a great tool, and the project would benefit from having a community that is focused on HiveMind. Writing "sub-modules" to create reusable HiveMind modules, extending HiveMind, etc, etc, etc... There are a number of projects in Jakarta Commons that might benefit from finding an independent identity apart from Jakarta Commons - like Jelly, maybe Math. (I like Jelly too, I'm not trying to start any fights.) Jakarta Commons doesn't have room for another great project - for one, the resources don't scale very well as there is one mailing list, one website and 68 committers. Sure, you can put up a mail filter and only read email prefaced with [hivemind], but that's not what mailing lists were made for. I like HiveMind so much, I don't want it to be in the Jakarta Commons. This conversation might be more appropriate for [EMAIL PROTECTED], but I refuse to crosspost. :-) Tim -----Original Message----- From: Howard M. Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 5:03 PM To: Jakarta Commons Developers List; 'David Solis'; Harish Krishnaswamy; Essl Christian; Johan Lindquist; Andy Barnett; Bill Lear Subject: [HiveMind] Roll call, please! As I've posted on the the blog, I'm gearing up to form an initial HiveMind community. If you are interested in joining, please drop me an e-mail. Once we form up, we should be able to get everyone commit rights to the hivemind CVS repository. Responsibilities will probably be pretty light; voting on a trickle of issues. Most votes concern addining additional team members, or votes about releases. The fun is not the voting, but the discussing of features and design issues. Step two is to move HiveMind to Jakarta commons proper and set up dedicated mailing lists. I'm researching exactly what the rules and procedures for this are. I feel the base framework is pretty much ready to head towards a 1.0 release; initial work will be documentation and (even better) unit tests, plus creating additional modules as outlined on my blog. Of course, the whole point is we discuss, as a group, what should get done! If you haven't worked on an open source project before ... come on in! The water's fine! All it takes is a desire to do some work, some skill at programming, and the right attitude. It's very rewarding. -- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry http://jakarta.apache.org/commons/sandbox/hivemind/ http://javatapestry.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
