I suggest three additional priorities for Q2A 1.4
Github -- Moving the source to GitHub would enable more people to contribute to Q2A. Note that Github enables exact control over who can contribute. I recommend using the fork/integration request model.
This means that no one other than Gideon would be able to commit to the main source (same as today). But it would also enable people to propose changes. Then they send (via GitHub) a re-integration request that enables Gideon to decide, on a case-by-case basis, whether to accept the proposed update or not.
This is the same model used by the YUI team where 90% or more of the changes come from the professional Yahoo developers. But anyone can propose changes. If the changes are of sufficient quality and fit in with the goals/architecture of the software then they are accepted.
Wiki -- We need a better way to organize the documentation than simply a bunch of questions and answers. I think it would be fine to have the wiki contain a lot of links back to the questions and answers, rather than duplicating the material. Having a wiki would also enable more people to contribute via documentation.
I'd suggest that initially, authorship rights for the wiki could be limited. Or try it as a more open wiki, relying on the community to prune the spam and out of date info.
Beta test including plugin compatibility. I need time to re-integrate my Proxy SSO Plugin with the updated architecture. Hopefully it will be easier to integrate the Proxy SSO plugin with 1.4. See https://github.com/larrykluger/Question-2-Answer-Proxy-SSO-Plugin