Opened 13 years ago

Closed 12 years ago

#15341 closed Bug (fixed)

Add info about transifex to New Ticket page

Reported by: Bas Peschier Owned by: nobody
Component: *.djangoproject.com Version: dev
Severity: Normal Keywords: trac
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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.

Attachments (1)

django15431-contribdocs.diff (1.1 KB ) - added by Bas Peschier 13 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 by Gabriel Hurley, 13 years ago

Triage Stage: UnreviewedAccepted

comment:2 by Jannis Leidel, 13 years ago

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.

by Bas Peschier, 13 years ago

comment:3 by Bas Peschier, 13 years ago

Has patch: set

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

comment:4 by Gabriel Hurley, 13 years ago

Resolution: fixed
Status: newclosed

In [15590]:

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

comment:5 by Bas Peschier, 13 years ago

Keywords: trac added
Resolution: fixed
Status: closedreopened

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.

comment:6 by Gabriel Hurley, 13 years ago

Component: DocumentationDjango Web site
Has patch: unset
Summary: Better documentation for translations of django-core/contribAdd info about transifex to New Ticket page

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.

comment:7 by Łukasz Rekucki, 13 years ago

Severity: Normal
Type: Bug

comment:8 by Aymeric Augustin, 12 years ago

UI/UX: unset

Change UI/UX from NULL to False.

comment:9 by Aymeric Augustin, 12 years ago

Easy pickings: unset

Change Easy pickings from NULL to False.

comment:10 by Aymeric Augustin, 12 years ago

Resolution: fixed
Status: reopenedclosed

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

    old new  
    1414          for common issues.
    1515        </li>
    1616        <li>
    17           <a href="https://docs.djangoproject.com/en/dev/internals/contributing/#reporting-security-issues">Don't report security issues here!</a>
     17          <a href="https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-features/#reporting-security-issues">Don't report security issues here!</a>
    1818          Contact <a href="mailto:security@djangoproject.com">security@djangoproject.com</a> instead.
    1919        </li>
    2020        <li>
     
    2222          <a href="https://docs.djangoproject.com/en/dev/faq/help/">help with support questions</a>.
    2323        </li>
    2424        <li>
    25           Patches should be attached to the ticket as files, not included in the
    26           description.
     25          Use <a href="https://www.transifex.net/projects/p/django/">Transifex</a> for
     26          <a href="https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations">bug reports on translations</a>.
    2727        </li>
    2828        <li>
    2929          Follow our
    30           <a href="https://docs.djangoproject.com/en/dev/internals/contributing/#reporting-bugs">bug reporting guidelines</a>
    31           and our <a href="https://docs.djangoproject.com/en/dev/internals/contributing/#submitting-patches">patch submission guidelines</a>
     30          <a href="https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-features/#reporting-bugs">bug reporting guidelines</a>
     31          and our <a href="https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#patch-style">patch submission guidelines</a>
    3232          for the best response.
    3333        </li>
    3434        <li>
Note: See TracTickets for help on using tickets.
Back to Top