> > To clear this up, does that mean that you'll volunteer in doing this
> > cleanup? ;)))
>
> Not alone.
>
> To be precise, I can
> physically move the files (except ZentAPI for the moment), and
> move the 3 parts from the manual into the new document (adapting the
> build system from a local point of view)
The ZendAPI doc is in CVS now. The problem with it is that there
is no support for translation and AFAIK they use a separate build
system... Zeev noted, that this was the previous decision of putting
the docs there, because the ZendAPI can be independent from PHP
(eg. used in MySQL stored procedure executor code).
> But I need also help, e.g.:
> - a decision from the group how it should be published (like phpweb,
> zipped html, etc.),
It may not need all the formats (eg. palm), but the main ones. It
may also be readable at /manual/LANG/phpdevel/. We do not need a
printable version of it online (the actual printable versions are
also soon to be replaced with some magic in the PHP codes).
> - help from Jim to do the necessary steps on the server (if we don't
> just provide it like the howto directly from the CVS, what's IMHO not
> really preferable),
The howto's audience is quite restricted right now. This is why it
is not hosted directly for the public (which may help more guys
contributing to the docs).
> - and the adaptation of phpweb (by you Goba?) to have at least a
> download-link (I don't have Karma for phpweb)
It would be easy, so I can volunteer on this ;))
> Then there is the licensing-issue ("explicit permission" or
> substitute-doc), where I have no idea who can/will solve this - and when
> (that's no hindrance for these first steps, but shouldn't get forgotten).
Zeev and the other Zend guys should be asked...
> So if you meant just the points I can do (and some conversation with Jim
> and you concerning the other things), I'll volunteer to it. Just with
> the remark, that it can take some time till I'm able to start the work
> (if, I want to do my part at once ;)
OK.
Goba
