Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!uakari.primate.wisc.edu!indri!xanth!mcnc!decvax!zinn!mem From: mem@zinn.MV.COM (Mark E. Mallett) Newsgroups: news.admin Subject: Re: DISCUSSION - modification of charter for news.announce.newgroups Message-ID: <610@zinn.MV.COM> Date: 20 Aug 89 18:42:24 GMT References: <3960@ncar.ucar.edu> <3027@cbnewsh.ATT.COM> <415@wet.UUCP> <3978@ncar.ucar.edu> <14549@bfmny0.UUCP> Reply-To: mem@zinn.MV.COM (Mark E. Mallett) Organization: Zinn Computer Co., Litchfield NH Lines: 29 In article <14549@bfmny0.UUCP> tneff@bfmny0.UUCP (Tom Neff) writes: >One problem with restricting other-hierarchy newgroup announcements to >their own distributions (new BIONET group announcements only in >dist:bionet, new ALT announcements only in dist:alt, etc), is that >mainstream people who might well consider adding another hierarchy to >their feed (if they knew what was in them these days) won't hear about >it. >The hair splitting about "allow but do not force" is vacuous. No one >can force the alternate hierarchies to do anything. "Allow" is the only >real decision that's ours to make. The latter opinion seems to contradict the former motivation. If you can't enforce the posting of announcements as suggested, then those who want to be up to date on other group hierarchies will have to look elsewhere anyway. If it's of only marginal importance to see these announcements, that might not be a problem. But the whole point of this discussion seems to be that it *is* important to see them. I still believe that announcements belong within their own scope, regardless. -mm- -- Mark E. Mallett Zinn Computer Co/ PO Box 4188/ Manchester NH/ 03103 Bus. Phone: 603 645 5069 Home: 603 424 8129 BIX: mmallett uucp: mem@zinn.MV.COM ( ...{decvax|elrond|harvard}!zinn!mem ) Northern MA and Southern NH consultants: Ask (in mail!) about MV.COM