🚀 go-pugleaf

This posting provides an introduction to the newsgroup "comp.sources.reviewed"
(CSR).  It contains a description of the group, information about the CSR
archives, and some guidelines for getting started as a submitter/reviewer.

Other information that is available includes the "Guidelines for
Reviewers" document that we use in evaluating submissions, and an Index
of sources already posted to the group.  This information is posted
occasionally to CSR, or it can be obtained via anonymous FTP from
ftp.uu.net:/usenet/comp.sources.reviewed.  Failing that, you can ask me
for the information.

People wanting to submit sources, become a reviewer, or get more
information should send mail:

	To: csr@cc.purdue.edu
	Subject: send guide

	Thanks,
	<your sig here>


What is Comp.Sources.Reviewed?
------------------------------

"Comp.sources.reviewed" is a moderated newsgroup (moderator: Kevin
Braunsdorf [csr-request@cc.purdue.edu]) with the following charter:

    Comp.sources.reviewed is a moderated newsgroup for the distribution of
    program sources that have been subjected to a Peer Review process.
    Similar to the process used for academic journals, submissions are sent
    to a moderator who then sends the sources to Peer Review volunteers for
    evaluation.  The Reviewers are asked to provided a timely evaluation of
    the software by compiling and running it on their machine.  If time does
    not permit them to complete a review, they are responsible for asking
    the moderator to select another reviewer.  If the Moderator and Peer
    Reviewers judge a submission to be acceptable, the sources will be
    posted along with the written comments provided by the Reviewers.  If a
    submission is not found to be acceptable, the author will be provided
    with the Reviewers' comments, and they will have the option of
    addressing those comments and submitting the sources again.



What are the steps of the peer review process?
----------------------------------------------

A typical sequence of events for the review of sources is:

- software is mailed to a mail-server in small (59k) shar files
- mail-server acknowledges receipt and wakes up moderator
- moderator briefly checks software against guidelines listed above
- moderator builds a Call For Reviews (CFR) and a part-0
- moderator posts CFR to comp.sources.testers
  (or if it is a patch sends mail to previous reviewers)
- reviewers volunteer for package and receive it from the mail-server
- reviewers unpack and gloss over the source
- reviewers might `nix' the package based on some obvious botch here
- reviewers build, install, run, and test the software
- reviewers return evaluations to mail-server
  (based on guidelines described an another document)
- moderator compiles evaluations and makes final publication decision
- if submission is accepted:
	- moderator discusses evaluations with author
	- moderator posts sources and evaluations
- if submission is not accepted:
	- moderator sends evaluations to author
	- moderator may suggest revision and resubmission,
	  (or posting in another newsgroup)


What if the reviewers find problems?
------------------------------------

We are discouraging making repairs to submissions during the review process.
Reviewers may contact you for information and clarification, but we do not
envision fixes being applied during the course of a review.

Once the reviews are completed, you will receive a summary from the moderator,
and, if necessary, will have a chance to make repairs to your package.


Where are the Archives?
-----------------------

The official archive site for comp.sources.reviewed is ftp.uu.net
(uunet.uu.net), and the sources are available by anonymous FTP (and
other means) in /usenet/comp.sources.reviewed.  Like most sources
groups, the archives for CSR are organized in terms of "volumes".

We have also been told that:

    The USENET archive section of the Anonymous FTP area of kirk [in
    Australia] now holds an archive of comp.sources.reviewed.  This
    archive is updated daily (i.e.  any posting will can be found in the
    archive and associated indexes within 24 hours of the news article
    being received by kirk).

    The archive is available via anonymous FTP only on kirk.bu.oz.au:
    (131.244.1.1).  Fetchfile access will be available in the near
    future.

    For more information, please contact ftp@kirk.bu.oz.au.

An alternative archive site in the USA is:

Site:         sparky.sterling.com (sparky)
Contact:      Kent Landfield (kent@sparky.sterling.com) (402) 291-8300
Location:     Omaha/Bellevue, NE
Modems:       Telebit
UUCP:         On request
FTP:          Anonymous FTP
Mail server:  NA (Yet)    
Additional:   This archive site uses Volume-Issue archiving.


How do I use that silly mail-server?
------------------------------------

Send a mail message to it like:
	To: csr@cc.purdue.edu
	Subject: help

	Thanks!
	<your sig here>

And it will send you a help file.  Here is a summary of the Subject lines
the mail-server might do something useful with:
Info commands:
	Subject: help
	Subject: index
	Subject: send index
	Subject: send guide

To get source:
	Subject: send product

To ACK or NAK and product:
	Subject: got product
	Subject: nix product

To (back out of a) review:
	Subject: review product
	Subject: drop product

To submit a product:
	Subject: submit product-version part/total


What can I review right now?
----------------------------

This is the comp.sources.reviewed index.

Name                   Parts   Size   Description
by-1.2                   1      58k   group lines
dbuf-1                   1      14k   double buffer routines
deliver-2.1-patch-11     2      11k   patch #11 to Deliver 2.1
guide-2                  4      50k   guides for reviewers and submitters
index-1                  2       5k   this index
rcinfo-1.1               6     208k   (hesiod style) network database
test-0                   1       5k   the test submission for play


What else should I do?
----------------------

Subscribe to comp.sources.testers -- we need you.

Thanks for you time and efforts!
--
Kevin Braunsdorf, csr-request@cc.purdue.edu
-- 
        Andrew Patrick acting as Comp.Sources.Reviewed Moderator
              Department of Communications, Ottawa, CANADA
                         csr@calvin.dgbt.doc.CA