I still prefer a wiki like approach since the php (or mysql) docs are very cluttered when you have to take their comments in account. On the other hand they are professionally maintained imho, since they are *much* better than KDE documentation. KDE is by far larger and has so many different apps, which need screenshots and end user not dev/api docs, that more help is needed as long as the devs prefer to code than to write nice docs.
And it is their choice to some degree imo. Technically interested but non-dev end users, which are plenty out there, are the users of and the best contributers to the docs, since they know what to write about. And they are certainly more than devs.

china tour
Apparel
shoes
bags
Kitchen
Food and Wine
Furniture)
Flowers and Gifts
Wall Art
Computer ComponentsMany things are transparently clear for a dev but unclear for an end user. This is why I think it is a different community which should take care of the docs than which develops the code. Of course the app maintainer has to check for vandalism correctness and his cool hidden feature missing for releases, but the docs can be generally worked out by end users who would like to contribute and start to use docs to learn cool stuff about their apps in the first place.

Both annotations and contributions will only clutter the interface by default as a design pattern rather than trying to put it all together. That way you can never create offline or print docs of high quality without again having the devs or current admins maintain the comments and annotations.
Hopefully a small Wiki quality team will evolve (i am against ops or admins) to review and summarize the contributions. I hope this gives us more users as contributors than having the docs focused on the devs.

Cheers,
duns