help.txt 3.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. =================
  2. FAQ: Getting Help
  3. =================
  4. How do I do X? Why doesn't Y work? Where can I go to get help?
  5. ==============================================================
  6. If this FAQ doesn't contain an answer to your question, you might want to
  7. try the |django-users| mailing list. Feel free to ask any question related
  8. to installing, using, or debugging Django.
  9. If you prefer IRC, the `#django IRC channel`_ on the Freenode IRC network is an
  10. active community of helpful individuals who may be able to solve your problem.
  11. .. _`#django IRC channel`: irc://irc.freenode.net/django
  12. .. _message-does-not-appear-on-django-users:
  13. Why hasn't my message appeared on `django-users`?
  14. =================================================
  15. |django-users| has a lot of subscribers. This is good for the community, as
  16. it means many people are available to contribute answers to questions.
  17. Unfortunately, it also means that |django-users| is an attractive target for
  18. spammers.
  19. In order to combat the spam problem, when you join the |django-users| mailing
  20. list, we manually moderate the first message you send to the list. This means
  21. that spammers get caught, but it also means that your first question to the
  22. list might take a little longer to get answered. We apologize for any
  23. inconvenience that this policy may cause.
  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 email 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. I think I've found a bug! What should I do?
  39. ===========================================
  40. Detailed instructions on how to handle a potential bug can be found in our
  41. :ref:`Guide to contributing to Django <reporting-bugs>`.
  42. I think I've found a security problem! What should I do?
  43. ========================================================
  44. If you think you've found a security problem with Django, please send a message
  45. to security@djangoproject.com. This is a private list only open to long-time,
  46. highly trusted Django developers, and its archives are not publicly readable.
  47. Due to the sensitive nature of security issues, we ask that if you think you
  48. have found a security problem, *please* don't send a message to one of the
  49. public mailing lists. Django has a
  50. :ref:`policy for handling security issues <reporting-security-issues>`;
  51. while a defect is outstanding, we would like to minimize any damage that
  52. could be inflicted through public knowledge of that defect.
  53. .. _`policy for handling security issues`: ../contributing/#reporting-security-issues