mozilla
Add "time to translate" graph to Locale and Project Locale Insights
While there is no SLA associated to localization, one data point that we're missing for locales is "how long does it take to get content translated".
A more technical definition would be: the time passing between a new string being added to the Pontoon database, and a translation being submitted for it (not just a suggestion).
This could be represented with an histogram, using months for the x axis, and number of days for the y axis.
Is "Time it takes to complete a project" out of scope here? That one would somehow also include strings that are not translated yet.
Technical question is - do we only look into strings that have (approved) translations when calculating times?
Is "Time it takes to complete a project" out of scope here? That one would somehow also include strings that are not translated yet.
Do you mean "time to get a project to 100%" or something else? If so, I don't understand the second part.
I don't think that — how long it takes to get to 100% — is as important.
Technical question is - do we only look into strings that have (approved) translations when calculating times?
You mean "imported" strings or something else?
I also realized the initial proposal is naive, because we need to account for strings that are not translated yet:
- If a string is translated, time_to_translate = time_translated - time_created.
- If a string is not translated, time_to_translate = end_of_month - time_created.
- If a string is "imported" (created with a translation), it should be excluded.
The final "time to translate" would be the average of these values.
Is "Time it takes to complete a project" out of scope here? That one would somehow also include strings that are not translated yet.
Do you mean "time to get a project to 100%" or something else? If so, I don't understand the second part.
I mean "Time to hit 100%", yeah. Such chart would need to account for missing strings (that's what the 2nd sentence was about).
Technical question is - do we only look into strings that have (approved) translations when calculating times?
You mean "imported" strings or something else?
No, I mean if we are looking at just strings with translations or also strings without them.
I also realized the initial proposal is naive, because we need to account for strings that are not translated yet:
That's it! :)
* If a string is not translate, time_to_translate = end_of_month - time_created.
That means translating at the end of the month and not translating will be the same?
That means translating at the end of the month and not translating will be the same?
Yes, otherwise I'm not sure how to account for untranslated.
I guess it would "Estimated time to translate", more than actual "Time to translate".