Re: *friendly reminder*: package docs: PEAR manual or maintener website version ?

On 8/20/2005 9:55 AM, Laurent Laville spake the following words: > Laurent Laville wrote: > >> I've a general question about user-end documentation. >> >> If, as its my own case, produced a full guide on my website, >> available to view online and download, and part of it on the PEAR manual. >> >> What is the best way ? >> 1. keep the API doc on pear manual >> 2. remove API docs on pear manual >> 3. make a restrictive mix of both : because pear manual could not >> accept all features included in my Guide ( i think to images / >> screenshots ) >> 4. other ? [explains please] >> >> >> Laurent > > > Without no feedback, i don't think i'll continue to maintain > my pear doc manual part, and my contribution will stop here. > > I think, as lot of people, that user-end docs is the poor parent of PEAR > packages. Lot of them are missing, (does not exists), but when something > is done, there are no feedback. > > The future of PEAR docs is really compromised in such conditions. > Why don't you set that as the package homepage? Should work :) Klaus