Re: Re: jump starting the qa team

From: Date: Sun, 18 Jan 2004 20:01:10 +0000
Subject: Re: Re: jump starting the qa team
References: 1 2  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-358@lists.php.net to get a copy of this message
Greg Beaver wrote:
Great balance of control and quality, I see few things to fine-tune. Clearly lots of thought went into this :) I would change this sentence: The initial members should be determined by the PEAR Group (people interested should apply to the PEAR Group) and from then on the PEAR QA Core team should decide to add/remove people from the PEAR QA Core team by a simply 2/3rds majority vote (each vote would last for 4 weeks). to this (clarification through remove of parentheticals): Initial membership in the PEAR QA Core team will be determined by the PEAR Group. People interested in being on the core team should send an email to the PEAR Group at pear-group@php.net. After the group is formed, the PEAR QA Core team can add or remove people be a 2/3 majority vote in favor of the action. Each vote period will last for 4 weeks.
looks good
Also, in these sentences: The PEAR QA team should discussion things internally as much as possible. Generally everyone can participate in the decision making process. The members of the PEAR QA core team can act without prior discussion if they deem it necessary and the decision is time critical (for example pull a broken release). how many PEAR QA members must decide it is OK in order to act without a vote? I would say if no negative response is heard in a week, or a release is obviously completely broken (missing file, fatal error in the main file, etc.), a single member may act unilaterally to remove a release as quickly as possible. If abuse is discovered, i.e. a release was removed for other reasons, then that member should be immediately placed on a "removal from the team" vote. This should help balance any future ego power struggles :).
anyone from the core qa team can just decide on his own as this stuff needs to happen quick. for decisions that dont have to happen quick a simple majority should suffice.
When you say "everyone can participate in the decision-making process" do you mean all team members or all programmers who have an opinion, regardless of membership?
anyone who reads/writes to pear-qa gruss, Lukas

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