Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!ogicse!milton!wiml
From: wiml@milton.u.washington.edu (William Lewis)
Newsgroups: comp.sys.next
Subject: Re: split up comp.sys.next (PLEASE!!)
Message-ID: <1991May6.060500.26605@milton.u.washington.edu>
Date: 6 May 91 06:05:00 GMT
Article-I.D.: milton.1991May6.060500.26605
References: <14461@ccncsu.ColoState.EDU> <1438@radius.com> <1991Apr26.013917.2813@lth.se>
Organization: University of Washington, Seattle
Lines: 30

In article <1991Apr26.013917.2813@lth.se> bengtl@maths.lth.se (Bengt Larsson) writes:
>In article <1438@radius.com> lemke@radius.com (Steve Lemke) writes:
>>comp.sys.next.announce	Important notices for NeXT users. (Moderated)
>>comp.sys.next.apps	Discussions of NeXT applications.
>>comp.sys.next.comm	Discussion of NeXT communications.
>>comp.sys.next.hardware	NeXT hardware issues & discussions.
>>comp.sys.next.misc	General discussions about the NeXT.
>>comp.sys.next.programmer Discussion by people programming the NeXT.
>comp.sys.next.os	Discussions of NeXT system software.
>>comp.sys.next.wanted	Postings of "I want XYZ for my NeXT."
>
>I think this is a good proposal, with maybe a question mark for
>comp.sys.next.comm which I don't think needs to be a separate group.

  Actually, I don't think there's quite enough volume to justify this
many groups. A lot of them can be folded into each other:

  groups                         become

csn.announce (moderated)    Same as above
csn.[apps/os/comm/wanted]   "csn.software" perhaps? or "csn.apps"
csn.[hardware/programmer]   "csn.programmer" or "csn.technical"
csn[.misc]                  just plain comp.sys.next

    If I am not flooded with hate mail, I will post a CFD based on these
in a few days. Does anyone care to moderate csn.announce? 
-- 
 wiml@milton.acs.washington.edu       Seattle, Washington   
     (William Lewis)   |  47 41' 15" N   122 42' 58" W  
 "Just remember, wherever you go ... you're stuck there."