Re: PEPr - Automated Verification Process for the transition from DRAFT to PROPOSAL to CALL FOR VOTES

On Mon, 30 May 2005 01:04:47 +0200, Alan Knowles <alan@akbkhome.com> wrote:

Comments inline...

IMHO the check can be performed via respective added functionality to PEPr: a link checker as well as with PHP_Beautifier (is the output of PHP_Beautifier identical with the original source code?) - just a very simplified solution, to be elaborated on.

The simplest way may just be to have a checkbox with the wording [x] "I have read throught PEAR's CS, and as far as I understand, this code complies to it" - that if not checked, then upgrading the status would not be possible..

A good compromise to start with, which would "morally enforce the commitment" of proposer to deliver Good Looking Code (TM).

Checking remote code seems a little risky/load intensive..

I would be prepared to offer my resources for the checking of the "terms & conditions".

PEAR Devs would then not to have to request again and again all this mandatory minimal conditions to be met.

You mean we have to add more constructive comments ;)

Is it not annoying to ask for what should be obvious?

Furthermore, I suggest that PEPr should reset the status of all "Proposal"s older than 3 or 6 months (?) automatically to "Draft", so to clear this list. A notification to the proposer should be sent by e-mail accordingly. No need for the PEAR Core-QA to respectively comment the proposal or to contact the proposer by other means.

+1 here I hope that also meant your volunteering to make the changes.....

Have I not been clear enough? ... ;) Sure!

Regards Alan

All the best -- Stefano