Pear Comitee

It's late and I'm not really clever right now so please don't flame too much on this. I come with the idea of founding something like a PEAR Comitee (PC). Well, I know that Stig hates burocracy :) but this shouldn't introduce too much of it. The task of the PC will be to analyse and approve package submissions (and why not other conflictive desicions). For giving some ideas: 1) Anyone could take part on the comitee. Possible type of members could be (in order of relevance): Type A) Special Type B) PEAR developer who has 3 or more packages Type C) Other PEAR/PHP developers Type D) Contributor/Average user of PEAR Type E) Others 2) Memebers vote via a simple web interface (after registering) in pear.php.net. The polls could be something like so: Desicion: * Approve as it is * Approve as it is but changes requested * Reject until some change is done * Reject |__comments__| Level of knowledge of the new class: a) Read class anouncement b) Cursory review c) Deep review d) User 3) The weight of a vote is meassured in UNITS (U): 13U - Special 10U - A PEAR developer who has 3 or more packages 7U - Other PEAR/PHP developers 5U - Contributor/Average user of PEAR 4U - Others The "Level" (commented above) affects UNITS: level a) -2U level b) -1U level c) +1U level d) +2U For example a common PEAR developer who votes "Accept this class" and does a "Deep review" of it, will be given 8U == 8 votes. 4) Anyone can submit a class to be analysed by the PC 5) Times: The polls starts the day of the submision (all the members get informed then) and will be opened to votes for the next 10 days. Then it will be automatically closed and the results will be sent to the user. If it is accepted he will request his account in the PEAR web (service already avaible). 6) The maximun number of members of each type is 2*N (where N is the number of members of its superior type) starting in type B). For ex: 3B, 6C, 12D, 24E 7) Any memeber has no obligation to vote, but he will loose his PC account if doen't vote for more than three submissions. 8) The results are valid when the ...% of members had been voted. (Ouch too late, so ... to be continued... :-) Tomas V.V.Cox