Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!kuhub.cc.ukans.edu!sloane
From: sloane@kuhub.cc.ukans.edu
Newsgroups: news.groups
Subject: Re: CALL FOR DISCUSSION: news.software.{transports,readers}
Message-ID: <18904.25725545@kuhub.cc.ukans.edu>
Date: 28 Nov 89 15:52:05 GMT
References: <68@van-bc.UUCP>
Followup-To: news.groups
Organization: University of Kansas Academic Computing Services
Lines: 32

In article <68@van-bc.UUCP>, jtc@wimsey.bc.ca writes:
> PROPOSAL:
> 	Merge current news.software.* groups into the two new
> 	groups: news.software.transports and news.software.readers.
>... 
> 	
> RENAMED OR REMOVED GROUPS???:
>     news.software.anu-news	VMS B-news software from Australian
> 				National Univ.
>... 	
> 
> COMMENTS:
>     This is my attempt at rationalizing the news.software.all hierarchy.
>     Constructive criticisim is welcome, flames are not.
> 
>     I can see the need for groups describing a particular implementation
>     due to limited interest, high volume, or a mailing list gateway.

Well, news.software.anu-news is a limited interest group, in that it only runs
on VAX/VMS machines.  I think there are about 200-300 sites world wide using
this package.  Leaving it in its own newsgroup lets sites that aren't
interested avoid the traffic.  It currently has about 20-25 messages per week.
It is also gatewayed to the ANU-NEWS@VM1.NODAK.EDU mailing list.  I would
rather not have to read all the news.software.b postings to see the anu stuff.
I suspect that the unix people would rather not hear about the anu problems.

Just out of curiosity, why do you think your scheme is better than the current
one?  It seems perfectly rational to me to have one group per package, so
people can find articles of interest easily.
-- 
USmail: Bob Sloane, University of Kansas Computer Center, Lawrence, KS, 66045
E-mail: sloane@kuhub.cc.ukans.edu, sloane@ukanvax.bitnet, AT&T: (913)864-0444 


Brought to you by Super Global Mega Corp .com