I recently got access to the question closure stats (yay?), and I've been thinking about the reasons why we close questions.
About 56% of closed questions, over the last 90 days, are closed as either "unclear what you're asking" or "off-topic - Questions on problems in code you've written must describe the specific problem...". I'm wondering whether we can invest work on our off-topic reasons to help make expectations for questioners clearer, while also providing more relevant and structured feedback on question closure. (I'm assuming we have some way to modify these, since they're customized for Salesforce?)
Would it be worthwhile to see about changing or adding to our roster of off-topic reasons? A few suggestions that occur to me:
- "You've asked a question about your code, but didn't provide the relevant code. Please edit your question to add this information, but consider including only affected lines rather than pasting your entire class." (We don't really insist on "short, self-contained syntactically-valid examples", so perhaps we can be more direct and specific?)
- "You've asked a question about an error, but you didn't include the error or its location. Please provide the verbatim error message, line number, and affected code."
- "Questions about testing and code coverage should focus on testing specific lines of code or areas of functionality. For help getting started with a test class, see (Trailhead link)."
- "Questions about how to achieve specific requirements or tasks should show your own research and work towards that goal. Requests for sample code or complete implementations are off-topic."
These are just some thoughts; feel free to shoot them down independently of the broader question of whether this is a tree up which it's worth barking.
I think it'd do us good to be able to express some of our more common question issues structurally, rather than leaving it up to individual commenters.