Re: WG: [PEAR-DEV] [Call for Votes] XML_Statistics

Alexy, Exscuse my bitching and let me intervene for a second... The point I'm trying to make is that contributing a package should require sufficient documentation, it should not be a step which is taken later, regardless of the developers reputation. As for those of us who are bitching about PEAR's pathetic exscuse for documentation, we would contribute if we could count on it being included. Remember, PEAR's other fault is that it doesn't pay attention to use submitted patches and so forth, thus there is a pluthra of patching which has never been done, some of which includes doc add-ons. I wanted access to get to HTML_BBCodeParser to patch some items and improve docs. Has anyone ever even aknowledged that inquiry? No. In addition, the developer(s) are responsible for the documentation, and are more then welcome to bring other developers solely for documentation purposes, but NO DEVELOPER should have this shitty attitude that if some one on the side line complains then they should do something about it. That attitude sucks, and that's type of BS that doesn't belong in PEAR or any other Open Source project. I'm appalled by your post, and rather disgusted at the approach a suggestion for further documentation has received. Heeaven forbid PEAR provide the type of information and documentation PHP does. PEAR to often forgets that there are begininers and newbies who want to use PEAR and should be able to. This package should NOT be accepted until the inline documentation is at least sufficient. - Stan Alexey Borzov wrote:

Hi! Katana wrote:

I don't post often here but I feel like I have to add a comment here: I'm a long time PEAR user, and I have to admit that the documentation of most packages is not as good as it has to be. I often had to dig into the code to find out what I needed. A pair of co-workers of mine keep making negative comments about PEAR mainly because of the (lack of) documentation. They even say that the best doc for PEAR is on google since there is almost no doc on the website :-/ Then I think that the documentation is almost as important as the package: without it, most standard developers will not even make the necessary research to find out if the package is good or not: they will just use another library with a documentation.

I saw a lot of people on these lists who bitched and moaned about poor QuickForm documentation, and only one of them (Keith Edmunds) came up with a tutorial when asked to contribute something himself. I suggest you either follow his example and contribute some docs to the packages you use or stop moaning. Thanks in advance.