MPL 2 upgrade for l10n

[reader]

Hi Axel and all,

What we localizer should do to upgrade l10n file license to MPL 2.0?
# To share info with localizers, let me ask here, not on bugzilla.

We should not touch license until compare-locales bug will be fixed?
https://bugzilla.mozilla.org/show_bug.cgi?id=721053

In the bug 716479, gerv wrote:
https://bugzilla.mozilla.org/show_bug.cgi?id=716479
> The current plan is to relicense the US English repo (bug 716478),
> wait one cycle and see what work remains to be done.

Do you have a plan to upgrade whole l10n files?
We should not upgrade by ourselves and just need wait to be upgraded?

In that case, don't do it for ja/ja-JP-mac locale and share your script
to upgrade the license of l10n files. We have separate repository from
which we generate both ja/ja-JP-mac files and we should use script for
this repository:
http://code.google.com/p/mozja/

[Axel Hecht]

The plan is as follows:

- wait for en-US to get relicensed
- for most teams, their toolchains are going to transport that to their
l10n files, either on central or aurora
- wait for that train to go through aurora
- look at the rest, and relicense that with Gerv's script, aurora and
possibly central, depending on locale.
-- apparently that script includes black voodoo magic, Gerv really
prefers to run that himself.

For Japanese, I'd suggest to file a bug once we have en-US relincensed,
CC Gerv and ask him to run the script on your upstream repo.

Axel

[reader]

It's clear now. Thanks!

I'll file a bug for ja/ja-JP-mac once en-US re-licensed and gerv start
working for other locales.

> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n