> I think it would be easier to put them together later, if that made
> sense, rather than break them up. 

That's odd, I was thinking exactly the opposite.  

Why not just use one list until one component/package gets too much traffic,
and then break that out into a separate list?  Wouldn't a lot of developers
end up subscribing to many or all of the lists anyway?

> If we have separate lists, we have choice. If we have one list, we have,
> well, spam.

If we have separate lists, I think we'll see a lot of cross-posting, and
posting to the wrong list.  

If we follow a convention like "Subject: [Freem] Does Flarkle have to be
private *AND* final?" and it should be easy enough to filter/sort to get to
the messages you want (and to see when a given component needs a list of its
own).

 - Rod

Reply via email to