What kind of issue tracking do we need for translations?

I think we primarily want to have people contribute to translations. Even when teams have people submit suggestions those suggestions are not always handled in a timely manner. So getting them submit issues about stuff is even more distant from actual contribution. I'd rather see the "issue queues" for languages be more closely tied to the strings, and only let team members participate there. Do you think it would be an issue for trying to drive in people to actually contribute to translations piggybacking on them submitting issues?

Also, there is an open issue in the l10n_server queue: #196878: Add comment field to translation (suggestion) which can be IMHO implemented by "discussion reference" fields on strings, so that certain source strings can have designated discussions.

I think for l.d.o "issues"/"discussions", we'd only need a status field, no need for criticality level, assignment, priority, categories, etc. I'm a bit vary of reimplementing a simpler version of issue queues on l.d.o, but reusing the heavy issue queues on d.o seems too distant and overwhelming to me.

I'd be in favor of a simple CCK + views based implementation of issue tracking. You could build it as a feature. That's the direction project_issue will be moving eventually. If you keep it simple, you hopefully won't need much of the crazy advanced views stuff I did for project_issue. The only possible cause for concern would be if you also wanted to allow email subscription. That'd be a lot more duplication of effort, and you might want to reconsider in that case. Otherwise, if you just need structured discussions on l.d.o and perhaps an RSS feed of updates, CCK + views (and probably comment_driven) should be all you need.

Good luck!
-Derek

@dww: good to hear. Yes, we'd need some kind of comment based property modification, and if comment driven is the best solution for that now, then I'll look at that more. Thanks for the tip! (I was considering comment_alter_taxonomy and comment_cck).

I haven't actually used comment_driven, but I hear it's the way to go. ;) I'll be curious to hear how it goes...

Some things which are clear:

- we'll have regular nodes for issues with a title and a body
- we'll have user reference field for assignment
- we'll have a status field

Ok, some questions then:

- should we call this "issues" or "discussions"?
- what kind of status values do we need?
- should we have a priority field for ordering?
- what level of "filter relation" do we need? so we can link issues to certain string sets; if its just a link field, we cannot do backlinks from the filtered data, if its fields for all possible filters, when we migrate filters to new meanings (as we did before), its gonna hurt to need to migrate these (also looking them up will be funky) - however, this can be really powerful if done well
- should we have some other catch-all field like tagging?

What else did I miss?

I think issues per language is less important oposit #196878: Add comment field to translation (suggestion)

@andypost: well, if we can figure out a way to relate issues to string sets, there you have comments for translations :) Trying to "kill two birds with one stone" as they say.

Hi people,

can one tell me, help me (maybe I blind) where I can add my translations to my modules???
Example:
In the translations list of one of my modules appear many many strings with status "not translated" and I can't nothing doing to change add translations.
In the past I applied for the spanish translators team as member account and I got a silent NO (without answers). Ok I will not contribute as translator but the question remains "How I can contribute translations to MY modules".

Please I would very gratefully If some body clarify me about this trouble.

Thanks in advance
Juan Carlos

[OT] @jcmc: You can contribute translations only if you are allowed to make suggestions; otherwise, you cannot suggest translations, even for your own modules/themes.

@jcmc: please contact the Spanish translation team maintainers. You can use their drupal.org contact forms via their user profile page. Team maintainers are listed on the team page in the sidebar.

in response to http://twitter.com/gaborhojtsy/statuses/8132753044283392

I'm the maintainer of comment_driven

demo site http://sandbox.990.cl/tracker
step by step #885554: How to build the demo ticket system site

evaluation:
- node: good to go (e.g: title)
- taxonomy: good to go (including hierarchical_select)
- cck: good to go with core's, including userreference & nodereference, BUT not so good with contrib (e.g: dates)
- exportable/features #769128: Support for exportables and the Features module, nevertheless there is a hacky workaround at #885554-39: How to build the demo ticket system site (I haven't reviewed it not even try it, just repeating what is claimed)

what else do you need to know?

[EDIT]
demo site was moved, it now resides at http://arhak.s4w.biz/tracker, however, if this new URL doesn't work then check the project page to know if it got moved again

Moving this issue to the new l.d.o project.

Closing this issue since it has been inactive for quite a while. This issue can be reopened if it is still relevant.