Changes between Version 3 and Version 4 of UsingTheMailingList

06/27/2011 06:48:00 AM (7 years ago)
Cal Leeming

Added some filler and some prelim ideas for this topic.


  • UsingTheMailingList

    v3 v4  
    44== Classify your question ==
    5 == Do a search first - where and how to search ==
     6== Do your homework!! ==
     7* Most of the time, Google holds the answer to your question.
     8* Don't expect a 'one-shot / copy-and-paste' answer, there may be some work involved.
     9* Don't give up on the first page, it's not unusual to go as far as 400-600 results (depending on how relevant each hit is)
     10* Make full use of exception tracebacks, and don't be afraid to dive deep into the Django core code (this is a great way to learn + find hints about what caused your problem)
     11* Look through the django-users mailing list archive ( )
     13== Be imaginative with your Google keywords ==
     14If you are looking for information relating to say "Sphinx", just typing that in alone usually won't help.
     16Here are some common search alternatives you could try;
     18* Looking for a method/class called 'ReportBug'
     20ReportBug python
     21"def ReportBug"
     22"class ReportBug"
     25* Looking for items relating to Django models
     27"Django (model|models)"
     28"from django" "import models"
     29"howto" django models
     30"problem with" django models
     33* Look for other peoples mailing list entries about MySQLdb
     35"django-users" "(problem|exception)" "MySQLdb"
     38* Be smart when it comes to looking for information about exceptions:
     40For example:
     42OperationalError: (2002, "Can't connect to local MySQL server through
     43socket '/var/run/mysqld/mysqld.sock' (2)")
     46Would become:
     48django "OperationalError" "2002"
     49"connect to local MySQL server through"
     50"OperationalError" "connect to local MySQL server through"
     51django "problem" "2002" "database"
    655== Prepare the question ==
     57* Include tracebacks (where applicable)
     58* Include an example of the code you are using
     59* Indicate what your end goal is
     60* Indicate what attempts you have made to resolve the problem yourself
     61* Ask yourself, what extra information might you need to resolve similar problems?
     64* Expect an instant or one-shot answer.
    766== Formatting your mail and your replies ==
     67* Try to use in-line replies where possible.
    869== Follow up ==
     70* Always make an effort to say thank you.
     71* If you feel someone did not understand your request (or gives an unrelated answer), then it's important you express this to them, and clarify further.
    973== Report resolution ==
     74* Always make an effort to make your findings public. This may be in the form of a Django core ticket,, 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)
    1076== Start answering questions ==
     77* Give something back to the community by answering questions you feel confident in.
Back to Top