Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ucsd!sdcsvax!amos!hartung
From: hartung@amos.ling.ucsd.edu (Jeff Hartung)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: delays in comp.binaries.ibm.pc
Message-ID: <7524@sdcsvax.UCSD.Edu>
Date: 29 Nov 89 00:34:05 GMT
References: <1128@cirrusl.UUCP> <5558@cps3xx.UUCP> <4511@itivax.iti.org>
Sender: nobody@sdcsvax.UCSD.Edu
Reply-To: hartung@amos.UUCP (Jeff Hartung)
Organization: Univ. of Calif., San Diego
Lines: 28

In article <4511@itivax.iti.org> dhw@itivax.UUCP (David H. West) writes:
>In article <5558@cps3xx.UUCP> hendrick@frith.UUCP (Kenneth J. Hendrickson) writes:
>|I prefer rigorous testing of software, before posting it to c.b.i.p.  I
>|am willing to suffer through the delays to get a quality product, as
>|free from viruses/trojans/etc. as can be assured.  Keep up the good
>|work, Rahul, and thank you.
>
>I agree.

If the bottleneck in getting binaries posted is due to the amount of
work required (of Rahul) to adequately test the programs prior to
posting, then maybe a solution to all this would be to have additional
people test the programs, send them back to Rahul when they are done
being tested, and then have Rahul post the programs, perhaps after
checking out any things that concerned the tester.  These
"co-moderators" would follow Rahul's criteria in evaluating the code
(eg.  Does it do what it is supposed to?  Is it free from bombs,
trojans and virii?  Is it PD or ShareWare?  etc.) and he would pick
those who would do the job for him.  Requests for co-moderators would
be posted to c.b.i.p.d and replacements could be obtaqined (same
source) as needed.

Opinions?

 --Jeff Hartung--  	
 Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
 ARPA - hartung@amos.ucsd.edu          
 UUCP - ucsd!amos.ucsd.edu!hartung