If this FAQ doesn’t contain an answer to your question, you might want to\ntry the django-users mailing list. Feel free to ask any question related\nto installing, using, or debugging Django.
\nIf you prefer IRC, the #django IRC channel on the Freenode IRC network is an\nactive community of helpful individuals who may be able to solve your problem.
\ndjango-users has a lot of subscribers. This is good for the community, as\nit means many people are available to contribute answers to questions.\nUnfortunately, it also means that django-users is an attractive target for\nspammers.
\nIn order to combat the spam problem, when you join the django-users mailing\nlist, we manually moderate the first message you send to the list. This means\nthat spammers get caught, but it also means that your first question to the\nlist might take a little longer to get answered. We apologize for any\ninconvenience that this policy may cause.
\nTry making your question more specific, or provide a better example of your\nproblem.
\nAs with most open-source mailing lists, the folks on django-users are\nvolunteers. If nobody has answered your question, it may be because nobody\nknows the answer, it may be because nobody can understand the question, or it\nmay be that everybody that can help is busy. One thing you might try is to ask\nthe question on IRC – visit the #django IRC channel on the Freenode IRC\nnetwork.
\nYou might notice we have a second mailing list, called django-developers –\nbut please don’t email support questions to this mailing list. This list is\nfor discussion of the development of Django itself. Asking a tech support\nquestion there is considered quite impolite.
\nDetailed instructions on how to handle a potential bug can be found in our\nGuide to contributing to Django.
\nIf you think you’ve found a security problem with Django, please send a message\nto security@djangoproject.com. This is a private list only open to long-time,\nhighly trusted Django developers, and its archives are not publicly readable.
\nDue to the sensitive nature of security issues, we ask that if you think you\nhave found a security problem, please don’t send a message to one of the\npublic mailing lists. Django has a\npolicy for handling security issues;\nwhile a defect is outstanding, we would like to minimize any damage that\ncould be inflicted through public knowledge of that defect.
\n