PEAR documentation team?

Hi All, I'm curious to know if anyone else in the PHP community would be interested in forming a PEAR documentation team? The PEAR repository is obviously one of the strengths of using PHP as a web development language, but one of the drawbacks that I've experienced along the way with implementing and using PEAR packages is the patchy documentation that often goes no further than listing class methods with little, and more often no, accompanying practical examples and clearly written beginner-thru-advanced documentation. I have no idea if it's even sane to suggest this, but I know I've often wished that PEAR packages were more consistently documented from one package to another, and I know that I'd be willing to donate time to writing end-user documentation. Would anyone else be interested in taking this idea any further? It would obviously need some discussion regarding how best to start, what goals the team should be attempting to achieve, what base considerations would need to be met before the team could work on documenting a package, etc. Much warmth, Murray --- "Lost in thought..." http://www.planetthoughtful.org