Re: [Fwd: [PEAR-QA] A little rant]

Hi Arnaud Limbourg! On 07/08/05 09:12 you wrote: I'm cc'ing pear-qa for getting this to public. :) > Those ideas sound good but it's not a <rant>, it's a proposition to > improve on > the current state of affairs :) Of course it is. :) As I started it should just become a rant on the idea. By now I think it can really be a solution. :) > Comments below, >> 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. > Minor mods and rephrase > quite impressive *to* me > The idea is to have someone who acts as a guide, advice and help the > proposer > throughtout the entire proposal's lifespan. An improvement in proposals > quality > should result from this. Sounds good. :) >> 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. > Comment: > More than approve it should be "I want to become a mentor/guide" of this > proposal. A first proposal draft may be terrible but the basis sound so you > don't "approve" in its current state but you see the potential and want > to help > the proposer. Yeah, you're right in some way. But I think that the acceptance of becoming a guide for a proposal should be bundled with the approvement of a PEPr account. That way, we save 1 step work for the group and only people get a PEPr account, who have a guide for their proposal. :) > I think terms are very important. "Approve" has a meaning of control, as > if we > were the final authority. It is important to me that we stress out the > fact we > are just here to help and advice. Ack. > Rephrase: > Every pearweb account holder will be able to become the "guide" of a > proposal. Ack. >> * 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). > Rephrase: > As a guide your role will be to help and advice the proposer. You will be > assigned as the proposal's guide, giving you the ability to change the > state of > the proposal. You will have to keep in touch with the proposer, > explaining to > him PEAR specifics (like Coding Standards) and give tips for better > implementations. You will also answer questions the proposer may have > and does > not want to ask on pear-dev list. If needed you will act as a mediator > on any > relevant discussion happening on the list. Yeah, what I wrote was just for internal use at the QA list. The (maybe) resulting proposal should be phrased much better. :) >> This would bring us several benefits: >> a) New PEAR developers get a more personal introduction into PEAR. They >> know who to ask. > Typo: > introduction *to* PEAR. Thx! :) >> b) The quality of the initial proposal and the first releases can be >> raised by far. > Rephrase: > The overall quality of the initial and first releases can be raised with > this > system. > Comment: > I moved the other sentence in the paragraph about the guide's role. Ack. :) >> 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. > where more people can get involved. (no need for the much) >> 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. :) > A package needs a "friend" in the community (which is quite large by > now) to act > as a guide. Just to line that out again: I do not mean a friend of the proposer personally or similar. What I mean by this is, that the proposer has to find someone inside the community who will guide his proposal, so, this person is most likely someone who "likes the idea", not a personal friend of the proposer. :) >> 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. > Only positive vibes. (not vibrations :) Ok. :) > I believe this can work for every proposal. > Drop the </rant> :) Done. :) Thanks for the feedback! :) 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