SC> My instant livedocs, for example, has not evolved, primarily because:
SC> lack of expressed interest from anyone but me and Goba, I haven't
SC> received much feedback, I got hung up on a bug
SC> (http://bugs.php.net/bug.php?id=33608), and:
I've seen livedocs, but didn't understand how it works. It looks
rather complicated with these shell scripts and I'm working on a
windows platform. I was not sure it will work on cygwin, because
I have separate locations for wwwroot, phpdoc repository and
cygwin root. Me too doen't have time to read these 130k just to
find out it should fill sqlite database somewhere, but that
doesn't happen, because the package is still alphabuggy and
cygwin/win uncompatible.
Yes, it works on cygwin (at least worked last time I checked it - one year ago).
I absolutely agree with you when you say that livedocs isn't easy to understand. the code isn't commented (as PHP sources aren't..) and there are no docs about it. But when you understand how all the magic works, it is easy. Having clear docs about livedocs would probably create a developer community (out of phpdoc) to maintain and improve it.
2. Developers don't have enough time
SC> That's the big one. I'm tasked at 100% right now, with working, working
SC> [sic], raising a kid, and having a new house that needs care.
The same conflict I'm trying to resolve. I'd like to be more
financially independent and work on PHP.NET issues at the same
time, but this seems to be unreal. That's why for last half of
year almost no progress has been done with CHM bugs and ToDo's.
Only Mozilla has such dreams :) I wouldn't mind to work on full time in PHP either...
Roadmap != deadlines. It is a list of features/bugs that should be
completed before release. It gives answers to question "when livedocs
will be available?" in a manner "after this, this and this bug will
be fixed". It also tells what "this bug is not so important and it
is planned on a next livedocs rewrite". So it is a way to map bugs and
features to releases and give others possibility to check box on this
buglist to speed up the release. No deadlines here. It just increases
visibility of the process. This bug and feature (issue) list can be
extended to include other relevant information about arising problems,
provide issue-dependency links. Issue != bugreport.
Yep, such list would also help.
Nuno