A little rant

Cheers! :) <rant> I recently took a look at some other proposal processes in other open source systems and one feature was quite impressive for me: Guiding peoples proposals. The idea is, to have someone who guides the proposal through it's way, to support the proposer and raise quality. My idea for something like that would be as follows: * PEPr-only accounts in future may only edit the proposal, not move forward stages any more. * Every PEAR-DEV may approve PEPr accounts. * The approver of an account will automatically be assigned as the "guide" for this proposal. He should keep in touch with the proposer, guide him in getting PEAR compliant, if help is necessary, moderate the pear-dev discussions,.... The guide may also move the proposal forward to the specific stages (draft -> proposal, proposal -> vote). This would bring us several benefits: a) New PEAR developers get a more personal introduction into PEAR. They know who to ask. b) The quality of the initial proposal and the first releases can be raised by far. Giving tips for petter implementations or for PEAR typical features should be the job of a guide, too. c) A big piece of pre-discussion of a package will be moved from PEPr back to the list, where much more people get involved. d) A package needs a real "friend" in the community (which is quite large by now) to act as a guide. This will reduce the amount of bull... in PEPr by far I believe. :) I made this experience recently with Kore (Image_3D). I convinced him to put the package into PEAR and we prepared all the stuff together. No complains by now. Only positive vibrations. IMO this can work for any other proposal by now. </rant> So what? ;) Regards, Toby -- Tobias Schlitt - Zend Certified Engineer GPG Key: 0xA6529579 a passion for php http://www.schlitt.info Like to say "thank you"? - http://pear.php.net/wishlist.php/toby