It is the holidays!
A time of gifts, food, drink and festival (and hats, if you are into that sort of thing).
Now, we don't have any of those for you (except the hats), but we do have over a thousand unanswered questions on our site. So, alongside the network-wide winter bash that will be happening again this year, we thought it would be a good idea to go through and prune the backlog in what we're going to call the 2013 GDSE Winter Refactor.
This will be a directed effort to review, answer or close all the "unanswered" questions on the site which have fallen off the front page and are bit-rotting in the deeper, darker, less-trafficked portions of our site.
What can you do to help, you ask? It's simple! Visit the unanswered questions page and give it a browse. Keep an eye out for questions good and bad that could use some tidying up (really, that's most of them). Then:
Vote to close anything that doesn't belong on this site or that would be better served on another SE network site. That includes
- Questions that are not on-topic or that aren't high-quality questions.
- Question that not the right sort of question for a StackExchange site.
- Queries that are general programming questions better suited for StackOverflow.
Edit any questions that are poorly worded, overly verbose, or not actually phrased as questions.
- Try your best to find the real question that a user is asking. Edit the question to focus on that. Remove excess distracting information.
- It's okay to make a question more general, especially if you are turning a "code dump" type of question into one that is more focused on the theory behind the topic.
- If the question title and the question text disagree, edit the former to match the latter.
- When in doubt, remember to be bold. Some of these question have been languishing, unanswered, for months. You can only really improve their chances by editing them.
Answer any questions you feel qualified to.
- Keep the usual guidelines in mind for answering questions. Try to avoid guesses or lots of speculation.
If a user is asking about something that suggests they are taking the wrong approach, consider answering their direct question first (briefly) before offering guidance on an alternative approach.
If a question already has an answer, consider editing the answer to improve it if needed, or give it up an appropriate vote.
Of course, please remember that the point of this event is to reduce the unanswered question backlog and improve the quality of the Q&A available on this site.
As such, please don't upvote zero-scored answers just to mark the question as answered, and please don't answer bad questions, make trivial edits, or add chatty comments. We want to be decisive about getting good questions salvaged and answered and getting bad questions closed. When in doubt, flag it for moderator attention.