768851 - Plug gaia-l10n repos into Elmo

Status: RESOLVED FIXED

(Localization Infrastructure and Tools :: Administration / Setup, task)

Description

[Staś Małolepszy :stas]

We'll need to figure out how to hook the gaia-l10n repos into Elmo.  A few data points:

1. B2G's platform code is in hg: https://hg.mozilla.org/mozilla-central/b2g.  

2. Gaia's code is in git:  https://github.com/mozilla-b2g/gaia

3. Kaze created a single git repository to store the localization files in: https://github.com/fabi1cazenave/gaia-l10n/

4. The structure of Kaze's gaia-l10n repo is: app first, locale second.

5. I had IT create hg.mozilla.org/gaia-l10n in bug 768373.

6. I pushed a few testing files to en-US and es. See

    https://hg.mozilla.org/gaia-l10n/en-US/
    https://hg.mozilla.org/gaia-l10n/es/

   I wonder if we should keep en-US in there, or maybe move it somewhere to mozilla-central/b2g or mozilla-central/gaia?

7. The structure in the gaia-l10n hierarchy is: locale first (an hg repo), app second.

8. I put all apps' localization files in an "apps" directory in case there are other files in the future (like toolkit overrides or other b2g strings -- this is not planned for v1 though).  Not sure if that was the right thing to do.  Maybe I should have had the hg hierarchy named "b2g-l10n" and created a "gaia" directory under each locale?

9. We'll need toolkit strings, like net error messages.

10. But it is likely that we will not show them directly from Gecko.  Instead, I hear that the current plan is to have Gecko bubble up error events and intercept them in Gaia and show custom error messages.  In this case, it would be good to be able to reuse the transaltions from netError.dtd.  (I'm concerned by this point.)

11. We shouldn't tie B2g to any particular release train or channel.

Comment 1

[Axel Hecht [:Pike]]

What the dashboard will do is run compare-dirs of en-US vs individual locales. For the existing setup, it's crucial that en-US is a sibling repo to the l10n ones. I'll probably pair the gaia tree with a Gaia app and appversion, and then things should show up on team pages and dashboards. I wouldn't open that up for sign-offs yet.

Re 9 - 11, I'd favor the discussion of that outside of this bug.

Comment 2

[Staś Małolepszy :stas]

Oh gotcha, so no l10n.ini, and use compare-dirs instead?  That sounds good indeed.

Comment 3

[Staś Małolepszy :stas]

Axel:  Who, in your opinion, should be pushing to gaia-l10n/en-US?  Should we give out push permissions to the developers?  Or have them file bugs with patches that we land ourselves?  I'm looking for a process that's easy for developers used to working with git, but also that scales well beyond three locales and works well with string freezes.

Help wanted :)

Comment 4

[Axel Hecht [:Pike]]

I think the gaia guys should have a defined set of people landing. If nothing else, that's what we did for the other groups with this structure like sync.

Comment 5

[Staś Małolepszy :stas]

Axel, can we close this now?

Comment 6

[Axel Hecht [:Pike]]

Yeah, let's mark bugs FIXED, because it's awesome.

Comment 7

[Axel Hecht [:Pike]]

tools tsunami, sorry.