Xref: utzoo unix-pc.general:6499 comp.sys.att:10899
Path: utzoo!utgpu!watserv1!watmath!uunet!nih-csl!helix.nih.gov!crtb
From: crtb@helix.nih.gov (Chuck Bacon)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: CALL FOR DISCUSSION: comp.sys.3b1
Summary: Points to consider
Keywords: 3b1 CFD comp.sys.3b1
Message-ID: <651@nih-csl.nih.gov>
Date: 20 Nov 90 01:46:20 GMT
References: <1990Nov19.040128.29048@bagend.uucp>
Sender: news@nih-csl.nih.gov
Followup-To: unix-pc.general
Organization: National Institutes of Health, Bethesda
Lines: 57

Here is my collection of points to consider in the discussion.
Others may do this more elegantly, but I think I cover them all
fairly well.  Please backflame if I miss something.

A. We wish to create a newsgroup, comp.sys.3b1, to augment and eventually
replace the five existing unix-pc.* newsgroups because:

1. The unix-pc.* newsgroups are unknown at many sites; many newsgroup
   managers say that only "standard" named newsgroups can be allowed.

2. One newsgroup instead of five.  I've been reading comp.sys.att for
   about a year, and unix-pc for about three months.  In all that time,
   I think I've seen about two "test" messages in those groups.
   I've seen a small number of "sources" (almost all shell scripts),
   posted to comp.sys.att and unix-pc.general.  I'm not sure, but I
   don't think I've ever seen an entry in unix-pc.{sources,bugs}.

3. Considering comp.sources.3b1 as one of multiple groups; I run
   Larry Wall's rrn.  I routinely say: rrn unix-pc   and get the
   five newsgroups (any that are non-empty).  If I were to command:
   rrn comp.sources   , I would get everybody else's sources too!

4. Multiple newsgroup names versus a single name; I prefer the single
   name comp.sys.3b1.  After all, if all the other AT&T models can
   exist within one newsgroup, I think we can too.  Sources don't
   live very long on our nntp server (48 hours?), so it's just as
   well if I see 'em as soon as posted.  Also the traffic: I think
   the average posting on unix-pc.* has been about ten a day across
   all five NGs.  I can look at the first screenlload of a posting
   and hit n if I don't want to look at the rest.  Or, if I run xrn
   (at work), I can go down the list of subject lines.

B. Now for some negatives; reasons NOT to create a comp.sys.3b1

1. The name unix-pc being rather unusual, it is more likely that a
   3b1 owner will have to find a feed from a fellow hobbyist.  This
   breeds self-reliance.  The very difficulty of getting the feed
   will enhance the sense of pride in those who succeed.

2. The 3b1/7300/unix-pc/Miniframe is a wonderful machine, particularly
   at the price.  Creation of a virtual advertisement for the 3b1
   through the existence of a more visible newsgroup name like
   comp.sys.3b1 will attract more people to this system.  This will
   tend to result in greater demand for these systems, thus higher
   prices for second machines, parts etc.  I'm sure everybody who
   has one thinks it's expensive enough already.  (If you're trying to
   sell one of these, don't read this).

I can't think of anything more on the subject.  I've been very impressed
with the quality of what I've seen in the unix-pc newsgroups.  Every
posting I've seen is thoughtful, and many have been useful.  If I've
violated the usual courtesy of brevity (Oh Polonius, where are you
when I need you?), I apologize.

--
Chuck Bacon - crtb@helix.nih.gov - 301-496-4823
	"After all, computers have rights too!" - Ernst Bacon, 1898-1990