Path: utzoo!attcan!telly!lethe!torsqnt!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!crdgw1!lewis.crd.ge.com!welty
From: welty@lewis.crd.ge.com (richard welty)
Newsgroups: news.groups
Subject: Re: rec.swl
Message-ID: <2831476267@lewis.crd.ge.com>
Date: 22 Sep 89 17:11:07 GMT
References: <9989@multimax.Encore.COM> <45945@bbn.COM> <34957@apple.Apple.COM>
Sender: news@crdgw1.crd.ge.com
Reply-To: welty@lewis.crd.ge.com (richard welty)
Followup-To: news.groups
Organization: New York State Institute for Sebastian Cabot Studies
Lines: 35

In article <34957@apple.Apple.COM>, Chuq Von Rospach writes: 

*After thinking about feedback overnight, here are my current thoughts on
*naming:

*	rec.radio.dxing
*	rec.radio.monitoring

*I still don't think they're perfect, but... (and I *hate* the term dx. Don't
*ask me why, it's not logical...)

here's an alternative -- i've been wanting a general radio group
for some time.  create rec.radio; if it's dominated by dx, swl, or
what have you, that's fine, but it would provide a place for other
discussions of radio as well.  i'm interested in discussions of
radio station operation, formats, programming, etc. that really
don't fit in to rec.music.* or anywhere else on the net; this
group would provide such a place.

the principle is simply to create the most general group first, and
spawn off the other groups as needed.  this is the principle that
should have been followed with rec.models.rc -- rec.models should
have been created first.

as for rec.ham-radio; i suppose we'll just have to leave it where
it is -- a renaming to rec.radio.ham would far to painful to
contemplate.

in summary:  create rec.radio; see what traffic develops, and
act accordingly.

richard
-- 
richard welty    518-387-6346, GE R&D, K1-5C39, Niskayuna, New York
..!crdgw1!lewis.crd.ge.com!welty            welty@lewis.crd.ge.com