> >>>The day livedocs becomes live, that will be a great day. :) > > > > It will take a while... It still has a couple of problems. Another problem > > is that the main livedocs developpers have little time to spend on the > > project, and the others who were working on it don't want to continue... > > (but I won't talk more about this). > > Note that livedocs core developers do accept patches. Have you seen Ilia > accepting the patch from Curt to fix the font sizes on the php.net view? > It is just that they have a hard time following the traffic on phpdoc. > Ilia himself has a trigger on cvs commit messages with "livedocs" in > them to get :) > > Livedocs needs more testers, and more people willing to put time into > it. I never found enough time to help out, but I try to direct everybody > who is not satisfied with the lack of insite search, lack of timely > manual updates, etc. to help in livedocs development as that is clearly > the way to go.
We need docs.php.net online, and docweb on a reliable, working, and maintained server; and in PHP CVS. The current situation there looks a bit screwy but I've only been an observer there. I do like the idea of a core group starting it out, less noise, but is it ready for others now or is the server problem still holding things back? Maybe we got a little too aggressive with idealistic ideas and should just focus on one thing at a time, like livedocs, I don't know. Once ready for testing (now?), docs.php.net can simply be livedocs like it used to be (or a shell of docweb) and we won't "advertise" it. People will slowly use it this way and the more people start using it the more people will complain and more importantly the more people will fix problems and add features. If a major problem exists there we can redirect users to php.net/manual/ Also, it should add excitement to the docweb project, a project few know even exists right now[1]. Regards, Philip [1] http://doc.keliglia.com/ http://news.php.net/php.doc.web
