Like your idea, although the smaller lists should be subscribeable. However I thought there were some problems (technical afaik) with these kinds of lists, which I don't recall however..
Mvgr, Martin On Tue, 2003-01-28 at 20:15, Mark R. Diggory wrote: > -1 > > Is it possible to actually "map" component email alias' to the list such > that: > > [EMAIL PROTECTED] could post messages on the > [EMAIL PROTECTED] list with subject headings prepended with > the component name? [jexl] > > While this wouldn't reduce the amount of activity on the list, it would > allow emails to be "filterable" in ones email client. This way instead > of being "best practice" to prepend the component name on Subjects of > the commons list, it would be inherent. If an individual didn't like > getting so much email from a specific component they could filter it at > the client level. > > I personally like seeing all the different activity, it creates vast > amounts of crossover interaction between components and allows the > fullest amount of interaction possible in 'commons'. > > -Mark Diggory > > >> > >> > >> > >>>This has been discussed in the past - but the traffic on commons is > >>>getting bigger as we add more very active components. > >>> > >>>We could split the list based on category - expression languages (jxpath, > >>>jexl, jsp-el, etc ), util libraries ( logging, discovery, modeler, > >>>collections, etc ). > >>> > >>>Opinions ? Should we vote ? > >>> > >>>Costin > >>> > >>> > >>> > > > > > >-- > >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
