Our Area 51 Beta site shows have a 1.9 answer ratio, which is close to the recommended 2.5 answers per question. We're also at 119 users with 200+ rep, also close to the recommended 150 users.
With SDL Tridion 2013 out, maybe we have an opportunity to revisit questions (more answers and more points). Regardless of the release, we should probably revisit unanswered questions (anyone know the answer to these?).
Here are some tips and reminders. Feel free to add more or disagree with any of these points.
We should look at questions and answers in the context of when they were asked. But new and old users should feel free to revisit old questions adding answers, comments, or updates where appropriate.
Sometimes it makes sense to re-ask questions in the context of new features and functionality, but we could also update existing Q&A. The appropriate update probably depends on the type of question or answer.
General "is it possible?" questions with a "no" (or "no but here's a hack") answers could use updated answers or comments as things change.
Specific questions for a given API version should probably be left as-is, but answers could include notes on major differences between versions (e.g. "here's how to do it in 2009, 2011, and/or 2013"). We seem to do this naturally.
For some examples, How would I get all pages using core service? and CoreService GetList() behaving differently to GetListXml() are 2011-specific questions, where the answer depends on the version of the Core Service. I think we did a good job tagging these and clarifying version differences.
Any recommendations for other scenarios? Does editing questions or providing answers "bump" them and is that a good/bad thing?