Hehe, maybe I will extract it and edit to post it as a blog when I get time.
One of the issues with getting good technical people to do high quality work is that they are in demand and get well paid - so either they have to be well paid by Hive or they have to be otherwise motivated to participate. It shouldn't be a problem to pay people well to do the work from the DAO but we need to have a way of reliably demonstrating the track record of those involved.
I am capable of doing the technical writing but I don't have time to do it and am unlikely to have time in the foreseeable future. Also, in honesty, the prospect of doing that work is quite daunting because of the difficulty of de-cyphering the code and trying to combine information from so many sources to make sense of what needs to be written and the purpose behind the code/functions. Another way around this problem is to formalise the process of code creation so that documentation is created in advance of code being written and ensuring that nothing can be finalised and put into public use without sufficient documentation to support the technicalities of it.
While this might sound like 'unncessary overheads' to some developers, the reality is that we can't expand Hive very well without something like this being done. Hive is an interface between technology and society, so we must have a focus on the society part at all times.