PageRenderTime 32ms CodeModel.GetById 20ms RepoModel.GetById 0ms app.codeStats 0ms

Plain Text | 73 lines | 54 code | 19 blank | 0 comment | 0 complexity | 6f960a0737c050645a655c50ab50e5f8 MD5 | raw file
Possible License(s): BSD-3-Clause
  1. FAQ: Getting Help
  2. =================
  3. How do I do X? Why doesn't Y work? Where can I go to get help?
  4. --------------------------------------------------------------
  5. If this FAQ doesn't contain an answer to your question, you might want to
  6. try the `django-users mailing list`_. Feel free to ask any question related
  7. to installing, using, or debugging Django.
  8. If you prefer IRC, the `#django IRC channel`_ on the Freenode IRC network is an
  9. active community of helpful individuals who may be able to solve your problem.
  10. .. _`django-users mailing list`:
  11. .. _`#django IRC channel`: irc://
  12. Why hasn't my message appeared on django-users?
  13. -----------------------------------------------
  14. django-users_ has a lot of subscribers. This is good for the community, as
  15. it means many people are available to contribute answers to questions.
  16. Unfortunately, it also means that django-users_ is an attractive target for
  17. spammers.
  18. In order to combat the spam problem, when you join the django-users_ mailing
  19. list, we manually moderate the first message you send to the list. This means
  20. that spammers get caught, but it also means that your first question to the
  21. list might take a little longer to get answered. We apologize for any
  22. inconvenience that this policy may cause.
  23. .. _django-users:
  24. Nobody on django-users answered my question! What should I do?
  25. --------------------------------------------------------------
  26. Try making your question more specific, or provide a better example of your
  27. problem.
  28. As with most open-source mailing lists, the folks on django-users_ are
  29. volunteers. If nobody has answered your question, it may be because nobody
  30. knows the answer, it may be because nobody can understand the question, or it
  31. may be that everybody that can help is busy. One thing you might try is to ask
  32. the question on IRC -- visit the `#django IRC channel`_ on the Freenode IRC
  33. network.
  34. You might notice we have a second mailing list, called django-developers_ --
  35. but please don't e-mail support questions to this mailing list. This list is
  36. for discussion of the development of Django itself. Asking a tech support
  37. question there is considered quite impolite.
  38. .. _django-developers:
  39. I think I've found a bug! What should I do?
  40. -------------------------------------------
  41. Detailed instructions on how to handle a potential bug can be found in our
  42. :ref:`Guide to contributing to Django <reporting-bugs>`.
  43. I think I've found a security problem! What should I do?
  44. --------------------------------------------------------
  45. If you think you've found a security problem with Django, please send a message
  46. to This is a private list only open to long-time,
  47. highly trusted Django developers, and its archives are not publicly readable.
  48. Due to the sensitive nature of security issues, we ask that if you think you
  49. have found a security problem, *please* don't send a message to one of the
  50. public mailing lists. Django has a
  51. :ref:`policy for handling security issues <reporting-security-issues>`;
  52. while a defect is outstanding, we would like to minimize any damage that
  53. could be inflicted through public knowledge of that defect.
  54. .. _`policy for handling security issues`: ../contributing/#reporting-security-issues