mirror of https://github.com/django/django.git
Fixed some linking errors in the FAQ.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@7602 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
b5f92938ab
commit
88a6fa5a07
33
docs/faq.txt
33
docs/faq.txt
|
@ -653,44 +653,49 @@ How do I do X? Why doesn't Y work? Where can I go to get help?
|
|||
--------------------------------------------------------------
|
||||
|
||||
If this FAQ doesn't contain an answer to your question, you might want to
|
||||
try the `django-users`_ mailing list. Feel free to ask any question related
|
||||
try the `django-users mailing list`_. Feel free to ask any question related
|
||||
to installing, using, or debugging Django.
|
||||
|
||||
If you prefer IRC, the `#django IRC channel`_ on freenode is an active
|
||||
community of helpful individuals who may be able to solve your problem.
|
||||
|
||||
.. _django-users mailing list: http://groups.google.com/group/django-users
|
||||
.. _#django IRC channel: irc://irc.freenode.net/django
|
||||
.. _`django-users mailing list`: http://groups.google.com/group/django-users
|
||||
.. _`#django IRC channel`: irc://irc.freenode.net/django
|
||||
|
||||
Why hasn't my message appeared on django-users?
|
||||
-----------------------------------------------
|
||||
|
||||
Django-users has a lot of subscribers. This is good for the community, as
|
||||
django-users_ has a lot of subscribers. This is good for the community, as
|
||||
there are lot of people that can contribute answers to questions.
|
||||
Unfortunately, it also means that django-users is an attractive target for
|
||||
Unfortunately, it also means that django-users_ is an attractive target for
|
||||
spammers.
|
||||
|
||||
In order to combat the spam problem, when you join the django-users mailing
|
||||
In order to combat the spam problem, when you join the django-users_ mailing
|
||||
list, we manually moderate the first message you send to the list. This means
|
||||
that spammers get caught, but it also means that your first question to the
|
||||
list might take a little longer to get answered. We apologize for any
|
||||
inconvenience that this policy may cause.
|
||||
|
||||
.. _django-users: http://groups.google.com/group/django-users
|
||||
|
||||
Nobody on django-users answered my question? What should I do?
|
||||
--------------------------------------------------------------
|
||||
|
||||
Wait. Ask again later. Try making your question more specific, or provide
|
||||
a better example of your problem.
|
||||
|
||||
Remember, the readers of django-users are all volunteers. If nobody has
|
||||
Remember, the readers of django-users_ are all volunteers. If nobody has
|
||||
answered your question, it may be because nobody knows the answer, it may
|
||||
be because nobody can understand the question, or it may be that everybody
|
||||
that can help is extremely busy.
|
||||
|
||||
Resist any temptation to mail the `django-developers mailing list`_ in an
|
||||
attempt to get an answer to your question. Django-developers is for discussing
|
||||
the development of Django itself. Attempts to use django-developers as
|
||||
a second-tier support mechanism will not be met with enthusiastic responses.
|
||||
attempt to get an answer to your question. django-developers_ is for discussing
|
||||
the development of Django itself. Attempts to use django-developers_ as
|
||||
a second-tier support mechanism will not be met an enthusiastic response.
|
||||
|
||||
.. _`django-developers mailing list`: http://groups.google.com/group/django-developers
|
||||
.. _django-developers: http://groups.google.com/group/django-developers
|
||||
|
||||
I think I've found a bug! What should I do?
|
||||
-------------------------------------------
|
||||
|
@ -698,7 +703,7 @@ I think I've found a bug! What should I do?
|
|||
Detailed instructions on how to handle a potential bug can be found in our
|
||||
`Guide to contributing to Django`_.
|
||||
|
||||
.. _contribution guide: ../contributing/#reporting-bugs
|
||||
.. _`Guide to contributing to Django`: ../contributing/#reporting-bugs
|
||||
|
||||
I think I've found a security problem! What should I do?
|
||||
--------------------------------------------------------
|
||||
|
@ -710,11 +715,11 @@ are not publicly readable.
|
|||
|
||||
Due to the sensitive nature of security issues, we ask that if you think you
|
||||
have found a security problem, *please* don't send a message to one of the
|
||||
public mailing lists. Django has `a policy for handling security issues`_;
|
||||
public mailing lists. Django has a `policy for handling security issues`_;
|
||||
while a defect is outstanding, we would like to minimize any damage that
|
||||
could be inflicted through public knowledge of that defect.
|
||||
|
||||
.. _policy for handling security issues: ../contributing/#reporting-security-issues
|
||||
.. _`policy for handling security issues`: ../contributing/#reporting-security-issues
|
||||
|
||||
Contributing code
|
||||
=================
|
||||
|
@ -725,7 +730,7 @@ How can I get started contributing code to Django?
|
|||
Thanks for asking! We've written an entire document devoted to this question.
|
||||
It's titled `Contributing to Django`_.
|
||||
|
||||
.. _Contributing to Django: ../contributing/
|
||||
.. _`Contributing to Django`: ../contributing/
|
||||
|
||||
I submitted a bug fix in the ticket system several weeks ago. Why are you ignoring my patch?
|
||||
--------------------------------------------------------------------------------------------
|
||||
|
|
Loading…
Reference in New Issue