Thanks for the suggestion! Actually, a process like this is more or less already in place. There are a few members of the core community group (namely Yong who is leading the efforts) who are generously contributing their volunteer and free time to help with the documentation effort. But because it's a purely volunteer effort, the task for this will understandably not always be a top priority as other things may take precedence.
But with the infrastructure in place for the members to be able to work on documentation, things are moving forward with that aspect.
The third suggestion of having the development team “wait” until the documentation is complete is unfortunately unrealistic. As technology in the landscape continues to evolve and grow, qcodo (both the community and the framework) will continue to change and grow as well. To simply wait until one thing is done until we can do the other is simply unrealistic given this climate.
The good news is that because it is open source, and because there (hopefully) is a great deal of consistency with the way qcodo is architected, as you learn and master one part of qcodo, understanding other, newer parts shouldn't be nearly as difficult or complex. And furthermore, things like the examples site and the forums serve to help users where the current documentation may not be able to yet.
Hope that helps!