🚀 go-pugleaf

Kevin W. Reed <kreed@tnet.com> wrote in article
<52c194$oj6@telesys.tnet.com>...
> If you really want to do this, you need to start from the beginning.
> 
> Create a charter for the newsgroups, their purpose, inital newsgroups,
> how new newsgroups will be added/dropped etc.

I started researching how to go about this very thing, but
I've only seen samples of how to get a new group started
under the Big 8 hierarchies.

Any advice on where to look for creating an entire new
hierarchy?  Or is it the same?

I'm trying to read all I can on how to do this before making
a fool out of myself on USENET by trying the wrong method
of creating the tucson.* groups.

> Post that to az.config and news.config and see if you get any support 
> for your idea.  You will need a site that is fairly well connected
> to start up the newsgroups and provide feeds for them until they become
> "mainstream" and get picked up by larger sites like UUNET.

I imagine StarNet or FlashNet would do that for us.  I have
accounts on both systems.

> One's that I would include would be...
> 
> 	tuc.config
> 	tuc.forsale
> 	tuc.general
> 	tuc.internet
> 	tuc.jobs
> 	tuc.test

What's wrong with using tucson.* rather than abbreviating
it to tuc.*?  Three more letters in the name shouldn't hurt
anyones system and the more explicit the better.

Any objections to using "tucson" rather than "tuc"?

> Others might not think that even that many would be necessary.

The list you have seems like a good starting point.  Need
to be careful of planning the names so that a future
levels fit in.  For example, we shouldn't create
tucson.toros, but rather tucson.sports.toros, or
even tucson.rec.sports.toros.  But lets not get
carried away at first.

	Erik