When a topic for discussion cannot be definitively "answered", it's silly (er, awkward) to pigeohole the users into titling the topic as a "question", eh?
Here, eftalgezer thoughtfully applied a tag, "feature-suggestion". My approach might have been to stuff "suggest:" into the title, not phrase the title as a question... and hope for upvotes. Oh, well...
For certain sites, I have repeatedly thought it would be a good idea to relabel and repurpose the "flag" feature. The label would read "RTFM" instead... and users would be advised to NOT reply to any post bearing "xx flags" (vs posting to mention "it's right there in the wiki; here's a link" or "already discussed numerious times, use the site search" or "don't feed the trolls" or whatever). Not toward encouraging rudeness, nor meanness, nor noob-unfriendliness... but, seriously, on many sites it begs to be said. Through the years I've painfully witnessed many communities devolving, due to the "Feed a man a fish" vs "Teach a man to fish" mindset of seekers.
On a related note (I'm saying it's related, others may not agree):
Many communities beg a better mechanism for handling/enforcing their user agreement stipulation "on this site, discussions (and bug reports, etc) must be posted in English [or whichever] language". If seeker does not speak users' language, users cannot reasonably be expected to provide help. I've become "burned out" as a result of repeatedly trying to work beyond language barriers and trying to help. Sadly, experience has taught me to refrain from discussion when a language barrier exists. Providing a lengthy, detailed "howto" misses the mark, as does a ping-pong, bits-n-pieces "what means termX?" dialog session. Nearly inevitably, the course of such dialogs has been "sorry i not understand. You do for me please? make work?" (ala "Feed a man a fish")