Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!ucsfcgl!cca.ucsf.edu!root From: root@cca.ucsf.edu (Computer Center) Newsgroups: comp.sources.d Subject: Re: Call for discussion: comp.sources.archives Summary: The archive list should not be restricted to the sources groups. Message-ID: <1349@ucsfcca.ucsf.edu> Date: 27 Aug 88 00:26:52 GMT References: <222@pigs.UUCP> <621@proxftl.UUCP> Organization: Computer Center, UCSF Lines: 29 In article <621@proxftl.UUCP>, bill@proxftl.UUCP (T. William Wells) writes: > ... > You'll get my "yes" if it ever gets that far. It is very tedious > collecting the archive information from the various newsgroups > where it gets posted. > ... > I'd suggest two groups: comp.sources.archives and > comp.sources.archives.d The archives directory group should not be a subgroup of sources. Two other widely sought classes of archives come to mind immediately: Binaries Archives Graphics Images Archives and I'm sure there are many others. A high level group seems reasonable. It should be conspicuous to help the goals of serving a wide community and reducing wasteful net traffic. The structure of a moderated data group (where the moderator can control expiration dates for reference information) plus an associated unmoderated discussion group seems to be appropriate for this. Thos Sumner (thos@cca.ucsf.edu) BITNET: thos@ucsfcca (The I.G.) (...ucbvax!ucsfcgl!cca.ucsf!thos) OS|2 -- an Operating System for puppets. #include