512491 - Need l10n repos for Weave

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Dan Mills [:thunder]]

We need we-accessible repositories for Weave localization.  They need to be web-accessible.

Comment 1

[Axel Hecht [:Pike]]

To add some additional detail:

We need an individual repository per locale, so the repo names should follow some pattern including the locale code.

If the list of repositories can be accessed as a directory listing like l10n-central http://hg.mozilla.org/l10n-central/?style=raw, that's a plus.

The repos should have write permissions to the localizer ldap group, and if possible, the weave team.

Hooks should be pushlog and single-head, at least.

We'll come up with a list of locales later, in a first step we need to find the right pattern and spot where they'll go.

Comment 2

[Cédric Corazza]

If you might, I would like to add a localizer point of view:

- It would be nice not to have yet another repo to deal with
- As Weave is tight to the version number of Firefox, it would be nice to have it in the current l10n Mercurial repos, maybe in ab-CD/extensions or in a new directory, like ab-CD/projects or ab-CD/labs

Usually, Add-ons are localized in Babelzilla site so it's a totally new situation.

My two cents

Comment 3

[Mike Connor [:mconnor]]

Weave is not tied to Firefox versioning or releases, and we will continue to push updates faster than Firefox releases.

Comment 4

[Axel Hecht [:Pike]]

I think that sethb addressed Cedric's comment, at least to some extent. When we did the collector extension lately, babelzilla wasn't too popular.

Opt-ins are tickling in in this thread, http://groups.google.com/group/mozilla.dev.l10n/browse_frm/thread/51117d7e781170c7#.

Zandr, no worries, we'll extract a list. I or Seth will pick that up once you figured out where to put things. If you're playful and figure that you need a sample to get going, fr, sk, or fa are likely to be the earliest birds.

Comment 5

[Rimas Kudelis [use needinfo to ping]]

Bug 453534 for Penelope.

Comment 6

[Rimas Kudelis [use needinfo to ping]]

Just FYI: bug 453534 was an equivalent for Penelope. After all the discussion it was decided that localizers should commit to the Penelope's repository itself.

Comment 7

[Mike Connor [:mconnor]]

That was their choice, and I don't think it's ideal (due to much more frequent rebasing for everyone, plus merging is easy to get wrong), or especially relevant.  The localizers just need repos set up on the server (which isn't that complicated) and then it's up to us to sort out the build scripting pieces to actually build it.

Comment 8

[matthew zeier [:mrz]]

What's the outcome here?  What do you need IT to do?

Comment 9

[Ragavan S [:rags]]

(In reply to comment #8)
> What's the outcome here?  What do you need IT to do?

We've basically put this on hold for the next couple of weeks at least while we rewrite major parts of the UI for 1.0 beta. My guess is we'll (mconnor will) get back to this in about 3 weeks or so.

Comment 10

[matthew zeier [:mrz]]

Great - re-open when you're ready.

Comment 11

[Seth Bindernagel]

Ragavan,

Can you give me and Axel an update in this bug as to when we need to reopen this and get going with establishing the individual repositories for Weave Sync?  We will need to do this with enough time in advance of the "actual l10n" work.  Should we start on this now?

Comment 12

[Mike Connor [:mconnor]]

Yes, we should start now.

bug 526078 is tracking finalization of strings.  When that is resolved, we will be calling that string frozen for 1.0.

Comment 13

[matthew zeier [:mrz]]

Please re-open when you're ready.

Comment 14

[Zandr Milewski [:zandr]]

OK, this is now blocking other bugs.

What do these repos need to be shaped like. Do you need clones of the existing repo(s)? What should they be called? Do we have a template for this?

Comment 15

[Mike Connor [:mconnor]]

It's okay if they're empty repos, but I'll need an en-US master.  Apparently we can use hg convert to split off a subset of a repo into a standalone repo, which is what I'll do to give localizers a base en-US repo they can pull and merge.

hg pull https://hg.mozilla.org/weave-l10n/en-US
<modify>
hg push ssh://hg.mozilla.org/weave-l10n/ab-CD

Axel, is there a good list of initial repos to create?

Comment 16

[Axel Hecht [:Pike]]

I don't think we need to bother about the internals of the l10n workflow.

There are a few interesting bits about these repos:

We'll have a flock of repos beneath weave-l10n, and they'll all be set to hg_l10n permissions, but the en-US repo. That should have the same permissions as the weave repo.

Scraping http://groups.google.com/group/mozilla.dev.l10n/browse_frm/thread/51117d7e781170c7/c1a51ad43737bc00?lnk=gst, the list of locales interested are:

ar be ca de el es-AR es-CL es-ES fa fr fy-NL gl he ja ja-JP-mac lt pl ro ru si sk sl sq sr tr vi zh-CN zh-TW

The hg hooks should be single head and pushlog, as usual. No tree closure hooks or somesuch needed.

I'm not sure if weave-l10n should be in the labs dir or not, I guess it'd make sense to have it as a sibling to the weave repo.

Comment 17

[Mike Connor [:mconnor]]

I think we probably should move stuff out of /labs since Weave isn't really a Labs project anymore.

Comment 18

[Zandr Milewski [:zandr]]

Moving over to Aravind, since we're now moving this out of /labs.

He says he'll be able to work on it next week.

Comment 19

[Aravind Gottipati [:aravind]]

So a couple of questions here..

1.  Where do I clone the initial en-US repo from?

2. Do the l10n repos need to be empty or clones of the en-US repo?

Comment 20

[Axel Hecht [:Pike]]

Mike, I guess all of them should be empty, right? At least the non-en-US ones should be.

Comment 21

[Mike Connor [:mconnor]]

They should be empty, including the en-US one, and I'll get the en-US one populated.

Comment 22

[Aravind Gottipati [:aravind]]

All these repos should be ready now.  Perms set to l10n, I also checked in a chance to make the weave-l10n footer show up in the main page, but I am not sure how to check the file into the HG_1.2_COMPATIBLE tag on it.

In anycase, these repos should be all set for you to checkin/etc..

Comment 23

[Rimas Kudelis [use needinfo to ping]]

I don't quite get why we needed a separate en-US repo. Localizers have been cloning mozilla-central and comm-central from the very move to hg, and noone cared to split en-US from those too. Isn't weave much *much* smaller than that? Or did somebody object cloning it fully?

Comment 24

[Axel Hecht [:Pike]]

The weave team would like to be a tad more experimental about their landings of localizable strings, and will convert those that stuck over to the en-US repository, which is what localizers actually should care about. That probably excludes a few of you that want to help the weave team in finding problems they land before they expose it to the wider l10n community.

Comment 25

[Gregory Szorc [:gps]]

https://hg.mozilla.org/hgcustom/version-control-tools/rev/5519623f4eaa