jump starting the qa team
| From: | Lukas Smith | Date: | Sun, 18 Jan 2004 17:05:07 +0000 |
| Subject: | jump starting the qa team | ||
| Groups: | php.pear.qa | ||
| Request: | Send a blank email to pear-qa+get-356@lists.php.net to get a copy of this message | ||
Hi,
here are my thoughts of how the QA team is supposed to work within the PEAR project.
There will be a system of checks and balances to ensure that the interworking of the individial maintainers, the PEAR Group and PEAR QA provides optimal results in terms of features and quality. The idea of these regulations are to give each group of people a defined set of rights for extreme cases. Generally people should of course simply work cooperatively to resolve issues. For example generally the QA team should send their patches to the maintainers and generally maintainers should listen to the proposals send to them by the QA team.
For these extreme cases the rights are as follows:
1. Every maintainer has full control over his package within the bounds of the PEAR CS.
2. PEAR QA has full control (this includes removing the package from the main index(*) all together and also includes adding notes to the package homepage) over how packages are listed in PEAR web and my make QA releases (by creating a CVS branch) or pull releases made by the maintainer
3. PEAR Group has the ability to veto PEAR QA and remove/add maintainers if it feels necessary
(*) The main index is what you see as default in the browser. Packages moved out of the main index and will then only be visible if you search for them explicitly or check the necessary options in the search form. The same could be done to the listing shown in the pear command. The basic idea here is that unmaintained, orphaned, deperecated etc code will always be reachable for those who know about the package but will be invisible for those that dont in order to (temporarily) phase out the use of that package.
Membership:
Anyone can contribute to the PEAR QA team, however only a limited amount of people will be allowed to vote, make QA package releases. This group of people will be the PEAR QA Core team. 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).
Internal decision making:
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). If no decision can easily be found that way the PEAR QA core team can hold a simple majority vote to find a decision.
regards,
Lukas Smith
smith@backendmedia.com
_______________________________
BackendMedia
www.backendmedia.com
berlin@backendmedia.com
Linn Zwoch Smith GbR
Pariser Str. 44
D-10707 Berlin
Tel +49 30 83 22 50 00
Fax +49 30 83 22 50 07