Proposal for "Core_Team_Vote"

» Metadata » Status
» Description
Following the RFC on QA (see links) this proposal is for the voting of the new Core QA Team.

All PEAR-Devs wishing to become a member of the Core PEAR-QA Team should comment on this proposal with this name, and (optionally) what they feel they can contribute - information on availability is also a must - if you're only going to be available every 6th Tuesday that is a full moon, you're not going to be much use to the QA Core Team.

If you do not wish to be part of the Core QA team, please do not comment. Comments should be given on the PEAR-Dev mailing list.

You have 2 weeks from this point, upon which to add your name to this vote.

After 2 weeks, a Call for Votes will be taken.

The rules of the vote are thus:

You must vote +1, or 0 (abstain).

You must put in your vote comment upto your Top 7 candidates. You do not need to vote for 7 people.

-1 Votes will not be counted

The voting period will follow the time frames set out by PEPr (1 week, if less than 5 votes, another week is given)

If less than 7 people volunteer, all volunteers will become part of the Core QA Team, the rest of the 7 will be allotted by the Core QA Team itself.

If the 7th place comes down to a tie, all those involved will be given the opportunity to withdraw their candidancy to allow another in the tie to become part of the Core QA Team.

If this procedure still leaves us with a tie, then the 6 new Core QA Team members will vote on who should be the 7th member. A tie in this vote will then cause a vote in PEAR Group to decide the outcome.

Remember, do not comment on the proposal itself in PEPr unless you wish to nomintate yourself for the Core QA Team
» Dependencies » Links
» Timeline » Changelog
  • First Draft: 2004-05-18
  • Proposal: 2004-05-21
  • Call for Votes: 2004-06-05