Re: [PEAR_PackageFileManager] UserGuide and Tutorial -call for comment

Greg Beaver a écrit :

Laurent Laville wrote:

For many reasons, as I've already explained in past when I wrote other manuals (in docbook format), this one will be again a standalone version. No pear doc integration. Main reason : I used all dockbook tags I want without restriction and some features that are probably not supported by pear manual architecture. But as, like other manuals I've wrote for HTML_CSS, HTML_Progress2, ... an html copy will be available with next stable release. LAST: I plan to publish the stable release 1.6.0 with a full user guide for November 21st. If someone is not agree or want to see something else in this manual, you have again 9 days.

Hi Greg

I can't support this decision. There are hundreds of grammar errors in the documentation you've written, and more than one factual error. I don't understand your point of view. Especially for two reasons :

1. I've asked your agreement to used your work one month ago 2. Of course there are some grammar errors, but remember that "Moliere" language is most easy to write for me than "Shakespeare" language ;-) 3. I asked your re-reader help one week ago and got no answer. I'd really appreciated an answer something like "I can't help you right know, but I will back to you in few days" rather than just a silence.

I don't see any good reason to avoid the PEAR manual. The thing is already in docbook! It wouldn't take long to tweak it to fix any compatibility issues encountered. If someone could do the job, I'm not against idea :

More, I'd really appreciated a reference list of dockbook tags supported. It can help myself but I think all other writers that want to help to improve the PEAR manual by their contributions. I've still in mind some tags not supported: this is why HTML_Progress2 is not part of PEAR Manual Now. And I received no mail to tell me that I 'm on wrong way or share me his help to include my work on PEAR manual

Most important, it cannot be translated or edited by anyone else as long as it it outside of CVS. On this point I agree with you, but the code is free to all that accept my effort to write it and

redistribution under the Creative Commons Attribution License.

HOWEVER, I understand and appreciate the effort you've put into this, and if you choose to publish the manual as an independent HTML document, I won't stop you. I have, however, removed myself as a developer from PEAR_PackageFileManager (marking as inactive) as I don't agree with the majority of your recent decisions, If you're against my recent decisions, I think so I should have at least a clean explain, isn't it ?

and also don't have the time to do anything about it. I hope you can understand my feeling on this issue. Greg Laurent