>Has the management considered splitting comp.lang.python into
>subgroups? Perhaps:
> comp.lang.python.announce for new versions, bug fixes, etc.
> comp.lang.python.help for help queries and responses
> comp.lang.python.futures for discussion of possible new features
>I was on the E-mail list because I wasn't getting comp.lang.python from
>my news server, and the volume was interfering with my work! Call it
>a self-control issue if you like (I could skip most messages based on
>the subject line), but it typically required > 30 minutes a day to scan
>through the Python messages (and I may be underestimating). Fortunately,
>my news server problem has been resolved, but the issue remains -- with
>news, I tend to miss lots of messages because I don't get around to
>scanning them before they expire. With more focussed subgroups, I
>would scan the announce group more frequently and the others as needed
>or as time allows.
>BTW, I think it is great to have this problem, versus having a list
>where the traffic was minimal and therefore less useful. I would just
>like a little help dealing with the volume.
I don't know how much news you read, but the volume on comp.lang.python
doesn't warrant a split yet. I think that we max out on a good (or bad)
day at about 100 messages with 30-40 being perhaps average. I could be
wrong, I check news fairly frequently during the day.
If you have problems with the volume, you should consider using a newsreader
that would thread articles and allow you to scan subject headings.
-- Jeffrey C. Ollie Iowa Network Services Support Daemon