🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: co.config
Article #64

Re: Who is the Admin for co.*

#64
From: Admin
Date: Mon, 26 Apr 2004 07:45
95 lines
4744 bytes
"kingfish" <spam_trap_void@yahoo.com> wrote in message
news:8p2jc.837$is3.217@fe07.usenetserver.com...
> <added news.groups>
>
> Please see co.config for background.
>
> co.* is in need of an admin as it has been abandoned for a couple
years and
> admin duties need to be accomplished by someone.
>
> read on:
>
> "NotBill" <me@privacy.net> wrote in message
> news:e8a4a198ad6730ce27c73f110d80cc16@news.bubbanews.com...
> |
> | "Admin" <admin@i70west.com> wrote in message
> | >
> | > "NotBill" <me@privacy.net> wrote in message
> | > >
> | > > "Admin" <admin@i70west.com> wrote in message
> | >>>
> | > > > Just wondering, who is the Admin or Maintainer for the Co.
> | > Hiararchy?
> | > >
> | > > I tried to find (e-mail) billofdenver.
> | > > He was posting through rmi (I believe) and now that
> | > > directs to Earthlink.
> | > >
> | > > Got "permanent error" messages for all the below:
> | > > billofdenver@usa.net
> | > > billofdenver@earthlink.net
> | > > billofdenver@flashmail.com
> | > >
> | > > Next step, I assume, would go to this group
> | > > 'news.groups'
> | > > and ask what to do next about this now
> | > > unmanaged hierarchy.
> | >
> | > Now it all makes sense.  There is no Administrator at this time.
Wow,
> | > no wonder some think they can run roughshod.
> |
> | Don't know what you mean by roughshod.  But people should follow
the
> | charter of the groups.  Whether it be in co.* or alt.* or any
place on
> | usenet.
> | Does something need to be changed?  A new group added?  Or?
>
> 1. Charter needs an update and clarification to reflect changes in
the
> Usenet environment since it's last update in 1999. Since the
creation of
> co.ads, co.cos.ads, etc there is no need for advertising in the
discussion
> groups.  "for sale" notices are being improperly placed in
co.general, and
> while this may not seem like such a terrible thing, it is inviting
the mass
> spammers to advertise in the discussion groups as well.
>
> 2. Yes, new groups need to be created.  co.durango.general &
> co.grandjunction.general in particular.  I believe the grandjunction
folks
> gave up a year or so back as there was no admin to do it.  That's a
shame.
> Boosters should be being sent. An "official," news admin with a pgp
key on
> file to complete admin duties in accordance with Usenet tradition,
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.

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.*.

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.
Technical Details
Message-ID: <e73214af42d55945d51f6ed654676298@news.teranews.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!news-feed01.roc.ny.frontiernet.net!nntp.frontiernet.net!news.webusenet.com.MISMATCH!chi1.usenetserver.com!news.usenetserver.com!newsfeed-east.nntpserver.com!newsfeed-west.nntpserver.com!hub1.meganetnews.com!hydra.nntpserver.com!nntpserver.com!news.teranews.com!not-for-mail
References: <700e489c5115757e577e7839c0a1d5ff@news.teranews.com> <1dd8e5dc70c7e079959207384055316f@news.bubbanews.com> <03bd46e2370b57b3ddc9cdcd90086879@news.teranews.com> <e8a4a198ad6730ce27c73f110d80cc16@news.bubbanews.com> <8p2jc.837$is3.217@fe07.usenetserver.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fc223,2d94b1f448fa6c3a
X-Google-Thread: f9437,a6bce9fa42aabc24
X-Google-Attributes: gidfc223,gidf9437,public
X-Google-ArrivalTime: 2004-04-26 00:51:23 PST
X-Abuse-Report: abuse@teranews.com
Message-ID: <e73214af42d55945d51f6ed654676298@news.teranews.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!news-feed01.roc.ny.frontiernet.net!nntp.frontiernet.net!news.webusenet.com.MISMATCH!chi1.usenetserver.com!news.usenetserver.com!newsfeed-east.nntpserver.com!newsfeed-west.nntpserver.com!hub1.meganetnews.com!hydra.nntpserver.com!nntpserver.com!news.teranews.com!not-for-mail
Date: Mon, 26 Apr 2004 07:45:00 GMT
Lines: 100
From: "Admin" <admin@i70west.com>
Newsgroups: co.config,news.groups
References: <700e489c5115757e577e7839c0a1d5ff@news.teranews.com> <1dd8e5dc70c7e079959207384055316f@news.bubbanews.com> <03bd46e2370b57b3ddc9cdcd90086879@news.teranews.com> <e8a4a198ad6730ce27c73f110d80cc16@news.bubbanews.com> <8p2jc.837$is3.217@fe07.usenetserver.com>
Subject: Re: Who is the Admin for co.*
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409