PEAR QA function definiton

Hi! As we did not come on a common point on how to deal with PEAR QA issues (concerning that access level stuff), I guess we should define concrete goals for the PEAR QA. I would prefer to to make this in a defined QA core team, but since there are not enough applicants for that, we should start going along to get QA process working. Here a short summary of the functions QA should perform in PHP (in no special order). It's a very high level view on the functionality, since IMHO the concrete implementation should be done by the QA core group (as soon as defined) in cooperation with PEAR core group, to get faster results. - Check packages for: - Unmaintanedness - Standard validation (Naming conventions, Group,...) - Check releases for: - Version validation - CS validation - Availability of peripherie (tests, docs, examples,...) for defined stadia ( - Functionality) - Check bugs - Check for unmaintaned bugs - Bring developers and bug reporters in contact Feel free to add anything I have forgotten. Please see, that I did not add any kind of "task" or even "process steps" to that list and want to keep it clean of that. The discussion about that has to follow the completion (or reduction) of the list. Regards, Toby