Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ncar!gatech!mcnc!beguine!Gerben.Wierda
From: Gerben.Wierda@samba.acs.unc.edu (Gerben Wierda)
Newsgroups: comp.sys.next
Subject: SPLIT group
Keywords: Name
Message-ID: <2613@beguine.UUCP>
Date: 15 Feb 91 09:54:24 GMT
Sender: usenet@beguine.UUCP
Lines: 32


This is a serious posting (the previous one wasn't, really)

*If* we are going to split, then the names of the subgroups are very
impoortant. Take this: if a group is called comp.sys.next.tech or
comp.sys.next.discussion it is likely that I would not know where to
post most of the time. Therefore we should use names that are more
helpful in a split up that is more than only a volume split-up.

I therefore propose that the following subgroups:
comp.sys.next.develop		# for C, C++, IB, Objective-C
comp.sys.next.connectivity	# for TCP/IP, UUCP, Kermit, modems, etc.
comp.sys.next.maintenance	# for hardware/software upgrading,
				# system admin
comp.sys.next.applications	# for things like WriteNow, Improv and
				# other ready-to-use products

I assume that if (for instance) the people doing music applications and
development are creating too much noise for either the development or
application subgroup it is time to make subsubgroups like
comp.sys.next.application.music or ...develop.music

Oh, I forgot, because NeXT is a new machine it would be nice to have a
comp.sys.next.announce, but I don't know if there are any problems
(legally) with such a subgroup.

I hope this is a useful addendum, so that people are not going to flame
me for being the source of the problem (newsgroup becoming too big)...

Greetings to you all

Gerben