Path: utzoo!attcan!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!bu-cs!tower
From: tower@bu-cs.BU.EDU (Leonard H. Tower Jr.)
Newsgroups: news.software.b
Subject: Re: rn/rrn patchlevels, etc.
Message-ID: <41379@bu-cs.BU.EDU>
Date: 27 Oct 89 20:47:17 GMT
References: <47.filbo@gorn.santa-cruz.ca.us> <54.filbo@gorn.santa-cruz.ca.us> <10049@ucsd.Edu> <457@laas.laas.fr>
Reply-To: tower@bu-it.bu.edu (Leonard H. Tower Jr.)
Followup-To: news.software.b
Organization: Information Technology, Boston University,
       111 Cummington Street, Boston, MA  02215, USA  +1 (617) 353-2780
Lines: 36

In article <457@laas.laas.fr> ralph@laas.laas.fr	(Ralph P. Sobek) writes:
||  In the meantime, I know of no one collecting patches or taking
||  maintenance responsibility for 'rn'.  It is essentially a mature
||  product with a few minor bugs.  Or maybe you can consider it an orphan,
||  if that makes you feel better.
||  
||  I suspect that if you were to publish bugfixes in comp.sources.bugs, or
||  put them out somewhere for FTP retrieval, people would be grateful.  
|
|I assume that there are many sites that run rn/rrn.  If so, we should
|post patchs to rn/rrn in comp.sources.bugs in order to iron out those
|"minor bugs."  I've found a number for rrn's script files: basically
|annoyances that can be gotten around, but why reinvent the wheel each
|and every time.

It would be really nice if one person became the unofficial 'official'
maintainer of rn, and:
	- either started issuing patchs from patchelevel 40
or incremented the version number and started a new patch series.
	- interface with Stan Barber to coordinate rrn/rn.
It might be wise to start from rrn and insure it builds properly for
either NNTP or spool based news systems.

Could those of you who have expressed interest, talk via e-mail and
decide who should do this.  Consider:
	- who has the most time to devote to rn maintenance.
	- who has the most experience with the rn code.
	- who has the best computing facilities.
	- who has the most stable job situtation and net access.

Good luck with keeping ego's out of the discussion. ;-}

I have most of the ad hoc patches saved, and be willing to mail them to
the designated maintainer.

thanx -len