forking off sublists

well, we have our first set of top level groups sort of working but we
are already making them into minor clones of the p5p list. we need to
start forking sublist for some of these threads already. one obvious
example is the inline code thread. other possible candidates include 
multiline comments, date interfaces, etc.

i personally am not directly interested in the debate on most of these
threads and would like to see them hashed out on their own sublist with
a nice fixed deadline (multiline comments should have 2 weeks IMO). then
i would be interested in seeing a nice rfc and rough consensus report
from that sublist. i got 191 emails this morning and the volume from
perl6 is growing exponentially with threads. we need to move these
threads to sublists as we have agreed.

what would be a good trigger point for when a thread deserves its own
list? the final decision is up to the group leader but we could use some
public guidelines. then someone on the parent group could say let's move
this thread to a sublist, the leader ok's it gets an rfc and ask creates
the list and the parent list volume is lowered a bit.

but we have to start forking off sublists now before we get swamped by
the parent list volume. i am not interested in debating all of these
subjects

and this is the best incentive i have to revamp my mail system. i have
had plans for a long time but i needed more kicks in the head.

thanx,

uri

-- 
Uri Guttman  ---------  uri@sysarch.com  ----------  http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page  -----------  http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net  ----------  http://www.northernlight.com

• forking off sublists by Uri Guttman