And +1 on a separate commons for webapp stuff from me too. Having projects in this commons is best done when there are already a fair number of commons committers who would be interested in contributing, or at least keeping an eye on the new project.
But there are many developers here (like me) who don't actually work with web components much. So having a new component here increases the commons "noise" without drawing in a lot of new contributors. And people interested in webapp-related stuff may well avoid joining the general commons as there is a huge volume of traffic about non-webapp-related projects here. Having a commons dedicated to webapp-related stuff seems much more sensible to me; the subscribers to the related mail list will all be knowledgeable in web-related matters and therefore both interested and able to contribute to multiple projects within that commons. It's all a matter of judgement and guesswork, but my guess is that there is enough interest in webapp-related stuff to make a dedicated commons for that work (though as always, it may take a while to build a community). Maybe things could be set up separately, but CC mails to the existing commons-dev list for a while? Regards, Simon On Tue, 2005-05-31 at 20:04 -0400, James Carman wrote: > +1 > > I agree that these reusable web components (context listeners, session > listeners, etc. included) should be grouped together. > > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 31, 2005 7:46 PM > To: Jakarta Commons Developers List > Subject: RE: [Proposal] Commons Filters > > As Martin alluded, there has been talk about a WebApps Commons, which could > house commonly reusable servlets, taglibs and filters. I still support such > a grouping. > > --- Noel > > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
