Instead of non-specific "head is broken" email, why not point out what
is broken?
Livedocs is running fine here; I built it only a week or so ago with
no problems.
Plus, I have a mirror that updates daily (livedocs.thebrainroom.net)
with no problems (assuming that someone hasn't broken phpdoc....)
If you have a patch that works properly, by all means send it our way
(either myself, Ilia, Derick or Goba). What we don't want is a
half-baked patch that "fixes" stuff for one person/case and that
breaks everything else; and that is the reason we tightened up the
karma--some of us are *already* running livedocs in production.
I've seen plenty of people say that livedocs isn't ready, but non of
them have said why or come up with a firm list of what needs to be
done to make it ready, let alone come up with patches for that.
Would it help to open a new "Livedocs issue" type of bug at bugs.php.net, so people can submit problems / (links to) patches there? I have heard people submit trouble tickets at thebrainroom lately (AFAIR philip did that). It would be better to cleanly provide a way to report bugs against livedocs, now that it is getting used more and more.
Goba