I would absolutely agree with you on this one. Do you know what you get
when you subscribe?
Welcome to the linux-kernel mailing list!
Please save this message for future reference. Thank you.
you can send mail to <Majordomo@vger.rutgers.edu> with the following
command in the body of your email message:
unsubscribe linux-kernel abszero@epix.net
#### No info available for linux-kernel.
Thats it. Nothing that says anything about what the list is for (and what
it is NOT for).
I would also sugest that there is a thinger (highly technical term) so that
if enough people (1/3 of subscribers?) vote to deny post-access, they will
have post-access revoked for a limited time (2 wks?). Also, should there be
sub-lists spawned?
How about this:
(l.k. is linux.kernel. This list is from the PoV of the News<->list
gateway.)
l.k.request --- I don't want to program it myself, but I have an idea
l.k.bugs --- I think I have a bug
l.k.patches --- I fixed a bug. (Pointers to patches prefered <G>)
l.newbie --- The proper place for "how do I do this?"
l.k.debate.proc--- Temp! Debate about the proc-fs
l.rc5-chalenge --- Temp! Is this subject dead yet?
l.list-admin --- Administrative stuff for these groups. Ex: messages
like this. <G>
l.k.debate.vm --- Temp! Virtual memory, overruns
l.k --- Everlthing else
I would sugest that we spawn sub-lists often, and that upon creation, all
subscribers to l.k be automaticly subscribed to the new list, with
notification. If there have been no posts to a list for a week, it should
be automaticly killed.
--- James Mastros