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

Comments inline... > PEPr should be enabled to do the following: allow the status' change > from "Draft" to "Proposal" and from "Proposal" to "Call for > Votes" > *only*, if (1) at least the following links are available: PEAR > package file (.tgz), one or more Package source file (.phps/.htm) and > Package documentation (API) (2) the source code presented complies > with the PEAR CS. > > 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.. Checking remote code seems a little risky/load intensive.. > > 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 ;) > 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..... Regards Alan > -- > Stefano F. Rausch (http://pear.php.net/user/sfrausch) has initiated > the call for votes on > Tools and Utilities::ScriptReorganizer. Voting Will End: 2005-05-31 > 08:00 UTC. > > Please review the proposal and give your vote here: > http://pear.php.net/pepr/pepr-proposal-show.php?id=247 > -- Alan Knowles <alan@akbkhome.com>