Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site leadsv.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!hao!noao!amd!amdcad!cae780!leadsv!morse
From: morse@leadsv.UUCP (Terry Morse)
Newsgroups: net.news.group,net.micro.mac
Subject: net.sources.mac
Message-ID: <677@leadsv.UUCP>
Date: Tue, 5-Nov-85 20:21:41 EST
Article-I.D.: leadsv.677
Posted: Tue Nov  5 20:21:41 1985
Date-Received: Fri, 8-Nov-85 21:11:25 EST
Organization: Lockheed, Sunnyvale CA
Lines: 28
Xref: linus net.news.group:3713 net.micro.mac:3311

Let's all stop complaining about the volume in net.sources.mac and start
seriously discussing what to do about it.  Here are my two cents:

1) Establish a small group of geographically distributed sites willing to
distribute Mac source (Mac backbone sites, if you will).  Those sites
interested in Macs would be the likely candidates.

2) Someone who has a program to contribute mails it to his nearest backbone
site.  If the code is not a duplicate, the backbone site passes it on to
the other backbone sites.

3) After the program has been checked out, an abstract is distributed on
net.sources.mac (or some other name) along with a list of backbone sites
where it may be obtained.

4) Persons interested in getting the program mail a request to the nearest
backbone site, specifying source code or binary.

Is this a workable solution?  Answering requests at the backbone site could be
automated with a bit of software.  Feel free to comment on this plan.  I have
Aztec C and would volunteer to compile and evaluate any Aztec C code.

I seem to recall that this was the way the uucp map was distributed for a
while.  Does anybody know how well that worked?
-- 

Terry Morse  (408)743-1487
{ amdcad!cae780 } | { sun!sunncal } !leadsv!morse