Xref: utzoo comp.sys.mac:16503 news.admin:2312
Path: utzoo!attcan!uunet!ccicpg!felix!dhw68k!bytebug
From: bytebug@dhw68k.cts.com (Roger L. Long)
Newsgroups: comp.sys.mac,news.admin
Subject: Re: some (should-be) ground-rules for submissions to comp.binaries.*
Message-ID: <8297@dhw68k.cts.com>
Date: 25 May 88 07:01:00 GMT
References: <2689@utastro.UUCP> <699@lakesys.UUCP> <307@spt.entity.com>
Reply-To: bytebug@dhw68k.cts.com (Roger L. Long)
Organization: Wolfskill residence; Anaheim, CA (USA)
Lines: 47

In article <699@lakesys.UUCP> macak@lakesys.UUCP (Jim Macak) suggests
standardizing using StuffIt for packing/compression.

In article <307@spt.entity.com> gz@eddie.mit.edu (Gail Zacharias) objects:
>In order for you to use this "freebie", the contributor has to use StuffIt
>for encoding.  This pretty much excludes people like me, who oppose shareware
>on principle, from contributing.

Actually not.  That's the job of the moderator.  People could contribute
stuff in just about any reasonable form that I could figure out how to deal
with, and I'd repackage things into the "standard" form here.  An there is
a public domain (at least for UNIX) un-StuffIt package, so no reason to 
even USE the shareware package if you don't care to.

What matters most (to me) for submitting things to comp.{binaries,sources}.mac
is that 

  -  the submission gets here intact
  -  it is real obvious who the submitter is (i.e. name, email address,
     organization, all the stuff that makes up an article header).
  -  if there is a version number, it'd be nice if you'd include that in
     the header, since one complaint a number of people have is being
     aware of what version something is, so they don't have to download
     it to see if it's an updated version of something they already have.
  -  Documentation, if provided, is TEXT or MacWrite, since these seem
     to be most standard.  Besides, I don't personally have every
     Word Processing package available, so I can't check out documentation
     that comes in other flavors.
  -  You write a paragraph or so explaining what you are posting (yes, I
     take a look at what's posted, but have better things to do than
     write a description for something that YOU felt was worth posting).
     Remember, in this paragraph, you want to convey enough information
     to the people who receive the article to give them something by which
     they can decide if they want to spend their time downloading it.
     Let people know if documentation is included.  If something will only
     work on a Mac II, let people know that in the text description, so
     that people with Mac SE's don't waste their time downloading something
     that has no hope of working on their machine.  If it requires the
     latest version of the system software, let people know that so they
     will understand why things don't work on their machine if they're using
     old software.

Thanks.

-- 
	Roger L. Long
	dhw68k!bytebug