Tips for posting to the Drupal forums

The following best practice tips can make participating in the forums a more pleasurable and productive experience for everyone:

"Always use context-sensitive forum post titles."

Good titles are just as important in forum posting as they are in email. Many newbies believe that the easiest way to get support is to scream "HELP!!!" in all caps in a subject line. However, the Drupal forums and issues are very active. Many Drupal members check the tracker page and scan the titles. They prioritize how they may use their limited time by offering support where they feel they can provide direct assistance. So a post like "Getting error X in installation" or "Help with thinking through corporate Internet site design" is more likely to attract someone who can assist with your problem.

"Provide detailed specifics."

Often, before someone may be able to assist you, they will need to know the Drupal version number, the hosting environment, the specific error generated, and other information. Vague support requests just end up requiring a volley of question and answer, lengthening the time it takes to resolve an issue. If you are using Drupal 5, you can find a status report in the administration screen, ready to be pasted into a forum topic. Of course you should still provide enough context for the information to be useful.

"Ignore flames and rude tones."

Drupal is a large international community. Since many members are not native English speakers, realize that a brusque tone may be a result of language differences and should not be immediately interpreted as rude. Regardless, if you feel like another user has flamed you, the best response is to ignore the offense and continue working toward discussing productive solutions.

"You get more bees with honey than with vinegar."

While it is very easy to become frustrated when grappling with a problem, remember that Drupal community members donate their time in offering support. People are more likely to respond to posts which ask nicely for assistance over those that demand it or complain. Politeness can make a difference.

"With volunteer support, not everyone gets a response."

If your post has gone unanswered, perhaps no one that has read your post has the solution to your problem. You might also consider whether the title for the post is specific enough. And if you feel like support response could be better on drupal.org, please donate some of your time, too, to answering support questions. In a volunteer effort, the only way to improve support is for everyone to participate.

"Enable your contact tab!"

So that people may offer assistance privately by email, be sure to edit your user account and check the Personal contact form box. This feature does not share your email address, but rather forwards the message to you via drupal.org.

"Please see the handbook."

If people provide a link to the information, please read it. Information in the handbook is to cut down on repetition so if you have further questions after reading, then try and refine your question further.

Additional reading:

Some more suggestions

dman - July 1, 2007 - 04:21
  • Describe what you've done so far. Not only will this avoid wasting everyones time by suggesting things you've tried, it will demonstrate a willingness and capability to help yourself, and possibly give an indication of your experience level so the answers can be worded appropriately without blinding your with jargon.
    Some questions can only be answered when built on an understanding of other core concepts. If you are Missing core concepts or looking for a simple answer to a hard question, no amount of short forum posts will provide a good answer.
    How to ask questions the smart way
  • How to write a bug report. And try to understand the difference between an actual bug - which should probably go in the project issues queues - and a problem or query that's giving you unwanted behaviour or just not working exactly like you want it to today. Programmers don't like it when the lack of a custom option you have just thought of is called an error. Nor if the option exists and you didn't see it, although that's often easy to answer, and a suggestion as to what would be better documentation/UI may be appreciated.
  • Don't expect anyone to take more time to answer the question than you did to ask it.
    Simply, if you state a problem in one sentence but the answer would take 2 pages to explain, your post may be ignored, or if you are lucky, given a link to the handbook
  • It is acceptable to 'bump' your own posts in order to keep them on the active list if you don't seem to be getting any good responses. Especially project issues, preferably with additional troubleshooting info. It's certainly better than reposting or cross-posting. But No more than once in 24 hours, and do not get petulant or sarcastic and complain about the community if your problem wasn't responded to immediately. That's a sure turn-off.
  • A really helpful addition to improving the docs would be to add to your question:
    "I was looking at pages X,Y,Z in the handbook, but couldn't see/understand the answer I expected to find there".
    This would enable the support folk to copy a summary of their forum answers to the FAQ or handbook pages where they will be the most use!
    Terminology and mind-maps differ between the reader and writer, so if you can let us know where you expect to find the answer ... we can copy/link it to there for next time.
    this does of course assume you did some of your own research first ;-)

.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/

 
 

Drupal is a registered trademark of Dries Buytaert.