Re: A little rant

From: Date: Thu, 07 Jul 2005 22:57:11 +0000
Subject: Re: A little rant
References: 1  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-2786@lists.php.net to get a copy of this message
On Fri, 08 Jul 2005 00:39:46 +0200 tobias@schlitt.info (Tobias Schlitt) wrote: > 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. Bad idea, there is some people smart enough to decide out there. > * Every PEAR-DEV may approve PEPr accounts. PEAR Dev approve proposals, it works well when they read them before the voting phase (the fact that many wait the voting phase to give comments is another problem). > * 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). Good idea, but does not work out. You cannot force affiniities. Direct contact works out of the box, for example, I'm helping these days 3 people to propose their first packages. A nice and well wroten notice telling how to ask help or support on a proposal could be enough. The ways to ask exist, mailing list, irc, contact form on pearweb. > So what? ;) I see your idea as an expensive godfather principle. Leave the new comers to choose a godfather to help/support/second the proposal or to got alone could be enough. Short version: KISS Regards, --Pierre

« previous php.pear.qa (#2786) next »