Xref: utzoo news.groups:29412 comp.sources.d:6680
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!caen!uakari.primate.wisc.edu!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: news.groups,comp.sources.d
Subject: Re: comp.archives.admin (was CFD Creation of comp.archives.d)
Message-ID: <3286@crdos1.crd.ge.COM>
Date: 22 Mar 91 15:32:57 GMT
References: <1991Mar18.221702.11225@sparky.IMD.Sterling.COM> <EMV.91Mar22000953@poe.aa.ox.com>
Reply-To: davidsen@crdos1.crd.ge.com (bill davidsen)
Followup-To: news.groups
Organization: GE Corp R&D Center, Schenectady NY
Lines: 17

In article <EMV.91Mar22000953@poe.aa.ox.com> emv@ox.com (Ed Vielmetti) writes:

| Given the possible (real) concern of a "comp.archives.d" turning into
| another "comp.sources.d" or "comp.sources.wanted", perhaps a different
| name (with the same charter more or less) is in order.  As a strawman
| I propose one of
| 
|   Newsgroup Name: comp.archives.admin
|   Newsgroup Name: comp.archives.managers

I think the admin is a good name. If the name should describe the topic
of the group, then the topic is administration, not the managers
themselves.
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
        "Most of the VAX instructions are in microcode,
         but halt and no-op are in hardware for efficiency"