QA process

Hi, Currently there is few PEAR QA can really do besides nagging maintainers. What I envision is a system where PEAR QA has the ultimate control about how packages get listed within the PEAR services. While the maintainer maintains ultimate control over his package. However the PEAR Group can decide to revoke/add maintainership to a package (for example if PEAR QA asks for this and provide enough evidence to make this step necessary). Furthermore PEAR QA gets its own (sub)channel (once we have channel support) to publish QA releases. This is just a basic idea. I will work on an RFC to flesh these basic ideas out. 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