Re: RFC - Rules on 'Rules and Guideline Proposals. Rev.2
| From: | Klaus Guenther | Date: | Fri, 12 Mar 2004 00:12:19 +0000 |
| Subject: | Re: RFC - Rules on 'Rules and Guideline Proposals. Rev.2 | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-26318@lists.php.net to get a copy of this message | ||
Ian Eure <ieure@php.net> wrote:
> On Thursday 11 March 2004 12:56 pm, Alan Knowles wrote:
> > Ok. Final Draft (hopefully)- speak now or forever hold your peace...
> >
> Looks pretty good, but I disagree with the decision to prohibit discussion
> arising from comments made about the RFC. Or are you saying that discussion
> about comments made should be made on -dev, as replies to the comment
> notifications from PEPr?
>
> I can understand the desire to limit flamewars, but it seems like stopping
> discussion between commentors and authors is a very high a price to pay.
Then
> again, I haven't been around long, and haven't seen any of these huge
> flamewars, so...
Yeah, I have the same feeling. To be honest, I've seen a few flamewars on
here. They seem to usually be about template systems ;-) Seriously, though,
imho there needs to be room left for honest discussion (comments on
comments). Who's to say that the RFC author always gets it right? Having some
people helping him decide whether to incorporate comments or not shouldn't be
prevented.
From the thread, it seemed to me that the biggest concern about comments on
comments is that they usually go off on a tangent. While I agree that an RFC
must be the center of a focused, serious non-flamewar discussion, preventing
any sort of discussion beyond comments seems to be counter-productive.
Otherwise I think revision 2 is quite good.
Klaus