Opened 14 years ago
Closed 13 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 |
Pull Requests: | How to create a pull request | ||
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.
Change History (11)
comment:1 by , 14 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 14 years ago
by , 14 years ago
Attachment: | django15431-contribdocs.diff added |
---|
comment:3 by , 14 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:5 by , 14 years ago
Keywords: | trac added |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
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 , 14 years ago
Component: | Documentation → Django Web site |
---|---|
Has patch: | unset |
Summary: | Better documentation for translations of django-core/contrib → Add 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 , 14 years ago
Severity: | → Normal |
---|---|
Type: | → Bug |
comment:10 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Some links were also obsolete since a refactoring of the contributing docs.
I modified the ticket submissing page as follows:
-
TabularUnified trac-env/templates/custom_ticket.html
old new 14 14 for common issues. 15 15 </li> 16 16 <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> 18 18 Contact <a href="mailto:security@djangoproject.com">security@djangoproject.com</a> instead. 19 19 </li> 20 20 <li> … … 22 22 <a href="https://docs.djangoproject.com/en/dev/faq/help/">help with support questions</a>. 23 23 </li> 24 24 <li> 25 Patches should be attached to the ticket as files, not included in the26 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>. 27 27 </li> 28 28 <li> 29 29 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> 32 32 for the best response. 33 33 </li> 34 34 <li>
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.