Rosetta needs a collaboration component

Bug #1524970 reported by Jimmy Merrild Krag
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

I propose this component would contain one or more of the following features:
- Language specific discussion for each string.
- Global discussion for each string (also accessible by the developers)
- Voting for suggestions.

Features like these is implemented over at https://crowdin.com/, and I urge you to consider doing some of the same for Rosetta. As a translator on multiple projects on both Launchpad and Crowdin, I often miss these means of communication on Launchpad. Translations often increase their quality and the speed of which they are conducted, since you avoid getting stuck at hard strings, or left puzzled by source strings which may or may be incorrect or lacking context.

Why should teams not just create separate means of communication regarding this?
Simply not all translation teams have the resources, and furthermore the proposed features
- Keeps the communication for each string close to the string.
- Avoids translators being dependent on following an IRC-channel (or similar) tightly, to not be excluded from discussion.
- Makes translators think a little longer, instead of quickly sending a rushed message.

Tags: feature
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.