1424935 - L10N for Onboarding GoFaster

Status: NEW

(Firefox :: Tours, enhancement, P3)

Description

[Fischer [:Fischer]]

We are planning make Onboarding tour ride the GoFaster so as to update tours or strings between releases based on ux research results. Right now we just check-in strings into the central and follow the l10n translation schedule on the Central. For GoFaster, we might need another way to handle the l10n translation.

Comment 1

[Fischer [:Fischer]]

Hi Flod,

The Onboarding tour is a system addon and we are planning make Onboarding tour ride the GoFaster. 

For GoFaster, 
1. Do we need to have a repo on Github (or somewhere else) to host locales?
2. Now we just check-in strings into central and follow the train translation process. For GoFaster, what process we should follow for l10n?

Thank you

Comment 2

[Francesco Lodolo [:flod]]

Would development still happen in mozilla-central? Would you be uplifting code from mozilla-central to mozilla-beta to ship the updated add-on?

Depending on the answer, we might keep using the translation in mozilla-central as they are, since all translations are now coming out of a single l10n repository for all branches.

I would also like to set expectations: having strings in mozilla-central gives you a better visibility than being a separate project (like Activity Stream). 

If you uplift strings, you should still need to plan a reasonable time for translation, and evaluate case by case if you're willing to ship an add-on not fully translated in some major languages.

Comment 3

[Fischer [:Fischer]]

Hi Flod,

After discussing with PMs about the project planning

(In reply to Francesco Lodolo [:flod] from comment #2)
> Would development still happen in mozilla-central? 
>  
Yes, still in m-c

> Would you be uplifting code from mozilla-central to mozilla-beta to ship the updated add-on?
> 
We expect the most cases should be updating in m-c then uplifting to beta

> Depending on the answer, we might keep using the translation in
> mozilla-central as they are, since all translations are now coming out of a
> single l10n repository for all branches.
> 
> I would also like to set expectations: having strings in mozilla-central
> gives you a better visibility than being a separate project (like Activity
> Stream). 
> 
Yes, this is also one consideration we think important.

> If you uplift strings, you should still need to plan a reasonable time for
> translation, and evaluate case by case if you're willing to ship an add-on
> not fully translated in some major languages.
> 
Thank you. This sounds like translating outside m-c brings some overhead to us.

Comment 4

[Francesco Lodolo [:flod]]

(In reply to Fischer [:Fischer] from comment #3)
> Thank you. This sounds like translating outside m-c brings some overhead to
> us.

I think it is. 

Both Screenshots and Activity Stream work on GitHub, and periodically dump code and translations in mozilla-central or mozilla-beta.

Localization updates are quite confusing in this scenario: sometimes they land updates to mozilla-beta early in the cycle, and we end up shipping translations in release that are 2 months old (also there's really no clear way to know which version we're shipping).

Since we only have one repository to ship all products from mozilla-central and mozilla-beta, you wouldn't need to bother with uplifting localization from an external GitHub repository, they would already be there for your add-on. You only need to uplift code.

As said, the only concern would be leaving enough time for localization, and making sure all major languages are well covered before shipping.