Re: PEAR Quality (vs. Quantity) RFC

Hi, * Wolfram Kriesing wrote: > Executive summary (what's the package about, what can it do) Then I would suggest PowerPoint as an adequate file format. :-) > * Stage 6 - UML diagrams Which impacts for real environments out there should that have? Can't see anything positive in that except gratifying theorists and managers. (I know that UML seems to be currently "hip" in the PHP scene, but IMHO it would have been better to set the guidelines on things that are usable in practice) > * Stage 7 - Design of the application > The QA team or an selected team should check a package for it's > OO-design and either suggest possible refactoring methods or approve > the high quality of the package. IMHO it shouldn't view on the OO design alone, but also on the easy-to-use APIs and perhaps on performance, if possible. Just my 0,02 EUR, Björn. -- ThinkPHP / rent-a-phpwizard bjoern@thinkphp.de Sedanstraße 27 Tel: 0931 / 78 43 804 97082 Würzburg Fax: 0931 / 78 43 795 http://www.thinkphp.de/ http://www.rent-a-phpwizard.de/