Vote system

From: Date: Fri, 03 Dec 2004 13:56:20 +0000
Subject: Vote system
Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-2045@lists.php.net to get a copy of this message
Hi QA, First, it has certainly be discussed allready, this case just tell me. I'm afraid the proposal system is sometimes leading to hastly programming, due to the unique and brief voting period, among other... I don't ask no revolution in the [PEPr] system, just point out from stage to stage: - *Drafts*: so far no comments enable, proposer quick likes to go on the Proposal stage, apart if he/she's a clever PEAR discussion member. But Draft should be the real prototyping/analysing stage - *Proposal*: it's giving some instant discussion, developers as they are kind, think people have time... A key is certainly for them to quick answer requests and periodicaly ask for comment in this stage. Unfortunately, it's too often a very quite period, no discussion and developer just champs his bit. Then after a while he says "OK, no complaint ... let's go to the vote" - *Vote*: Case it's well known, discussed or karmaid, come quick on release. Some interessant cases lead to direct discussions and adaptations, that's real life. Just it can also lead to hastly re-programing -enginering Some don't give no reaction, can even lands on "last call". The acceptance can get thru desperate recalls. Again, I totally agree on the voting system, it's cosy to be sure other people agree the pckg before it comes in magazine. I believe the system should provoke to more discussion in the right phases: - Present a digest about what's currently (should) in discussion. - Watchers should never hesitate to tell the proposer he should withdraw, re-examine the stuff and make a new proposal - Have a first go to vote acceptance phase: so the proposer can cumulate a litlle karma delegation before start the votes (simply have 2 or 3 returns from members before switch to vote) - ... OK, I understand it was too long, bye. -- bertrand Gugger (toggg)

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