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

On Sun May 29, 2005 at 09:0146PM +0200, Stefano F. Rausch wrote: > 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. 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. > 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. > > What are your feelings about it? I like them. - Martin