On Tue, 28 Jan 2003, Dmitri Plotnikov wrote:
> Date: Tue, 28 Jan 2003 11:23:30 -0800 (PST) > From: Dmitri Plotnikov <[EMAIL PROTECTED]> > Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: Jakarta Commons Developers List <[EMAIL PROTECTED]> > Subject: Re: Time for more mailing lists ? > > How expensive is it to set up a mailing list? Can we have a ton of > those, one per subproject? > It's trivially cheap from a technical perspective, but horribly over-complicated from a *user* perspective, IMHO. --- A Reader's Perspective --- Personally, I much prefer a single higher-volume list, especially when posters are pretty good about "[package]" prefixes on subject lines like they are here, than I would a bunch of individual lower-volume lists specific to a package. That way, I can keep an eye on what is going on throughout the group of packages, but skim the subject lines if I'm in a hurry at the moment. If the fine-grained lists come into existence (I'm going to vote against on the packages I'm involved with), I'd just lump them all into a single folder anyway. --- A Poster's Perspective --- Here is where lots-o-little-lists has more problems. How do you know which list to post to? Especially if it's a question of broader interest than a single package? Every time I've seen someone try fine-grained lists in a situation like this, the poster's choice has been lots of cross-posting, to ensure that everyone who might be interested. Of course, the reader who is subscribed to multiple fine-grained lists is going to get that message multiple times instead of just once, dramatically *increasing* the effort required to manage them. That seems quite counter to the purported goals of the effort. --- Summary --- I'd just as soon have the [httpclient] guys back on commons-dev so that I can more easily keep track (without having to subscribe separately), but that's up to them. Mail filters and folders are basic tools that can make the management of high volume lists straightforward. Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
