From: weiner@terminator.cc.umich.edu (Jeff Weiner)
Subject: uploading to atari archive and c.{b,s}.a.st
Keywords: the pope bart atari archive umich edu umich atari posse 
Organization: University of Michigan
Date: Tue, 29 Sep 1992 16:06:09 GMT

		
		Uploading to Atari.archive.umich.edu
				  and 
             Posting to comp.{binaries,sources}.atari.st
                By Jeff Weiner, Atari.archive Guardian 


How to upload to atari.archive.umich.edu:

There are two main ways to upload to the archive: FTP or mail 

1: FTP - This is the preferred method, as it doesn't clog my mailbox with
   megs and megs of stuff, not to mention it's a bit easier for you too.
   Logon to the archive as usual, then issue the following commands
   
   cd ~atari/New
   type binary
   put filename.ext
   mail weiner@atari.archive.umich.edu .... "Hey Jeff, I just uploaded this..."

   This last step is very important.  As we're now integrating the 
   index with text and the ls -lR listing, descriptions and an address to
   send questions to are key.

Ed Krimen, ekrimen@ecst.csuchico.edu, adds this:

For those that may not know, may I add that, for aesthetic effects,
if you enter "hash," before you "put filename.ext" or "get
filename.ext," the ftp program will display a # for every 1024 bytes
sent or received.  Actually, when you 'put' a file, it will display
bunch of # at once.  Moreover, if you enter "bell," it will sound your
system bell when a function has completed.  Finally, you can send and
receive a list of files using the "mput" and "mget" commands,
respectively, with a list of the files after the command.


2: MAIL - This is a bit slower for you and for me, but is still very effective.
   Simply uuencode the file, (please split it into parts ~=60 K or less please)
   and mail the result to weiner@atari.archive.umich.edu.  Please name
   the parts in the subject line.  This is really helpfull as the parts
   usually don't arrive in the proper sequence. Also, please include a 
   message labeled file transmission, containing a short description of 
   the file, etc.  Shar files are also acceptable, but I prefer the uuencoded.


And for those of you who would like to see your binaries and sources appear
in comp.{binaries,sources}.atari.st, the following is taken from Steve
Grimm's Introduction to Binaries and Sources:

Subject: Submitting binaries for publication

Items intended for posting or queries and problem notes should be sent to
atari-binaries@spud.Hyperion.COM. If you are on a UUCP-only site, you
can send them to {backbone}!spud.hyperion.com!atari-binaries.

If you want verification of arrival, so say in a cover note, or at the
beginning of your submission, if it is small.  I try to verify that a
program works, and if I can't get it to work, I may hold up posting it
for a couple of days.  Please note that, except in rare cases, software
without documentation will not be published. The backlog from receipt
to posting varies from one to four weeks depending mostly on the set
of submissions currently in my queue.

If you are submitting both sources and binaries, PLEASE send the two
separately.  If I have to separate your sources from your binaries by
hand, your submission will most likely sit on the back burner for a
while.

Also, as of volume 8, I will only accept binaries packed with an archiver
for which source code is widely available.  For the time being, this pretty
much means arc, zoo, and lharc.  If you want to use a nifty new archiver,
make the source code available to the public (posting to comp.sources.atari.st
is fine.)  I reserve the right to repack binaries with another archiver if
the other archiver saves a significant amount of space, or has other
advantages.

If you're submitting a demo of a commercial program, or a shareware program,
please keep the amount of advertising to an absolute minimum.  The net
gods become angry when people try to use the net as a free advertising
medium, and I'd like to keep comp.binaries.atari.st out of trouble.  If
you want to solicit orders, do it in a README file or an About... dialog
box, not in a message that comes up every time the user does something.
In other words, treat the net like a PBS station (apologies to those
outside the US.)  I will not accept programs which I feel are excessively
commercial.  I'm aware that commercial demos and shareware are often very
useful (to the users on the net,) which is why I allow them at all.



Subject: Submitting source for publication

Items intended for posting or queries and problem notes should be sent to
atari-sources@twitterpater.eng.sun.com. If you are on a UUCP-only site, you
can send them to sun!twitterpater.eng!atari-sources.  

If you want verification of arrival, so say in a cover note, or at the
beginning of your submission, if it is small.  I try to verify that a
program works, and if I can't get it to work, I may hold up posting it
for a couple of days.  Please note that, except in rare cases, source
without documentation will not be published. The backlog from receipt
to posting varies from one to four weeks depending mostly on the set
of submissions currently in my queue.

I prefer that you submit sources and binaries separately, as it's a
pain to separate them, and such submissions are invariably placed on
the back burner.  Sources should be submitted in the same format as
binaries -- uuencoded arc, zoo, or lzh files.  Please use Pierre Dumas'
"uue" program if possible, as it can correct some common transmission
errors.  Split long submissions up into reasonable (less than 50K)
chunks.  "uue" will do this for you, if you use "uue -700 file" to
encode.

Please inform me of any special system requirements, and what development
environment was used, so that I can properly test your submission and
label it when I post it.

-------------------

weiner
-- 
Jeff Weiner  - jweiner@umich.edu - weiner@atari.archive.umich.edu -
414 Erie St. SE, Minneapolis, MN 55414
Now at the University of Minnesota