"Craig R. McClanahan" wrote:
> +1, except for having separate mailing lists (if you included that in "etc." :-).  A
> common list for all the library components seems more practical, and better at
> encouraging the use of other components in the library ("gee, I didn't know we had a 
>FOO
> until I saw a question about it on commons-dev").

I think we should be very sensitive to traffic and attention-span. If
subscribing to a list about a package you use means wading through a lot
of mail about packages you don't use, then people may unsub and
fall-away. (I know I do ;-)

I do agree we should make good use of an announcement list to help
publicize news about other packages (and products). But here I would
suggest we automatically subscribe everyone to jakarta-announce, and let
them unsub from that if they don't like it.

The catalog will also encourage more spelunking and serendipity.

-Ted.

Reply via email to