On Sun, 07 Dec 2003, Phil Steitz <[EMAIL PROTECTED]> wrote:

> It would be very noisy, indeed.

Szre.

> Here are some stats from October (from message counts displayed at
> http://marc.theaimsgroup.com)
> 
>       struts   tomcat   commons
> user   3115     2908       375
> dev     759     1131      2112

I guess you could remove half of struts user if we added a
jakarta-friday list 8-)

Seriously, combining the user lists is not desirable at all IMHO, as
our users probably don't care too much for the projects they don't
use.

Let's look at the dev lists using nagoya's eyebrowse installation
and looking at the number of mails in Nevember 2003:

Alexandria                 3
BCEL                      12
BSF                        8
Cactus                   173
Commons                 2061
Commons-HTTP-Client      379
ECS                        0
Jetspeed                 283
JMeter                   276
Gump                     292 (*)
Log4J                    146
Lucene                   164
ORO                        3
Pluto                    112
POI                      213
Regexp                    21
Slide                    724
Struts                   431
Taglibs                   35
Tapestry                 110
Tomcat                   982
Turbine                  271
Turbine-JCS               10
Velocity                 244

I think there are more lists than that.

(*) using MARC as Gump is not listed in eyebrowse.

OK, the total is 6953, more than three times the traffic of
commons-dev.  This is unless we'd really split the lists into separate
lists for bug reports, commits and ideas (I'm not sure I'd like that
idea).

Can anybody with a better memory for commons than I have recap why the
httpclient traffic list has been split off?  Did the httpclient
developers want a list of their own or have the developers for the
other commons components been overwhelmed by httpclient traffic?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to