Re: Is your package really documented? The truth

<gurugeek@php.net> wrote : >> I think it is time to realize that the problem is not the format but >> the >> interface. Use whatever you want to store the data, whether it is >> docbook or >> reSt, who cares, but provide an interface that works, that's easy to >> use, >> that allows WYSIWYG like editing and where you don't have to wait a >> whole >> week to see you made something wrong. > > This is exactly what I proposed as an alternative, do it on a wiki > (which fits the bill of an easy to use, WYSIWYG editor, and don't have > to wait a whole week) > and I will take care of the docbook deal. David, The fact that you are working on writing missing documentation is very good, that's not what I am worried about. It is also great that you are volunteer to convert wiki written documentation to docbook. But I think that's maybe relying on you too much and one of these days, you might be too busy to take care of that, especially with 139 (and more coming) missing docs. So at the moment, I see your solution as a placebo to a bigger problem. If in the end everything is written in the wiki, then why not use the wiki directly ? IMO, a specialized CMS is the solution. Unfortunately, this does not exist yet. Bertrand Mansion Mamasam