On Fri, 12 Sep 2003, Tim OBrien wrote:
> What about moving HiveMind out of the Jakarta Commons? I know this is a > controversial suggestion, but here me out a little. There are two roles in Commons. One is incubation in Commons-Sandbox, the other is Commons projects that are being used in various Jakarta [Apache] projects. Hivemind is definitely using Commons for incubation I think. Looking at Howard's email, it even sounds like incubation, with the Hivemind community not being the Commons community. > 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.) I agree to Jelly. Jelly and HttpClient are the two that could most easily become full on projects. Math needs to gain more maturity, though moving to the Apache Incubator project might help to boost its independence. Unsure if that's best. Re-usable mathematical bits would be great to keep in Commons, but Math is definitely growing into a big collation of mathematical algorithms etc. I think it's up to the committers for that sub-project to make the decision though. Then the rest of Commons is asked. I'm not sure how it happened before with Cactus. > Jakarta Commons doesn't have room for another great project - for one, the More than enough room :) > 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. 4 mailing lists. users/dev, and httpclient has its own pair of lists. If hivemind gets noisy, it can have its own list. Jelly's JIRA noise to actual [jelly] discussion suggests they use JIRA more for communication, but I could just have a mental habit of hitting 'd' for [jelly]. > 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. :-) Nah. It's for the hivemind community and to a lesser extent the Commons community [and the PMC]. This is where the big issue comes in. Until Hivemind has community, or at least a driving Jakarta project, it's unlikely to become a Jakarta project or Commons proper. [Continuing in Howard's email] > -----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. Why not the list? > Once we form up, we should be able to get everyone commit rights to the > hivemind CVS repository. Really? Without any patches/code? Unless they're already Jakarta (Apache?) committers, commit rights won't be immediately handed out [I reckon]. > 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. People are really worried about the responsibilities? It's probably true, but I hadn't thought it was needed as a selling point. It's taken a while, but I've realised the responsibility is what you step forward and accept and what the community will allow you to take. > 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. You can ask for a dedicated list as a Commons project, but unless you've actually got the content happening I suspect you'll get quite a few -1's. We don't want httpclient to be a separate list, it's just too damn noisy. > 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! I applaud the honest of admitting that is currently a benevolent-dictator driven project. Poor PR though I suspect. :) > 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. +1. Other questions: So how is Hivemind different to Avalon? It seems like it must clash with the Avalon kernel or something. Not that I grokk either project. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
