Xref: utzoo comp.sys.ibm.pc:20666 comp.binaries.ibm.pc.d:1236
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!batcomputer!sun.soe.clarkson.edu!nelson
From: nelson@sun.soe.clarkson.edu (Russ Nelson)
Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc.d
Subject: DESCRIBE.TXT
Message-ID: <1565@sun.soe.clarkson.edu>
Date: 28 Oct 88 16:15:29 GMT
Reply-To: nelson@clutx.clarkson.edu
Organization: Clarkson University, Potsdam, NY
Lines: 20

I am going to start putting a file into all of the .arc files that I maintain
that describes the package.  The first line will contain the "short"
description, which will always be less than 45 characters.  The remainder
of the file will be a verbose description of the package, but will always
be less than ten lines long.  The name of the file will always be DESCRIBE.TXT.
The description will be of benefits to the user, not features of the package.

I would appreciate any help I can get in this effort.  For example, if you
have posted something to comp.binaries.ibm.pc, please write the DESCRIBE.TXT
file for it, and I will retroactively stick the description into the .ARC
file.  Furthermore, if you have a favorite package I would enjoy receiving
a description of it.

This will have obvious benefits for both sysops and users.  Users who upload
will not have to describe their files, and sysops will have a ready-made
description.
-- 
--russ (nelson@clutx [.bitnet | .clarkson.edu])
To surrender is to remain in the hands of barbarians for the rest of my life.
To fight is to leave my bones exposed in the desert waste.