🚀 go-pugleaf

In article <2v28s4$k3s@gazette.bcm.tmc.edu> sob@tmc.edu (Stan Barber) writes:
> Ditto for houston.* and tx.*. Consider this a yea for all those mentioned so
> far and a proposal for the following:
> 	rename houston.news -> houston.usenet.config
> 	rename tx.news -> tx.usenet.config
> 	rename tx.news.stats -> tx.usenet.config

I presume you mean tx.news.stats -> tx.usenet.stats?

> One idea mentioned (in another mail or posting) was to rename the *.test
> groups to *.usenet.test. What do you think about that?

There don't seem to be many problems with confusion over .test groups,
so I would say leave them alone unless it becomes a problem. 

Someone else suggested .announce -> .usenet.announce. I think this is
also a bad idea. The .announce name is not generally a problem as
long as the groups are moderated. .announce groups are also broader in
scope than just usenet-related announcements. They should cover local
events, meetings, and so on.

I'm worried that we're going to end up renaming all the regional foo.*
groups into foo.usenet.* at this rate. Let's keep it simple, and not try
to fix what hasn't been demonstrated to be broken.

-- 
Ty Sarna	             "Good leaders being scarce,
tsarna@endicor.com            following yourself is allowed."