Re: Is the scala list getting too busy? (correction)

On 1/29/07, martin odersky <odersky@xxxxxxxxx> wrote:
> [Sorry, last mail got sent by accident before I was finished composing]
>
>  Dear all,
>
>  Over the weekend we must have had upwards of 100 messages on scala (I did
> not count them, but that's how it felt). Lively discussion and lots of
> questions are great! However, I am worried that people who subscribed to the
> scala list only for keeping track of important announcements will
> unsubscribe now, because they cannot tolerate the load.
>
>  One possible answer would be to turn the mailing list into a newsgroup. I
> am skeptical about this, because I personally don't read news anymore (takes
> too much time, and a different reader).
>
>  Another possibility would be to sub-divide the list. I have thought about
> this and would like to present the following proposal.
>  There could be three lists:
>
>  scala                        for announcements, fundamental questions, and
> starts of discussions.
>  scala-programming    for presentations of nice programming solutions,
> questions about programming etc.
>  scala-discussion       for discussions about language design, libraries,
> language evolution, etc.
>
>  What do you think? Is this useful? Which of the lists would you subscribe
> to? Should there be other sublists?
>  Please respond directly to me. I will then summarize to the list.

I'm fine with the amount of list traffic so far but I must confess
reading LKML, so...

If you really want to create different lists, I would only create an additional
announce list 'scala-announce' and keep the 'scala' list as is.
The traffic is really not that much and it is easy to filter based on subject.
I personally find it harder to track many separate but related lists more
than one high-traffic and one low-traffic list. Some might say it's only a
matter of the right tool but I'm not so sure about that.