so lets get going

Hi, so folks lets start thinking about qa'ing PEAR. My suggestion would be that we find 2 people that take responsibility for each category. These people should be familiar with each package in their category. What would also be interesting then would be to get some data about our status quo. That is what sort of testing, docs etc do we have today. Stuff like directory structures would also be topics (like test scripts go in "tests", examples go in "examples" etc). Also the qa team could work up proposals about naming conventions of methods (although I would say the final decision on this sort of thing should be with the pear group). Finally the qa team should think up and assign tasks and tools that are needed the qa more efficiently. Etc ... 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