Don,
I don't know. I'm sure Collaboraid would help with documentation. What I fear is that it'll be simple for most people to claim (for themselves) "well, I have a contract/commitment to finish too".
Of course I realize that commitments are commitments, but our documentation is in such need of help that we must find a way to commit people to help with it, and then work so it continues doing well.
The danger of not allowing any new code is that those with commitments (such as Collaboraid) will just say "I'll just keep my own tree and merge it later on", so we lost that contributor.
The danger of allowing new code is that it can be claimed to come because of the commitment.
So perhaps a balanced approach would be:
- No new code for #period of time#
- BUT, if you need to commit new code, it needs to be accompanied by documentation work in _some other_ area besides the new code being committed.
How does that sound? Another question is, do you think a month will be enough? (oh, I think we definitely should do something similar with bugs)
