OpenSource documentation problems

[Paul Rubin]

"Fredrik Lundh" <fredrik at pythonware.com> writes:
> another problem is that to be able to do really good work on the
> documentation, you need to know things well enough to "have the
> big picture".  and once you have that, you'll find that the docs aren't
> really as bad as you once thought they were.

One thing that might help is a comments/questions area on each online
doc page, like PHP has.  That would let users easily point out the
areas where the docs need improvement, and collect wisdom about the
library functions attached to the docs for those functions instead of
getting it lost in clpy archives.