>> 1. We can easily ship an sqlite db for the complete manual, as we are >> going to do with all the mirror sites, when livedocs will be ready to >> handle serving the manual. > > Good point (-: > >> 2. We can provide a web service for users to pick their customized >> manual, and get a customized sqlite db plus the needed XML files in a >> package. > >> 3. For those, who want more, requiring the full phpdoc build system is >> not an issue. With #2, we can already expand in areas not thought of >> before by our kind readers. > > These are good ideas. +1 (-:
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). Goba
