Re: Re: [PEPr] +1 for RFC::Prefix all classes with PEAR_
| From: | Mark Wiesemann | Date: | Wed, 04 Oct 2006 19:17:54 +0000 |
| Subject: | Re: Re: [PEPr] +1 for RFC::Prefix all classes with PEAR_ | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44329@lists.php.net to get a copy of this message | ||
Craig Constantine wrote:
> --On October 4, 2006 2:02:12 PM +0200 Mark Wiesemann <wiesemann@php.net>
> wrote:
>
>> Laurent Laville wrote:
>>
>>> A reminder is display but it seems not to be check by the Pepr System ?
>>> http://pear.php.net/pepr/pepr-votes-show.php?id=420
>>
>> AFAIR there is an exception for RFCs that the proposer may vote on his
>> proposal, for normal proposal there should be a (working) check against
>> that.
>>
>> Regards,
>> Mark
>
> can someone confirm this...
> PEPr programmatically prevents the author from voting on a proposal, except
> when the proposal is an RFC?
> (yes, I can look in the code, but I figure someone familiar with the code
> can answer off the top of their head.)
You can see the vote lock and the exception for RFCs in the mayVote()
method here:
http://cvs.php.net/viewcvs.cgi/pearweb/include/pepr/pepr.php?revision=1.66&view=markup
There was also already a discussion about this on the list, actually
initiated by myself in last December:
http://www.codecomments.com/archive219-2005-12-724933.html
Regards,
Mark