Changes between Version 36 and Version 37 of UsingTheMailingList


Ignore:
Timestamp:
Jul 27, 2011, 1:30:23 AM (13 years ago)
Author:
gamesbook@…
Comment:

Adding formatting for names of web technologies. Formatted "dont's" for consistency.

Legend:

Unmodified
Added
Removed
Modified

  • UsingTheMailingList

    v36 v37  
    115115
    116116=== Don't's: ===
    117 * DON'T EVER POST A USER QUESTION TO THE DEVELOPERS' MAILING LIST.
    118 * Expect an instant or one-shot answer. (django-users is *NOT* your personal tutor.)
    119 * Be vague e.g. "please help build a website"
    120 * Keep repeating the same question - if anyone has an answer, you will get it sooner or later.
     117* '''Post a user question to the developers' mailing list.'''
     118* Expect an instant or one-shot answer. The mailing list is '''not''' your personal tutor.
     119* 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.
    121121* Use the phrase 'it doesn't work'. The most common question on IRC is: 'What does doesn't work mean?'
    122122* Attempt to 'bump' your question by reposting it a second time. The mailing list is not a phpBB bulletin board.
    123123
    124124=== 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.
     125For 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.
    126126
    127127wrong:
    … …  
    180180
    181181== Report resolution ==
    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)
     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.)
    183183
    184184== Start answering questions ==
    … …  
    209209== How to answer questions on the list ==
    210210 * 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.
    212212 * 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.
    213213 * 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).
Back to Top