To clear things up once and for all :) Wez started livedocs on his own machine without any revision control, and then some curious people peaked in (Derick Ilia and myself).
And me, actually..
Well, only those listed by me have CVS write Karma :) But others also tested it, including Alan Knowles.
contribute code will get access (keeping in mind that we would like to keep it a general tool to be useable for all the PHP subprojects and others too).
Hooray :) cos I got tired of adapting it w/o cvs karma.. it meant re-writing locally every time there was a change in the core version. That's why I lost interest.
That's why the development will move to cvs.php.net (to let and to persuade people to contribute).
Hm, I am sure the phpdoc build system would not work with the configure.in file outside of cygwin, even if the tools are available as native windows .exe files, since the configure system is tailored for unix tools...
No, we still need cygwin, it's just that xsltproc is available as a cygwin package and I put the stylesheets into cvs.php.net now. Incidentally, cygwin's improved massively over the last couple of years - go for a minimum install, fire up a build and see what's missing, download it, try again & etc. Even over dialup, it doesn't take too long to set this up now, maybe an hour or so. PHP is the only executable we need to add to /bin because we use it for part of the processing (PHP4, but 5 works fine too).
Since we have never had the XSLT tools sutiable enough for HTML generation, we still need jade. The current website manual is built with jade... So until we can employ livedocs, we will not be able to move away from jade. Now that livedocs is on the horizon, there are not much people who would like to put effort into making the DSSSL and XSLT sheets better...
Goba
