🚀 go-pugleaf

In article <1993Jan27.155027.9777@midway.uchicago.edu>  
colin@agincourt.bsd.uchicago.edu (& Garrett) writes:
> If someone is not sure that a problem they are encountering is caused by  
a  
> bug or not, it would seem most appropriate to place the note in a  
> newsgroup dedicated to the subject (c.s.n.sysadmin, programmer, misc).   
> And since 'bug' is a catch-all category for any unexplained  
unsatisfactory  
> behavior, until the problem is resolved, almost anything is a bug  
> candidate.  (What percentage of those "I think there's a bug in gcc..."  
> notes pan out?)
> On the other hand, if something has been proved to be a bug, the most  
> suitable place for a note explaining it is probably a static locus like  
a   
> FAQ (preferably archived), rather than a forum for dynamic discussion  
like  
> a newsgroup.
> Maybe that's why posts in here have been dwindling?
> 
> colin

I'm afraid you're right. At the beginning of this group I wrote to the  
creator of it asking that some posting rules be established. I thought  
threads should be disallowed and instead a moderator ought to post  
confirmed bugs (with solutions) as determined by discourse in the other  
Next newsgroups. Your idea of a FAQ would also be required. Still I would  
like to see the bug and solution posted once. I think the problem here  
appears to be the lack of a moderator.

-----------------------------------------------------------------
Greg Colello
Carnegie Institution, Department of Plant Biology
Stanford University
gcolello@biosphere.stanford.edu (NeXT mail OK)