Xref: utzoo comp.sys.ibm.pc:13063 comp.binaries.ibm.pc:511
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!uvaarpa!mcnc!decvax!decwrl!sun!aeras!richard
From: richard@aeras.UUCP (Richard Karasik)
Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc
Subject: Re: Moderation...
Message-ID: <125@aeras.UUCP>
Date: 10 Mar 88 17:32:51 GMT
References: <1424@polyslo.UUCP> <149@tscs.UUCP>
Reply-To: richard@aeras.UUCP (Richard Karasik)
Organization: Arete Systems, Inc. San Jose, CA.
Lines: 33
Keywords: ok, definatly time for it...

[STUFF DELETED]
.If there are any serious potential moderators out there, here are a few
.features that I would like to see:
.
.	* A standardized header for postings including:
.		1. Program Name
.		2. Version Number of Revision Date
.		3. Author Name and Address
.		4. Program Clasification (System Utility, Communications,
.		   Business, Text Processing, etc.)
.		5. A Source Code Included Flag
.		6. A four to six line description of the program that is
.		   not burried in a README file and especially NOT UUENCODED
.		7. Hardware Requirements
.		8. Software Compatibility (DOS, UNIX SV, UNIX BSD, etc)
.
.	* A cataloging program that can read through headers with the
.	  afore mentioned information that can print out a cross reference
.	  list.
.
.	* A standardized multi-system compatible archiving format such as
.	  ARC.
.

In addition - the standard header should have VOLUME: etc so that
standard archiving programs that grab stuff out of various places
like comp.sources can be "slightly" modified (I emphasize slightly)
to grab stuff out of here and archive it automatically. 

Whoever moderates might want to contact the moderator
of comp.sources to see why the headers were set up that way.

Sorry for the extra chit chat -but no x.x.x.d group yet.