* Be vague e.g. "please help build a website". No one has time to write a vague answer.

120

* Keep repeating the same question. If anyone has an answer, you will get it sooner or later.

121

121

* Use the phrase 'it doesn't work'. The most common question on IRC is: 'What does doesn't work mean?'

122

122

* Attempt to 'bump' your question by reposting it a second time. The mailing list is not a phpBB bulletin board.

123

123

124

124

=== Language ===

125

For many of us, English is not our native language. Try to follow English syntax, but do not waste everyone's time by apologising. People will realise your difficulty and will ask for clarification if needed. However avoid using 'sms-speak' and refrain from being overly casual.

125

For many of us, English is not our native language. Try to follow English syntax, but do not waste everyone's time by apologising. People will realise your difficulty and will ask for clarification if needed. However, please avoid using 'sms-speak' and refrain from being overly casual.

* Always make an effort to make your findings public. This may be in the form of a Django core ticket, djangosnippets.com, blog post, youtube video etc. (Although sometimes, if the mailing list subject is descriptive enough, it may suffice to just have it in archive - which happens automatically)

182

* Always make an effort to make your findings public. This may be in the form of a Django core ticket, djangosnippets.com, blog post, YouTube video etc. (Although sometimes, if the mailing list subject is descriptive enough, it may suffice to just have it in archive - which happens automatically.)

* We were all newbies once. If you feel a question is too trivial to answer, do not flame - ignore the post.

211

* Ideally everyone who uses django should know the basics of python, html, css, SQL and the http protocol, but we do not live in an ideal world. If a post shows lack of such knowledge, gently point the poster to resources that would help.

211

* Ideally everyone who uses django should know the basics of Python, HTML, CSS, SQL and the HTTP protocol, but we do not live in an ideal world. If a post shows lack of such knowledge, gently point the poster to resources that would help.

212

212

* 90% of errors are explained in the last line of the traceback - this is not intuitive. The rest of the traceback needs an experienced hand to interpret. Educate users on the last line.

213

213

* If you feel the user hasn't made enough effort to find the answer themselves, explain to them why, and give them some guidance on how they can do this (point them to this page).