[translate] Implement original string discussions

NEW
Unassigned

Status

enhancement
P3
normal
2 years ago
11 months ago

People

(Reporter: mathjazz, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

User Story

As a registered user, I want the ability to ask questions about the source string, so that project managers, developers, translators and other registered users can provide more context.

These discussions should be displayed to all users in the translation interface. A user could also have an option to limit the question to a specific locale, in which case only translators to this locale will see the thread.

We should also send notifications to related audience for each post.

Note: Pontoon already shows string comments that are present in localization files, including any links and screenshots it detects within.

Also, this is separate from bug 1203265, which refers to translation comments.
No description provided.
Do you see this feature as a separate tab (e.g. "Discussion") in editor view or do you want to add something different?
Flags: needinfo?(m)
Semantically it belongs to the editor panel, yes. That said, that panel is getting pretty packed with features, especially compared to the string list panel.

I've been thinking about several different scenarios, including:
- just add it to the editor tab
- use a separate (3rd) panel
- refactor translate UI completely

Ideas welcome!

Also, we should write the more concrete spec first - one that doesn't use the word "should". ;)
Flags: needinfo?(m)
User Story: (updated)
Duplicate of this bug: 1191424
Duplicate of this bug: 1468874
We can look at this feature from various angles, as implemented by several other Localization Platforms:
- Weblate: Comments are visible to everyone, everyone following, regardless of the translation language can see the comment and reply to it, there is a special mode that only notifies the owners of the repository (Case of source strings typo or incomprehensible text).
- Crowdin: There are several categories, a comment can be marked as an issue but even in this case there are several options, for example: Request for context, Source string mistake, Translation mistake, etc., which notifies the right personnel.
- Transifex: Mark as issue feature, all others are simply comments and only the relevant translators are aware.

From a personal point of view: Many of my latest PRs and Issues on GitHub are somehow related to the fact that I was able to trace the correct location of the string in the code and quickly prepare a fix for it.
In Pontoon's case I often find myself just talking to some Mozilla dev and trying to understand if I'm going the right way.

The fact that the community can't have an open discussion with the owners of the source strings (the true context) and with one another creates a lot of unrelated "side chats" (in our case, a copy paste to the Telegram group and all the discussion is done there without bringing the conclusions to the public).

I truly believe in the necessity of this feature and think it will lead to better understanding and taking less load on the Mozila devs.
(In reply to Yaron Shahrabani from comment #5)
> In Pontoon's case I often find myself just talking to some Mozilla dev and
> trying to understand if I'm going the right way.

I'd point out that each project has a l10n PM in charge of it (visible in the header): if a string is unclear or wrong, you shouldn't be afraid to reach out directly to the PM in charge to get clarifications (that's part of their job). If needed, these clarifications should end up in the localization files itself as a comment for other localizers.
(In reply to Francesco Lodolo [:flod] from comment #6)
> I'd point out that each project has a l10n PM in charge of it (visible in
> the header): if a string is unclear or wrong, you shouldn't be afraid to
> reach out directly to the PM in charge to get clarifications (that's part of
> their job). If needed, these clarifications should end up in the
> localization files itself as a comment for other localizers.

Oh no, that's not what I meant :) You know how much I like you guys and I also like talking to you and consult you, yet the problem I'm referring to is: private conversations, Instead of Mozilla devs talking to each and every one of the translators individually we can collect experiences and conclusions with the right reference right from the translation platform.

I agree that personal communication is good and most of the time I'm getting the results I came for but what if someone else from my team or from any other team will be able to answer me so you won't have to?

Not that it's a burden or something like that but I think having the option to ask directly from the interface is very intuitive and will encourage translators to engage in the process of assisting one another and possibly engage with the product owner in a much more frequent and direct manner without repetitions if there are any.

Just my two cents :) No complaints to the Mozilla team whatsoever.
I think there are two facets here:

One is the low-risk-of-embarrassment conversation between a localizer and one of our l10n PMs, to clarify a question about a string or set of strings. And to possibly open that conversation up to other localizers (increasing the personal risk).

The other facet is reaching out to developers, possibly in bugzilla and github issues, trying to fix problems with the strings that are exposed. For many projects, we could dig into the source information for the string to find original bug and author.
You need to log in before you can comment on or make changes to this bug.