>> Well, sad thing is that we have some good perspectives with livedocs, >> but not much work is done on this front. We might have had some good >> chance to grab some coding hands with Google SOC, but we are quite late >> in the game :) Any ideas to help recruit more developers? >> >> I often think about exposing the possibilities of livedocs more to >> php.net users, maybe finding more developers, but all of them should >> accept the controlled development model of the source (which should not >> be a roadblock, as many other OS projects follow these semantics). > > I think people get discouraged about livedocs, because it's so hands-off. > > That said -- what's WRONG with livedocs, now? There are few bugs open at > bugs.php.net -- is there a big unknown issue? > > PEARdoc (& friends like smarty-doc) support is on my wish-list.. but > otherwise, is there a showstopper?
I don't know of a showstopper. It will probably only turn out, if we push it out to a lot of testers. It might be a good idea to package up a manual with some pregenerated sqlite db, and offer it as some BETA (how popular this designation is nowadays :). Since the code gets pushed out, we can get some review and patches/improvements maybe. My only fear is that it is possible that we get too many improvements without no common direction, and not accepting a good percentage of them might discouradge quite some contributors. Goba