989865 - git url for http://hg.mozilla.org/releases/l10n/

Status: RESOLVED INCOMPLETE

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Description

[Kai-Zhen Li [:seinlin][:kli]]

Is it possible to have git access url for all repos under http://hg.mozilla.org/l10n/?

For example, 

Now we can find 
https://git.mozilla.org/releases/l10n/ca/gecko.git
which is mapping to
http://hg.mozilla.org/releases/l10n/mozilla-beta/ca/

But we can't find
https://git.mozilla.org/releases/l10n/bn-BD/gecko.git
for
http://hg.mozilla.org/releases/l10n/mozilla-release/bn-BD/

Comment 1

[Joe Cheng [:jcheng] (please needinfo)]

Hi Chris, is it something rel.eng can look into? Thanks

Comment 2

[Axel Hecht [:Pike]]

We don't localize gecko for any locales but pt-BR, es, pl.

If you want to change that, that's a different project.

Note that by bug 967282, the gecko content is probably wrong, too.

Comment 3

[Hal Wine [:hwine] (leaving Jan 17, ping on slack if needed)]

Axel is correct - l10n repositories are only created on as-needed basis for b2g. All initial coordination and approval happens with the l10n team.

Comment 4

[Axel Hecht [:Pike]]

This actually has nothing to do with localization at all, moving over to repo stuff.

Comment 5

[Hal Wine [:hwine] (leaving Jan 17, ping on slack if needed)]

Okay, since the bug has made full circle, it sounds like we have a changing business requirement. :)

We only mirror gaia l10n repositories to git.m.o on request of the l10n team. To date, we've only mirrored those l10n repos needed by partners to build specific deliverables.

The current process served several purposes:
 a) ensured l10n was in the loop on new gaia/gecko locales
 b) a conscious decision was made regarding which locales would ship with which versions
 c) minimizing churn during an evolving build process.

The churn (c) has been decreasing, so is no longer a real blocker. 

However, both the gecko and gaia l10n repos are owned by the l10n team, and we administer the replication per their processes. 

Axel: can you help me reconcile comment 2 with comment 4?
 - comment 2 implies we're already mirroring all relevant gecko l10n repos
 - comment 4 implies you may want to change the rules for which gecko l10n repos get converted.

Kai-Zhen: can you clarify the use case for the git version of these? In particular is it related to building b2g for a device, or just having read only access while developing?

Comment 6

[Axel Hecht [:Pike]]

I talked to Vivien just two days ago about what we ship in terms of gecko l10n on devices, and he was "oh? oh! oh :-(". But didn't have an answer really either.

I'm afraid I can't reconcile, tbh.

I guess I'd be looking for a product decision on the fx os side, and then we could eventually build out localizations for what's needed. But at this point, nobody seems to know what's "needed", nor does there seem to be a driving force to figure this out.

Comment 7

[Kai-Zhen Li [:seinlin][:kli]]

Hwine, Actually this is requested by partner. AIK, they want to add these urls into their manifest file and then they can use repo to maintain their l10n build. 

BTW, if gecko-l10n is not a must for Firefox OS build, I think mirror all gaia-l10n is enough. Can anyone help to confirm this?

Comment 8

[Hal Wine [:hwine] (leaving Jan 17, ping on slack if needed)]

Two points:
 1) the git.mozilla.org l10n repositories are read only. If the partner wants to contribute translations for gecko or gaia, they need to do so via the existing l10n mechanisms which utilize repositories on hg.mozilla.org. Axel can provide details on that process.

 2) All repositories required for any FFOS localization Mozilla supports are already both:
   a) on git.mozilla.org
   b) referenced in the manifests

So, this appears to ultimately be a request for Mozilla to support additional gecko locales for FFOS. And, perhaps a request to change the definition of "supported locale", or define "levels of support".

Both of those are decisions needing approval from the product team and l10n team. Once they have approved, the repositories will appear.

Axel: if you agree, can you pull this bug into the right product group please? Or correct my thinking?

Comment 9

[Axel Hecht [:Pike]]

I think you're right, but I have no idea how one would drive the discussion around gecko localization for fx os.

I'd probably just resolve this INCOMPLETE, and reopen if we learn of a discussion and its outcome.

Comment 10

[Hal Wine [:hwine] (leaving Jan 17, ping on slack if needed)]

resolving INCOMPLETE based on comment 9, see also comment 8 for the bigger picture.

Kai-Zhen - once the product issues are resolved, that new process should make things appear as the partner desires.

Comment 11

[Kai-Zhen Li [:seinlin][:kli]]

Hwine, Thanks!