Add info about transifex to New Ticket page

[Bas Peschier]

At the moment it is not very clear where people should put their comments on translations of django itself.

• The "contributing to django" docs only portray the angle of people wanting to join language teams and not people wanting to comment on translations.
• It would be useful to put a note on the "new ticket" page what to do with django translation issues (and refer them to Transifex) so people will not open tickets for it.

[Jannis Leidel]

​http://docs.djangoproject.com/en/dev/internals/contributing/#submitting-and-maintaining-translations at least mentions that translators should join the django-i18n list. Questions regarding the specific translations of each language should be handled via Transifex teams.

[Bas Peschier]

Added a patch with a slight rephrasing in the contributing docs to emphasise Transifex for discussing and reporting issues.

[Gabriel Hurley]

In [15590]:

Fixed #15341 -- Clarified where translation problems should be reported in the contributing docs. Thanks to bpeschier for the report and patch.

[Bas Peschier]

Ok, my bad: I added two issues to this ticket O:-)

The addition to the "new ticket" page should happen before we close this one.

[Gabriel Hurley]

This really ought to be a new and separate ticket now, but in favor of not adding to ticket churn I'll just re-categorize this one, clarify the title, and reset the flags to indicate that there's no patch for that aspect.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Aymeric Augustin]

Some links were also obsolete since a refactoring of the contributing docs.

I modified the ticket submissing page as follows:

trac-env/templates/custom_ticket.html

@@ -14 +14 @@
           for common issues.
         </li>
         <li>
-          <a href="https://docs.djangoproject.com/en/dev/internals/contributing/#reporting-security-issues">Don't report security issues here!</a>
+          <a href="https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-features/#reporting-security-issues">Don't report security issues here!</a>
           Contact <a href="mailto:security@djangoproject.com">security@djangoproject.com</a> instead.
         </li>
         <li>
@@ -22 +22 @@
           <a href="https://docs.djangoproject.com/en/dev/faq/help/">help with support questions</a>.
         </li>
         <li>
-          Patches should be attached to the ticket as files, not included in the
-          description.
+          Use <a href="https://www.transifex.net/projects/p/django/">Transifex</a> for
+          <a href="https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations">bug reports on translations</a>.
         </li>
         <li>
           Follow our
-          <a href="https://docs.djangoproject.com/en/dev/internals/contributing/#reporting-bugs">bug reporting guidelines</a>
-          and our <a href="https://docs.djangoproject.com/en/dev/internals/contributing/#submitting-patches">patch submission guidelines</a>
+          <a href="https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-features/#reporting-bugs">bug reporting guidelines</a>
+          and our <a href="https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#patch-style">patch submission guidelines</a>
           for the best response.
         </li>
         <li>