🚀 go-pugleaf

In article <4ipi37$23m@ns.comdial.com>, mbs@comdial.com (Michael B. Smith) writes:
|> Much local news in Charlottesville (where there are only two local
|> groups: chv.general and chv.test) is bottled up inside UVa. UVa has
|> probably over 100 newsgroups in uva.*, but refuses to allow any of 
|> them outside the campus feeds.
|> 
|> Most of the ISPs in Charlottesville have a dozen or so local
|> newsgroups. The users on the ISPs, and at least some of the
|> ISPs themselves, want more local news coverage. But UVa doesn't.

Charlottesville local news belongs in the chv hierarchy. It is small now,
but will grow now that we have these local ISPs. UVa exchanges va.* and
chv.* with two of the local ISPs, and will exchange it with any other
local ISP that wants those hierarchies.

The uva hierarchy is the UVa hierarchy -- it is local to UVa. Any business,
organization, or educational institution can have their own _local_
hierarchy. That is exactly what uva.* is. There are some very site-specific
policies that govern use of the uva newsgroups. 

The va.* hierarchy used to be almost unused, but has grown enormously in
the past year. I expect to see the same growth in the chv.* hierarchy.
News users at UVa should participate in chv.*, but it would not be
appropriate for the general Charlottesville public to participate in
the uva.* newsgroups.