Re: [PEPr] Call for test on new proposal system

Hi, great news ! here are my remarks New package proposal Package describtion should be description ;) The package dependencies (list). Instead of a textarea could it show a checkboxes list of all the packages since they are in the database, right ? Having a textarea is just asking for typos. Seeing that they can also be external libs, it hink there should be two lists. One as pear packages dependencies where you check the packages, and a free textarea for anything else. Does that make sense ? Arnaud. Tobias Schlitt wrote:

Ladies and gentlemen, I'm proud to present PEPr (pronounced like 'pepper') to you. I'd like to beg you for extensive testing and feedback on it. You can find the application here: http://preview.pear.php.net You should be able to logon to this system using your normal PEAR Website account. After login you have 2 new menupoints central on the main page, called "Browse proposals" and "New package proposal" to use the new system. ----------------------------------- Some general info before you start: ----------------------------------- What is PEPr? ------------- PEPr (pronounced like the hot spice 'pepper') is the new proposal system for the PEAR Website, which should optimize the package proposal process for the pear community (as described here: http://pear.php.net/group/docs/20030904-pph.php). PEPr is fully integrated into the PEAR Website. The acronym means something like "_PE_AR _Pr_oposal system". How do I use PEPr? -------------------- Usage of PEPr is pretty easy. Just goto the PEAR Website and log on using your normal username and password (for proposal viewing, no logon is required). You have 2 new menu items in the central main menu called "Browse proposals" and "New package proposal". Hit one of them. The usage should then be more or less selfexplained. What is the proposal process like? ---------------------------------- A new proposal has to go through serveral stati to become accepted or declined. First status is "Draft", which means, you have created your proposal on pearweb but hdo not have proposed it officially to PEAR developers mailinglist (pear-dev). Next status is "Proposal". This status can be achieved by editing your proposal and checking the very last checkbox, before you save. This checkbox will result in an automatic email to the PEAR developers mailinglist where the developers get 1 week (7 days) to discuss your proposal. You have the possibillity to edit your proposal at any time during this phase, what will result in an update email to pear-dev. After 7 days of proposal time you get the chance to call for votes on your package. For that you have to select a similar checkbox on the edit page as described before. After you pushed your proposal into call-for-votes state, you do not have the chance to edit it again. An automatic proposal email will be send to pear-dev and developers get the abillity to give their vote online. The general vote-time is 7 days. If there are not enough (5) votes after that, the vote time automatically gets longened by the system for another 7 days. This happens always once. After 14 days of vote time without enough votes your package gets declined. If there are enough votes after 7 or 14 days, these votes are summarized and the result is automatically interpreted as a decision ( sum > +5 == accepted ). FOR TESTING PURPOSE THE PROPOSAL AND VOTE TIMES HAVE BEEN SET TO 1 HOUR. Any questions left? ------------------- Are there any questions regarding PEPr? Ask them here! You found a bug? Please report it in the bug database: http://pear.php.net/bugs/report.php?package=PEPr Happy testing! Regards, Toby