Xref: utzoo comp.binaries.ibm.pc.d:871 comp.sources.wanted:4903 comp.sources.d:2625
Path: utzoo!attcan!uunet!milhow1!how
From: how@milhow1.UUCP (Mike Howard)
Newsgroups: comp.binaries.ibm.pc.d,comp.sources.wanted,comp.sources.d
Subject: Re: Call for discussion: comp.sources.archives
Summary: How about indirecting the archive info?
Message-ID: <219@milhow1.UUCP>
Date: 29 Aug 88 12:31:33 GMT
References: <621@proxftl.UUCP> <231@acheron.UUCP>
Reply-To: how@.UUCP (Mike Howard) (...!uunet!milhow1!how)
Organization: Miller/Howard Investments, Malden-on-Hudson, NY
Lines: 23

How about archiving the archive info someplace and periodically
posting a listing of the archive info listings and how to get them.

The general idea seems to be to collect _all_ archive access information
in one `location'.  It should be a little more efficient to collect
the actual information at an archive site(s) and periodically post (every
two weeks?) information on how to get the archive info lists and what
lists (with revision dates) are available.

Archive maintainers would then mail their archive info to the archive
site(s) - which (should be able to) can automatically generate the
summary list.  Summary list(s) would probably have to be mailed to
some central distribution for reposting.  Anyway, this list should be
a short concise index to archive info.

BTW, I would like that quite a bit better than having the archive info 
which I don't care about cropping up in groups I am reading for `content'.

Are a there any groups which currently exist which would be suitable for
such a list - such as `comp.newuser'?
-- 
Mike Howard
uunet!milhow1!how