I'll rehash the "Documentation Status" document listing things that need to be written/improved, so we can assign it to people. The current problem is one of resources (it has always been).
People want to work on code because it's more fun. You can see things happenning and people giving you kudos for your work (recognition). So we've ended up with very few people doing documentation, but this needs to stop.
I'm confident that once 4.6 is released, we could solve our documentation woes in 4-6 weeks of committed time from the community. But I only see that happenning if we have a new-code freeze until documentation gets improved.
From there on, we set higher documentation standards for accepting packages into the OpenACS CVS tree -- namely, your package needs to have documentation before it can be considered complete, no matter how well it works.
