Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!dino!mehl
From: mehl@cs.iastate.edu (Mark M Mehl)
Newsgroups: news.groups
Subject: Re: Splitting Comp.Sys.Mac again (was Re: Too many messages in ....)
Message-ID: <534@dino.cs.iastate.edu>
Date: 7 Feb 90 08:27:39 GMT
References: <629@ascom.UUCP> <38387@apple.Apple.COM> <1603@umigw.MIAMI.EDU> <38392@apple.Apple.COM>
Sender: news@dino.cs.iastate.edu
Reply-To: mehl@atanasoff.cs.iastate.edu
Lines: 57

chuq@Apple.COM (Chuq Von Rospach) writes:
>My preferences right now would be:
>comp.sys.mac.misc
>comp.sys.mac.d
>comp.sys.mac.wanted
>comp.sys.mac.futures

Well, let me suggest a different breakdown:
comp.sys.mac.app   (for discussion of Mac applications)
comp.sys.mac.os    (for discussion of system and networking issues)

Now let's examine how well they fit the article profile of
comp.sys.mac posted by Chuq:

> Topics with the most responses:
> #msgs	subject line

c.s.mac   >42 Priority scheme for comp.sys.mac.binaries?
c.s.m.os  >29 What I'd like to see in the AppleShare of the 90's
c.s.mac   >27 Low-Cost Macintosh
c.s.mac   >26 MacWorld's Phony Offers
c.s.m.os  >25 A call for "3D look" interface guidelines from Apple
c.s.m.app >17 Macintosh Yellow Pages
c.s.m.app >16 Backup Utility Recommendations...
misc.forsale >14 Rolex watch for sale
c.s.m.app >13 Windows 3.0: Coming of age
c.s.m.os  >12 no 6.0.4 upgarde path
c.s.mac   >12 Mac only has 90-day warranty
c.s.m.os  >12 Hiding background layers in MultiFinder
c.s.m.app >11 ShortCut vs. Boomerang: Opinions?
c.s.mac   >11 MIP rating for the Mac II
c.s.m.app?>11 FastPath vs. GatorBox
c.s.m.os? >11 Don't buy SuperLaserSpool (or anything from SuperMac)
c.s.m.app >11 ATM
c.s.m.app >10 Text file madness: diagnosis & prescription.
c.s.m.os  >10 Changing Boot "Welcome" message

Well, that breakdown just about divides out most of the traffic in what
is now comp.sys.mac fairly well.  In making the above breakdown, some
issues came into mind.  "Exactly what are the system and networking
articles that should be posted to comp.sys.mac.os instead of c.s.mac
or c.s.m.app?"  The charter for comp.sys.mac.os needs to be well
defined to prevent confusion.  I would, for example, consider cDEV's
and INIT's, and spoolers to be system issues, but would everyone else?
I would even consider viruses to be systems issues (afterall when a
main-frame gets a virus, the systems people fix it), but would others
consider placing a discussion on viruses in comp.sys.mac.os?

I think the charter for c.s.m.os is going to be tricky to write and
confusing for non-computer oriented people to follow.  Nevertheless,
I'm for the c.s.m.os and c.s.m.app breakdown.  When do we get
started?
--
 /\ Mark M Mehl, alias Superticker (Supertickler to some)
<><> Internet: mehl@atanasoff.cs.IAstate.edu
 \/ UUCP: {{mailrus,umix}!sharkey,hplabs!hp-lsd,uunet}!atanasoff!mehl
Disclaimer: You got to be kidding; who would want to claim anything I said?