Re: Re: PEPr - Automated Verification Process for the transition from DRAFT to PROPOSAL to CALL FOR VOTES
| From: | Stefano F. Rausch | Date: | Mon, 30 May 2005 09:42:33 +0000 |
| Subject: | Re: Re: PEPr - Automated Verification Process for the transition from DRAFT to PROPOSAL to CALL FOR VOTES | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37885@lists.php.net to get a copy of this message | ||
On Mon, 30 May 2005 04:00:07 +0200, Justin Patrin <papercrane@gmail.com> wrote:
Unfortunately the docs are not consistent in this respect. I have already logged a bug report (still with status open) on 22 April 2005 - see http://pear.php.net/bugs/bug.php?id=4207.On 5/29/05, Vincent Lascaux <vincent.lascaux@centraliens.net> wrote: Obviously, there should be some code that meets the CS when you call a package for vote. But I don't think this is required when changing from draft to proposal. The goal of the proposal is to retrieve some comments about the package (at least that's what I believe...). I do think that you may want to retrieve some comments without having coded anything, or having a code that does not meet the CS. The developper may not want to work on a code he already has to meet the CS if he doesn't have an idea if the package is going to be accepted or not.This is why the docs say you should mention on the PEAR list before you propose.
That way you can get a quick check on whether it's worth your time. This is *also* what the Draft phase is for. If a proposer wants some comments before they propose then they should ask the list.YEP. -- Stefano