Article View: us.config
Article #26Re: Who is the Admin for co.*
From: Henrietta K Thomas
Date: Wed, 28 Apr 2004 07:04
Date: Wed, 28 Apr 2004 07:04
85 lines
4181 bytes
4181 bytes
-----BEGIN PGP SIGNED MESSAGE----- On Mon, 26 Apr 2004 17:31:37 -0400, AUK Registrar <cjiii@mxyzptlk.net> wrote: Why is this being posted to us.config? And who the hay is AUK Registrar? There seens to be some concern about the absentee admin of the co.* hierarchy. BillofDenver abandoned his post a long time ago, kept promising to come back, but never did. He has the PGP key, and until he lets it go, no one else can act on behalf of the co.* hierarchy. That is my understanding of the situation. <snip previous discussion> AUK Registrar wrote: >-IMO. >- >-The first order of business is to find someone that >-is nuetral or thereabouts who is willing to take over >-the Admin duties. It's not that bad, really. But it >-sounds like co.config needs a complete redo >-where it puts things into a Committee with the >-Admin sitting in the -center chair. This way, the >-only real duty of the Admin will be tie breakers >-and file the appropriate control messages >which are really just the RMgrouped messages >-and the Cmsg for new ones. The Boosters >-would also need to be done when a nutcase >-files an illegal message but that's not too often. You won't be able to do anything, IMHO, as long as BillofDenver sits in the Admin chair. The only way to overturn this, IMHO, is to get the local site administrators to assume responsibility for the co.* hierarchy. They have more clout than regular users do. >-As for getting NGs that have beem cmsged, each >-and everyone needs to contact various NewsAdmins >-that you wish it using a copy of the original Charter >-for that group. That is not up to the Admin but the >-folks that support the co.*. Well, it -is- part of the Admin's job to encourage sites to carry all approved groups, but there's nothing to stop regulars users from doing the same things. It is quite useful, in fact, to have regular users checking to be sure their service providers are carrying all the groups. Bottom line, however, is that you need to talk to local admins in Colorado and see if you can find someone who'll take over the job. It's a sad situation. I wish you luck. Followups to co.config. rule against regular users >-BTW, I am in Grand Junction and it would be nice to see a GJ NG like >-Boulder has. >- >-If anyone wishes to become the Admin, I have server space they can use >-to put the Policies, Procedures and a copy of the Charters so that >-none of us have to go to ISC for them. >- >-Just some thoughts. >- >- >- >- > -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQBVAwUBQI9UP/N+ETRZJrAdAQHFugH/ffcqaafVDDvnmv/JApNDccIYeiA7yG2C z+qch9j3Qirf8arEfGG/LFD/YjWW/1b6CFO6uDvGUzaL37PP10uAwA== =v94m -----END PGP SIGNATURE-----
Technical Details
Message-ID:
<lkju801vb6c82m0h6a3jkrhmo77pdh20b2@4ax.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!border1.nntp.ash.giganews.com!nntp.giganews.com!newspeer.monmouth.com!news.xnet.com!not-for-mailReferences:
<700e489c5115757e577e7839c0a1d5ff@news.teranews.com> <1dd8e5dc70c7e079959207384055316f@news.bubbanews.com> <03bd46e2370b57b3ddc9cdcd90086879@news.teranews.com> <e8a4a198ad6730ce27c73f110d80cc16@news.bubbanews.com> <8p2jc.837$is3.217@fe07.usenetserver.com> <e73214af42d55945d51f6ed654676298@news.teranews.com> <lrvq80d6g1c8ai621hpgg13sfftf1au5sc@4ax.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 102b80,b59f9d92a7365b73,start X-Google-Thread: fc223,2d94b1f448fa6c3a X-Google-Attributes: gid102b80,gidfc223,public X-Google-ArrivalTime: 2004-04-28 00:01:21 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!border1.nntp.ash.giganews.com!nntp.giganews.com!newspeer.monmouth.com!news.xnet.com!not-for-mail From: Henrietta K Thomas <hkt@xnet.com> Newsgroups: us.config,co.config Subject: Re: Who is the Admin for co.* Followup-To: co.config Date: Wed, 28 Apr 2004 02:04:02 -0500 Organization: XNet Information Systems, Inc. Lines: 86 Message-ID: <lkju801vb6c82m0h6a3jkrhmo77pdh20b2@4ax.com> References: <700e489c5115757e577e7839c0a1d5ff@news.teranews.com> <1dd8e5dc70c7e079959207384055316f@news.bubbanews.com> <03bd46e2370b57b3ddc9cdcd90086879@news.teranews.com> <e8a4a198ad6730ce27c73f110d80cc16@news.bubbanews.com> <8p2jc.837$is3.217@fe07.usenetserver.com> <e73214af42d55945d51f6ed654676298@news.teranews.com> <lrvq80d6g1c8ai621hpgg13sfftf1au5sc@4ax.com> NNTP-Posting-Host: d158.p1.xnet.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: flood.xnet.com 1083135681 16633 207.227.16.158 (28 Apr 2004 07:01:21 GMT) X-Complaints-To: abuse@xnet.com NNTP-Posting-Date: Wed, 28 Apr 2004 07:01:21 +0000 (UTC) X-Newsreader: Forte Agent 1.8/16.553