Re: 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. I'll step forward for HTML, as I'm working extensively with packages there. I haven't gotten into the templating systems, though, so I'd be happy if someone else with lots of experience there would join me. I've also worked a decent bit with HTTP, so if that's not covered, I could help there. I'm not sure about most everything else, so if someone is needed in the following, I'm ready to learn :-) - Numbers (we really need to release a new version of Numbers_Roman with a proper package.xml) - Text (btw, any reason why Text_Statistics is under structures? Oh well) - XML As for the rest, let's see what's covered and go on from there. > 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. I'll prepare a report for HTML. I know very little testing has been done. > Stuff like directory structures would also be topics (like test scripts > go in "tests", examples go in "examples" etc). Let's look at existing directory structures and modify them where needed, etc. Anyway, let's get this show on the road :-) Klaus