This isn't exactly the "loosest" forum I've ever been on, but OTOH a lot of what could be called snippiness comes from the fact that people (esp. newbies) don't read the instructions carefully before posting -- i.e. the reminder to post bugs to the bug tracker, search the forums first and so on.
Many years ago, I used to work for a company whose bug tracking efforts were "managed" (if it can be called that) in forums. It was such an awful experience that a couple of us went away and wrote a new bug tracking program, called
the Bug Genie. Anyway, one of the killer features that we built into the Bug Genie was that it automagically searched the bug database for possible duplicate issues before the user could actually submit the bug. The user could then look at the existing reports before deciding whether to go ahead and submit their own.
My point is this: some (most??) users, even sysadmins are not necessarily all that bright sometimes (and I include myself in this, I do some dumb things on occasion!). The trick is to come up with logical processes to help manage and address potential stupidity, so that it doesn't always get to the point where the user makes a foolish post here on the forums.
How could this be done? What about some kind of guided support wizard, which steps the user through the process, and then link to it from the wiki main page.
An example process might be:
1. Question: Is a program not working as expected, or do you want to know how to do something?
2. Get title & keywords
(not working)
3. Automatically search bugzilla - ask, is the issue listed here?
4. Help user to post to bugzilla if not found
(do something)
3. Automatically search the wiki - ask, is the answer listed here?
4. If not, automatically search the forums - ask, is the answer listed here?
5. If not, advise the user to post a question in the correct forum. Perhaps help construct the question.