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 20:30:09 +0000 |
| Subject: | Re: PEPr - Automated Verification Process for the transition from DRAFT to PROPOSAL to CALL FOR VOTES | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37898@lists.php.net to get a copy of this message | ||
On Mon, 30 May 2005 16:43:08 +0200, Martin Jansen <mj@php.net> wrote:
On Sun May 29, 2005 at 09:0146PM +0200, Stefano F. Rausch wrote:Following what Alan has thought of, a checkbox for marking the proposal a "non-code" one could be added to PEPr, which would/could prevent the "checking". Furthermore, the addition of "code links" should/could then be disabled, to further cement the special type of proposal in discussion. -- StefanoPEPr 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.While this sounds sane, we should keep in mind that sometimes proposals are handled in PEPr that do not deal with code, but with guidelines for PEAR. (E.g. Daniel's recent RfC for the header comment block format.) Thus we need to make sure that there is a way to circumvent the above mentioned requirements for such proposals.