Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!aplcomm!capd.jhuapl.edu!waltrip
From: waltrip@capd.jhuapl.edu
Newsgroups: comp.sys.next
Subject: Re: Call for vote: SPLIT GROUP!
Message-ID: <1991Feb14.144545.1@capd.jhuapl.edu>
Date: 14 Feb 91 19:45:45 GMT
References: <EbiAXsa00UzxI4eqRg@andrew.cmu.edu> <1076@kaos.MATH.UCLA.EDU>
Sender: news@aplcomm.JHUAPL.EDU
Organization: CAPVAX, JHU/APL
Lines: 25

In article <1076@kaos.MATH.UCLA.EDU>, barry@pico.math.ucla.edu (Barry 
Merriman) writes:

	[...material deleted...]
> I agree its time for a split---but how about a sequence of
> bifurcations as needed, rather than splintering all at once.
> The first bifurcation, it seems, would be
> 
> comp.sys.next.technical_aspects_of_apps,_system_admin_and_hardware
> comp.sys.next.general_discussions_of_next_related_issues
> 
> although I think the naming requires a bit more work.:-)
> 
	I agree with this approach.  I believe I've seen it implemented with
	names (to tweak Barry's suggestions just a tad) such as:
		comp.sys.next.tech
		comp.sys.next.discussion or comp.sys.next.d
	in other newsgroups I've followed.
	[...more material deleted...]

c.f.waltrip

Internet:  <waltrip@capsrv.jhuapl.edu>

Opinions expressed are my own.