Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!tinman.cis.ohio-state.edu!bob
From: bob@tinman.cis.ohio-state.edu (Bob Sutterfield)
Newsgroups: news.admin
Subject: Re: DISCUSSION - modification of charter for news.announce.newgroups
Message-ID: 
Date: 14 Aug 89 12:36:39 GMT
References: <3960@ncar.ucar.edu> 
	<1989Aug13.021012.216@utzoo.uucp> <3994@looking.on.ca>
	<1047@anise.acc.com> <4001@looking.on.ca>
Sender: news@tut.cis.ohio-state.edu
Reply-To: Bob Sutterfield 
Organization: The Ohio State University Dept of Computer & Information Science
Lines: 33
In-reply-to: pst@anise.acc.com's message of 13 Aug 89 18:46:16 GMT

In article <1047@anise.acc.com> pst@anise.acc.com (Paul Traina) writes:
   I don't see a particular pressing need for an universal announce
   group.  If it turns out that alt or bionet, or gnu need such a
   mechanism, they will create one within their own heirarchy.

At least one such mechanism already exists.  See gnu.config or
gnu.announce, depending upon whether you're talking about
announcements regarding GNU software or discussion regarding the gnu.*
heirarchy.

In article <4001@looking.on.ca> brad@looking.on.ca (Brad Templeton) writes:
   It would be nice to just get announcements, with a short 5 line
   description for each gorup, and not have to check for changes in a
   big list of one line descriptions of everything.

That's why the "diffs to alternative newsgroup heirarchies" are
posted, so it can be easily scanned.  One line can contain plenty of
information to support a decision to request a feed of the group.

I don't feel especially compelled to update the moderator of
comp.archives every time I update something in our archive here,
largely because our archive operates differently than many, and those
who use it keep themselves up to date via the normal mechanisms we
provide for them to do so.  Similarly, I don't feel any particular
need to tell news.announce.newgroups whenever a new GNU-oriented
mailing list is created with a corresponding group in gnu.*.  Sites
that get gnu.* get the newgroup as part of the normal course of life,
and the newgroup control message generally contains a description of
the group.

Call me a rugged individualist, but when I undertake activities
outside the scope of the Usenet, I don't feel the need to
automatically conform to its conventions.