MozillaWiki - User contributions [en]

L10n:Dictionaries

2025-05-15T15:22:18Z

Flod: Remove Macedonian from list (see bug 1966699)

{{L10navbar}} 

If we ever want to improve our situation with dictionaries, it would be good to know:

* How many different dictionary formats there are
* Which ones different major projects use
* What dictionaries exist in each
* Who knows about their copyright status

To be included in the source tree, and therefore in builds shipped by Mozilla, a dictionary needs to have a licence compatible with the MPL 2.0. Examples of compatible licensing schemes include:

* MPL 2.0
* MPL 1.1/LGPL 2.1/GPL 2.0 tri-licence (the old Mozilla licence)
* Apache 2.0
* [https://www.opensource.org/licenses/bsd-license.php BSD] or [https://www.opensource.org/licenses/mit-license.php MIT]-style licences
* LGPL
* Public domain

Use of some of these licences may require an addition of some text to about:licence. Please file a mozilla.org::Licensing bug when including a new dictionary so the licensing team can check this.

== Afrikaans ==
Afrikaans dictionaries are built for MySpell and aspell by [http://www.translate.org.za translate.org.za]. Releases available at [https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=103504 SourceForge]. They are released under LGPL. --[[User:Friedelwolff|Friedelwolff]] 07:57, 9 Feb 2006 (PST)

== Albanian ==
Albanian has GPL-ed dictionary for Aspell, Ispell and MySpell. The project covering them is available at http://www.shkenca.org/k6i/index_sq.html.

== Arabic ==
There are GPL/LGPL/MPL Hunspell dictionaries for Firefox and Thunderbird 3
on http://ayaspell.sourceforge.net/ site. [[User:Nemethl|Nemethl]] 04:35, 28 January 2008 (PST)

== Armenian ==
[https://addons.mozilla.org/en-US/firefox/addon/armenian-spell-checker-diction Armenian spell checker dictionary] [[User:Armenzg]]

== Asturian ==
Hunspell dictionary based on Aspell for Firefox (2.0 and above) and Thunderbird (2.0a1 and above), under Mozilla tri-license. Actual version is 0.04 ([https://addons.mozilla.org/en-US/firefox/addon/Correutor_asturianu/ download]).

== Basque ==
MySpell (Firefox 2) and Hunspell (Firefox 3) dictionaries, licensed under GPL:
[http://www.euskara.euskadi.net/r59-20660/eu/contenidos/informacion/euskarazko_softwarea/eu_9567/xuxen.html http://www.euskara.euskadi.net/r59-20660/eu/contenidos/informacion/euskarazko_softwarea/eu_9567/xuxen.html].

== Breton [br] ==
Hunspell dictionary provided by the An Drouizig team (http://www.drouizig.org). It is the same dictionary as in OpenOffice.org. Licensed under the Mozilla tri-license

== Bulgarian [bg] ==
There is only one project dealing with free Bulgarian dictionaries and its releases can be found in [https://sourceforge.net/project/showfiles.php?group_id=52198 bgoffice Sourceforge project files]. Since 2010-04-15, the license is tri-licensed GPLv2 (or later) / LGPLv2.1 (or later) / MPLv1.1.

== Catalan ==
Catalan dictionaries are available in Hunspell, MySpell and Aspell formats under GPL 2+, LGPL 2.1+ License at https://www.softcatala.org/wiki/Corrector_ortogràfic --[[User:Toniher|Toniher]] ([[User talk:Toniher|talk]]) 06:53, 12 November 2013 (PST)

== Czech ==
The only open Czech dictionary I know is [[https://github.com/tvondra/ispell_czech Ispell]] that was coverted by OOo guys to [[https://lingucomponent.openoffice.org/spell_dic.html MySpell]]. Both dictionaries are under GPL/LGPL. However the original Ispell is kind of abandoned and its author doesn't communicate at all. Therefore, our efforts with relicencing failed.
--[[User:Pawell]]

Update 2017: With [https://wiki.l10n.cz/Kontrola_pravopisu:Nov%C3%BD_slovn%C3%ADk l10n.cz] We are trying to find open data for a new dictionary. So far we have found only data under viral copyleft licenses, so we would end up in the same situation we are now, only the dictionary quality would be slightly better. --[[User:mstanke]]

== Danish ==
An old [http://da.speling.org/ danish dictionary] is available as aspell/ispell/myspell under GPL2. This is used in the add-on on AMO (Used because Thunderbird 2 does not support hunspell).

A newer [http://www.stavekontrolden.dk/ dictionary] is available as hunspell under the MPL/GPL/LGPL tri-license. It is part of the Danish build starting at Firefox 3.5. [https://bugzilla.mozilla.org/show_bug.cgi?id=422162 Bug 422162]

== Dutch ==
The [https://www.opentaal.org/bestanden dutch dictionary] is available as Hunspell. The project purposely wants to be very open, such that the list can be used anywhere. Therefore, it is available under BSD and CC-by.

== German ==
Unfortunately cannot ship with Firefox, only as add-ons ([https://addons.mozilla.org/addon/german-dictionary/ German], [https://addons.mozilla.org/addon/german-dictionary-extended-for/ extended for Austria], [https://addons.mozilla.org/addon/german-dictionary-switzerland/ variant for Switzerland]), as we are using the same as LibreOffice, which is the [https://www.j3e.de/ispell/igerman98/ igerman98] dictionary from Björn Jacke, licensed under GPL v2/v3 and the OASIS distribution license agreement.

== Hebrew ==
OpenOffice.org has a localized version in hebrew, that uses the [http://www.ivrix.org.il/projects/spell-checker/ Hspell] format, which is similar to MySpell. They converted it to MySpell for use with mozilla, and it's available [http://dictionaries.mozdev.org/installation.html here]. the MySpell format is GPL, and i think Hspell too. [[User:Tsahi|Tsahi]]

== Hungarian ==
There are new MySpell (Firefox 2) and Hunspell (Firefox 3) add-ons on the [http://magyarispell.sourceforge.net/ Hungarian spelling dictionary site].
Unfortunately, Hungarian add-on 1.1.3 of Mozilla Add-on site is bad, see
[https://bugzilla.mozilla.org/show_bug.cgi?id=412386 Bug 412386].
Hunspell dictionary is licensed under MPL, so we would like it, as default spelling dictionary of the Hungarian localized versions of Mozilla products:
[https://bugzilla.mozilla.org/show_bug.cgi?id=414344 Bug 414344]. [[User:Nemethl|Nemethl]] 04:25, 28 January 2008 (PST)

+1 [[User:Timar|Timar]] 04:40, 28 January 2008 (PST)

== Indonesian ==
MySpell id_ID dictionary is provided by OOo under GPL v2 [https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/id_ID.zip]. License notes: https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/README_id_ID.txt (in Indonesian and English). There is aspell dictionaries under GPL v2 too in [https://ftp.gnu.org/gnu/aspell/dict/id aspell project] made by the same author.
The author (Benitius Brevoort) is willing to make the dictionary files from OOo available under GPLv2/LGPLv2.1/MPLv1.1 licenses to be used in Mozilla products. The email conversation and licenses is available at https://www.ewesewes.net/fxspellcheck/permissions.txt. We would like this dictionary to be included in the Firefox 3 release, see [https://bugzilla.mozilla.org/show_bug.cgi?id=417095 Bug 417095]
--[[User:Rodin|Rodin]]

== Irish ==
The free Irish dictionary is available in aspell/ispell/myspell formats, licensed under the GPL. See http://borel.slu.edu/ispell/
--[[User:Kscanne|Kscanne]]

== Italian ==
The free Italian dictionary is available in aspell/myspell/OOo formats and as an .xpi for Mozilla, licensed only under the GPL. We asked about relicensing it, but the answer was negative. See [http://linguistico.sourceforge.net/ Linguistico] project.
--[[User:Prometeo|Prometeo]]

== Kurdish ==
The Kurdish free dictonary is available as aspell/ispell/myspell, licensed under the GPL. If necessary, we can license it under something else, too. The URL is https://sourceforge.net/projects/myspellkurdish --[[User:Erdal Ronahi|Erdal Ronahi]] 07:00, 21 Feb 2006 (PST)

== Latvian ==
Latvian myspell dictionary is available under a BSD licence from https://sourceforge.net/projects/openoffice-lv/.

== Lithuanian ==
Lithuanian ispell/aspell/myspell dictionary is available under a BSD licence from https://files.akl.lt/ispell-lt/.

== Polish ==

The Polish free dictonary is available as aspell/ispell/myspell, licensed under the MPL/GPL/LGPL and CC-SA: https://www.sjp.pl/

Other projects using this dictionary:
* OpenOffice.org (it uses the older, GPL/CC-SA licensed version, see https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/README_pl_PL.txt )

[[User:Marcoos|Marcoos]] 10:04, 19 July 2006 (PDT)

== Portuguese ==

The base dictionaries come from Project Natura's myspell dictionary. Fore Firefox 2 the dictionaries were licensed GPL2/BSD. In the meantime the license changed to GPL3. They've offered a triple-licensed (GPL2+, LGPL2.1+, MPL1.1) version for Firefox.

Dictionaries: https://natura.di.uminho.pt/natura/natura?&topic=Dicion%E1rios

[[User:JoaoNeves|Joao Miguel Neves]] 15:51, 12 September 2006 (WET)

== Romanian ==

The hunspell dictionaries are available at http://rospell.sourceforge.net/index.html , there's a google group also at https://groups.google.com/forum/#!forum/rospell . The dictionaries are released under Mozilla tri-license: GPL 2.0/LGPL 2.1/MPL 1.1 .

--[[User:Alexxed|alexxed]] 10:44, 3 May 2008 (PDT)

== Russian ==
There are three Russian Myspell dictionaries in Openoffice (all of them were converted from ispell format) - two of them are licensed under BSD License ( see ftp://scon155.phys.msu.ru/pub/russian/ispell/LICENSE ) and one is licensed under GPL/LGPL/MPL/CC-SA. --[[User:Unghost|Unghost]]

== Slovak ==
The open Slovak dictionaries are maintained by [[http://sk-spell.sk.cx/ sk-spell]] project. Both ispell and aspell dictionaries are released under GPL/LGPL. The myspell dictionary is licensed under GPL / LGPL / MPL
--[[User:Branor]]

== Serbian ==
The Serbian dictionary is made with Myspell. It was produced by Igor Miletić (Игор Милетић), based on the Serbian Aspell dictionary made by Goran Rakić (Горан Ракић). See [https://srpski.org/aspell/index-en.html Serbian Aspell]. The dictionary is released under MPL, GPL, and LGPL, the proof of which is given in the LICENSE.txt file of the localized spell checker directory.
[[User:Filmil|filmil]]

== Swedish [sv-SE] ==
A Swedish Hunspell dictionary made by [https://addons.mozilla.org/firefox/user/g%C3%B6ran-andersson/ Göran Andersson] is available from [https://addons.mozilla.org/firefox/addon/g%C3%B6rans-hemmasnickrade-ordli/ AMO]. The dictionary is released under LGPL 3.0.
([[User:Hasse|Hasse]],
[[User:Lakrits|Lakrits]])

== Thai [th] ==

Thai Hunspell dictionary (2006-12-12) - [https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/th_TH.zip zipped], from OpenOffice.org; [https://rpmfind.net//linux/RPM/fedora/8/i386/hunspell-th-0.20061212-1.fc7.noarch.html RPM], from Fedora 8.

Distributed in LGPL (as stated in RPM).

Maintained by Sila Chunwijitra <hin # opentle org>.

Words in the dictionary are partially from NECTEC's Lexitron dictionary ([https://dict.longdo.com/about/hintcontents/lexitron-license.txt license]), with additional geographical names, removal of words with Mai Yamok (repetition mark).

== Ukrainian [uk] ==
There is a project which produces myspell/aspell/ispell Ukrainian dictionaries from single source. More information can be found on wiki page of [https://code.google.com/p/spell-uk/wiki/aspell_uk Knowledge base for Ukrainian language]. Downloads, CVS etc can be found on [https://sourceforge.net/projects/ispell-uk/ SourceForge].
These spell dictionaries distributed under GPL, LGPL, and MPL.

== Vietnamese ==
There's currently an Aspell dictionary for Vietnamese that is licensed under the LGPL. [https://ftp.gnu.org/gnu/aspell/dict/0index.html] I've been contacted by someone creating a spellchecker for a Vietnamese distribution of OpenOffice.org (Hunspell?). A demo of that spellchecker is available. [https://wiki.openoffice.org/wiki/Dictionaries#Vietnamese_.28Vietnam.29] I haven't tried either, but I'd imagine creating a Vietnamese spell checker is a bit more straightforward than an English one, say. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 01:25, 7 June 2007 (PDT)

There's now a [https://code.google.com/p/hunspell-spellcheck-vi/ Hunspell dictionary] for Vietnamese, licensed under GPL v3. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 16:36, 21 May 2008 (PDT)

:I've packaged the dictionary as an extension, [https://addons.mozilla.org/en-US/firefox/addon/7479 Vietnamese Dictionary]. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 22:51, 17 June 2008 (PDT)

:The Hunspell dictionaries are now bundled with the Vietnamese localizations of Firefox 3.5 and above and Thunderbird 3.0 and above. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 02:16, 5 July 2009 (UTC)

The Vietnamese Hunspell dictionary project has moved from Google Code [https://github.com/1ec5/hunspell-vi to GitHub]. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 04:21, 10 November 2014 (PST)

The dictionary has been removed from the Vietname repository (see [https://bugzilla.mozilla.org/show_bug.cgi?id=1912392 bug 1912392]). As stated at the top of the page, dictionaries released under GPL are not suitable.

== Walloon (wa) ==
There is a Walloon dictionaries being enriched; it's main target is aspell, but myspell is easily built from it (there is a "make myspell" rule); also a rule to make an XPI for firefox; and a (quite rude) rule to make a myspell for OOo (copying the files to local directory tree, ouch :) )

It can be downloaded on http://chanae.walon.org/walon/aspell.php
license is LGPL. -- [[User:Srtxg|Srtxg]]

== Zulu ==
Provisional Zulu dictionaries are built for MySpell and aspell by [http://www.translate.org.za translate.org.za]. Releases available at [https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=106128 SourceForge]. They are released under LGPL. --[[User:Friedelwolff|Friedelwolff]] 07:57, 9 Feb 2006 (PST)

[[category:L10n]]

Mastodon

2025-01-22T07:17:51Z

Flod: Add mozilla-l10n, flod

{{stub}}

Mozilla has an official Mastodon account at [https://mastodon.social/@mozillaofficial @mozillaofficial@mastodon.social] and there are Mozillians with personal accounts and their own sites directly connected to the fediverse if you’re interested in following any of them.
__TOC__

== Mozilla accounts ==
* [https://mastodon.social/@mozillaofficial @mozillaofficial@mastodon.social]
* [https://mastodon.social/@FirefoxDevTools @FirefoxDevTools@mastodon.social]
* [https://mastodon.social/@firefoxnightly @firefoxnightly@mastodon.social]
* [https://fosstodon.org/@mozilla_l10n/ @mozilla_l10n/@fosstodon.social]



Automated:

* [https://fosstodon.org/@planetmozilla @planetmozilla@fosstodon.org] — posts from [[Planet Mozilla]]

== Mozillians ==
Personal fediverse addresses of Mozillians, feel free to add yourself, sorted alphabetically by family name.

Copy & paste these into your reader/client to follow:
* Wim Benes - [https://mastodon.frl/@Fjoerfoks <kbd>@Fjoerfoks@mastodon.frl</kbd>]
* Paul Bone - [https://fosstodon.org/@pbone <kbd>@pbone@fosstodon.org</kbd>]
* Frederik Braun (freddy) - <kbd>@freddy@security.plumbing</kbd>
* [[User:dbryant | David Bryant ]] 
* [[Tantek Çelik]] — <kbd>tantek.com</kbd> — or — <kbd>@tantek.com@tantek.com</kbd>
* Pascal Chevrel [https://mamot.fr/@pascalchevrel <kbd>@pascalchevrel@mamot.fr</kbd>]
* [[User:dannycolin | Danny Colin (:sdk)]] - [https://floss.social/@dannycolin <kbd>@dannycolin@floss.social</kbd>]
* [[User:mconley | Mike Conley (:mconley)]] - [https://fosstodon.org/@mconley <kbd>@mconley@fosstodon.org</kbd>]
* [[User:jrconlin| j-r conlin]] - [https://soc.jrconlin.com/@jrconlin <kbd>@jrconlin@soc.jrconlin.com</kbd>]
* [[User:SpikeUK1|Chris Foote (Spike)]] – @tenbus_uk@mstdn.social
* Alex Gibson (agibson) 
* [[User:mhammond|Mark Hammond (:markh)]] - [https://aus.social/@skippyhammond <kbd>@skippyhammond@aus.social</kbd>]
* Dale Harvey - [https://toot.cafe/@dale <kbd>@dale@toot.cafe</kbd>]
* Stephen Hood — [https://fosstodon.org/@stlhood <kbd>@stlhood@fosstodon.org</kbd>]
* Michael Kohler – @mkohler@fosstodon.org
* David Lawrence - @dklawren@fosstodon.org
* [[User:Pmclanahan|Paul McLanahan]] - [https://fosstodon.org/@pmac <kbd>@pmac@fosstodon.org</kbd>]
* [[User:Zcorpan|Simon Pieters]] 
* Greg Stoll - <kbd>@gregstoll@techhub.social</kbd> (https://techhub.social/@gregstoll)
* [[User:rupert|Rupert Parry]] - <kbd>@rupert@mstdn.social</kbd> (https://mstdn.social/@rupert)
* [[User:Krosylight|Kagami Rosylight]] - <kbd>@krosylight@fosstodon.org</kbd> (https://fosstodon.org/@krosylight)
* [[User:Gsvelto|Gabriele Svelto]] - [https://fosstodon.org/@gabrielesvelto <kbd>@gabrielesvelto@fosstodon.org</kbd>]
* Aaron Train - [https://fosstodon.org/@AaronMT <kbd>@AaronMT@fosstodon.org</kbd>]
* Vincent Tunru — [https://fosstodon.org/@VincentTunru <kbd>@VincentTunru@fosstodon.org</kbd>]
* Michael Verdi - [https://mastodon.art/@verdi @verdi@mastodon.art]
* [[User:jwhitlock|John Whitlock]] - [https://mastodon.social/@jwhitlock <kbd>@jwhitlock@mastodon.social</kbd>]
* Emma Zühlcke [https://mastodon.social/@pbz <kbd>@pbz@mastodon.social</kbd>]
* Paul Wright [https://mstdn.social/@plwt <kbd>@plwt@mstdn.social</kbd>]
* [[User:flod|flod]] [https://fosstodon.org/@flod <kbd>@flod@fosstodon.org</kbd>]

== French-speaking community (mostly in French) ==
* @Mozilla@mamot.fr (Mozilla & community news)
* [https://people.mozilla.org/p/hellosct1 Christophe Villeneuve] – @hellosct1@mamot.fr
* [https://people.mozilla.org/p/Mozinet Mozinet] – @Mozinet@mamot.fr

== Browser Extensions ==
* [https://addons.mozilla.org/en-US/firefox/addon/mastodon-simplified-federation/ Simplified Federation] - Simplifies following or interacting with other users on remote Mastodon instances in the Fediverse. It skips the “Enter your Mastodon handle” popup and takes you to your own “home” instance, without entering your Mastodon handle on remote instances.

== History ==
=== mozilla.social ===
{{main|mozilla.social}}
Mozilla.social [https://web.archive.org/web/20241209024733/https://mozilla.social/@mozilla/113153943609185249 shut down on December 17, 2024].

More information:
* [https://mozilla.social/settings/export How to download your data]
* [https://support.mozilla.org/en-US/kb/mozilla-social-faq FAQ including how to migrate your account to another instance]

== See Also ==
* [[Planet Mozilla]]
* [[dweb]]

L10n:Dictionaries

2024-12-04T10:53:20Z

Flod: Remove en-GB (broken link)

{{L10navbar}} 

If we ever want to improve our situation with dictionaries, it would be good to know:

* How many different dictionary formats there are
* Which ones different major projects use
* What dictionaries exist in each
* Who knows about their copyright status

To be included in the source tree, and therefore in builds shipped by Mozilla, a dictionary needs to have a licence compatible with the MPL 2.0. Examples of compatible licensing schemes include:

* MPL 2.0
* MPL 1.1/LGPL 2.1/GPL 2.0 tri-licence (the old Mozilla licence)
* Apache 2.0
* [https://www.opensource.org/licenses/bsd-license.php BSD] or [https://www.opensource.org/licenses/mit-license.php MIT]-style licences
* LGPL
* Public domain

Use of some of these licences may require an addition of some text to about:licence. Please file a mozilla.org::Licensing bug when including a new dictionary so the licensing team can check this.

== Afrikaans ==
Afrikaans dictionaries are built for MySpell and aspell by [http://www.translate.org.za translate.org.za]. Releases available at [https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=103504 SourceForge]. They are released under LGPL. --[[User:Friedelwolff|Friedelwolff]] 07:57, 9 Feb 2006 (PST)

== Albanian ==
Albanian has GPL-ed dictionary for Aspell, Ispell and MySpell. The project covering them is available at http://www.shkenca.org/k6i/index_sq.html.

== Arabic ==
There are GPL/LGPL/MPL Hunspell dictionaries for Firefox and Thunderbird 3
on http://ayaspell.sourceforge.net/ site. [[User:Nemethl|Nemethl]] 04:35, 28 January 2008 (PST)

== Armenian ==
[https://addons.mozilla.org/en-US/firefox/addon/armenian-spell-checker-diction Armenian spell checker dictionary] [[User:Armenzg]]

== Asturian ==
Hunspell dictionary based on Aspell for Firefox (2.0 and above) and Thunderbird (2.0a1 and above), under Mozilla tri-license. Actual version is 0.04 ([https://addons.mozilla.org/en-US/firefox/addon/Correutor_asturianu/ download]).

== Basque ==
MySpell (Firefox 2) and Hunspell (Firefox 3) dictionaries, licensed under GPL:
[http://www.euskara.euskadi.net/r59-20660/eu/contenidos/informacion/euskarazko_softwarea/eu_9567/xuxen.html http://www.euskara.euskadi.net/r59-20660/eu/contenidos/informacion/euskarazko_softwarea/eu_9567/xuxen.html].

== Breton [br] ==
Hunspell dictionary provided by the An Drouizig team (http://www.drouizig.org). It is the same dictionary as in OpenOffice.org. Licensed under the Mozilla tri-license

== Bulgarian [bg] ==
There is only one project dealing with free Bulgarian dictionaries and its releases can be found in [https://sourceforge.net/project/showfiles.php?group_id=52198 bgoffice Sourceforge project files]. Since 2010-04-15, the license is tri-licensed GPLv2 (or later) / LGPLv2.1 (or later) / MPLv1.1.

== Catalan ==
Catalan dictionaries are available in Hunspell, MySpell and Aspell formats under GPL 2+, LGPL 2.1+ License at https://www.softcatala.org/wiki/Corrector_ortogràfic --[[User:Toniher|Toniher]] ([[User talk:Toniher|talk]]) 06:53, 12 November 2013 (PST)

== Czech ==
The only open Czech dictionary I know is [[https://github.com/tvondra/ispell_czech Ispell]] that was coverted by OOo guys to [[https://lingucomponent.openoffice.org/spell_dic.html MySpell]]. Both dictionaries are under GPL/LGPL. However the original Ispell is kind of abandoned and its author doesn't communicate at all. Therefore, our efforts with relicencing failed.
--[[User:Pawell]]

Update 2017: With [https://wiki.l10n.cz/Kontrola_pravopisu:Nov%C3%BD_slovn%C3%ADk l10n.cz] We are trying to find open data for a new dictionary. So far we have found only data under viral copyleft licenses, so we would end up in the same situation we are now, only the dictionary quality would be slightly better. --[[User:mstanke]]

== Danish ==
An old [http://da.speling.org/ danish dictionary] is available as aspell/ispell/myspell under GPL2. This is used in the add-on on AMO (Used because Thunderbird 2 does not support hunspell).

A newer [http://www.stavekontrolden.dk/ dictionary] is available as hunspell under the MPL/GPL/LGPL tri-license. It is part of the Danish build starting at Firefox 3.5. [https://bugzilla.mozilla.org/show_bug.cgi?id=422162 Bug 422162]

== Dutch ==
The [https://www.opentaal.org/bestanden dutch dictionary] is available as Hunspell. The project purposely wants to be very open, such that the list can be used anywhere. Therefore, it is available under BSD and CC-by.

== German ==
Unfortunately cannot ship with Firefox, only as add-ons ([https://addons.mozilla.org/addon/german-dictionary/ German], [https://addons.mozilla.org/addon/german-dictionary-extended-for/ extended for Austria], [https://addons.mozilla.org/addon/german-dictionary-switzerland/ variant for Switzerland]), as we are using the same as LibreOffice, which is the [https://www.j3e.de/ispell/igerman98/ igerman98] dictionary from Björn Jacke, licensed under GPL v2/v3 and the OASIS distribution license agreement.

== Hebrew ==
OpenOffice.org has a localized version in hebrew, that uses the [http://www.ivrix.org.il/projects/spell-checker/ Hspell] format, which is similar to MySpell. They converted it to MySpell for use with mozilla, and it's available [http://dictionaries.mozdev.org/installation.html here]. the MySpell format is GPL, and i think Hspell too. [[User:Tsahi|Tsahi]]

== Hungarian ==
There are new MySpell (Firefox 2) and Hunspell (Firefox 3) add-ons on the [http://magyarispell.sourceforge.net/ Hungarian spelling dictionary site].
Unfortunately, Hungarian add-on 1.1.3 of Mozilla Add-on site is bad, see
[https://bugzilla.mozilla.org/show_bug.cgi?id=412386 Bug 412386].
Hunspell dictionary is licensed under MPL, so we would like it, as default spelling dictionary of the Hungarian localized versions of Mozilla products:
[https://bugzilla.mozilla.org/show_bug.cgi?id=414344 Bug 414344]. [[User:Nemethl|Nemethl]] 04:25, 28 January 2008 (PST)

+1 [[User:Timar|Timar]] 04:40, 28 January 2008 (PST)

== Indonesian ==
MySpell id_ID dictionary is provided by OOo under GPL v2 [https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/id_ID.zip]. License notes: https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/README_id_ID.txt (in Indonesian and English). There is aspell dictionaries under GPL v2 too in [https://ftp.gnu.org/gnu/aspell/dict/id aspell project] made by the same author.
The author (Benitius Brevoort) is willing to make the dictionary files from OOo available under GPLv2/LGPLv2.1/MPLv1.1 licenses to be used in Mozilla products. The email conversation and licenses is available at https://www.ewesewes.net/fxspellcheck/permissions.txt. We would like this dictionary to be included in the Firefox 3 release, see [https://bugzilla.mozilla.org/show_bug.cgi?id=417095 Bug 417095]
--[[User:Rodin|Rodin]]

== Irish ==
The free Irish dictionary is available in aspell/ispell/myspell formats, licensed under the GPL. See http://borel.slu.edu/ispell/
--[[User:Kscanne|Kscanne]]

== Italian ==
The free Italian dictionary is available in aspell/myspell/OOo formats and as an .xpi for Mozilla, licensed only under the GPL. We asked about relicensing it, but the answer was negative. See [http://linguistico.sourceforge.net/ Linguistico] project.
--[[User:Prometeo|Prometeo]]

== Kurdish ==
The Kurdish free dictonary is available as aspell/ispell/myspell, licensed under the GPL. If necessary, we can license it under something else, too. The URL is https://sourceforge.net/projects/myspellkurdish --[[User:Erdal Ronahi|Erdal Ronahi]] 07:00, 21 Feb 2006 (PST)

== Latvian ==
Latvian myspell dictionary is available under a BSD licence from https://sourceforge.net/projects/openoffice-lv/.

== Lithuanian ==
Lithuanian ispell/aspell/myspell dictionary is available under a BSD licence from https://files.akl.lt/ispell-lt/.

== Macedonian [mk] ==
The macedonian dictionary is public domain.

== Polish ==

The Polish free dictonary is available as aspell/ispell/myspell, licensed under the MPL/GPL/LGPL and CC-SA: https://www.sjp.pl/

Other projects using this dictionary:
* OpenOffice.org (it uses the older, GPL/CC-SA licensed version, see https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/README_pl_PL.txt )

[[User:Marcoos|Marcoos]] 10:04, 19 July 2006 (PDT)

== Portuguese ==

The base dictionaries come from Project Natura's myspell dictionary. Fore Firefox 2 the dictionaries were licensed GPL2/BSD. In the meantime the license changed to GPL3. They've offered a triple-licensed (GPL2+, LGPL2.1+, MPL1.1) version for Firefox.

Dictionaries: https://natura.di.uminho.pt/natura/natura?&topic=Dicion%E1rios

[[User:JoaoNeves|Joao Miguel Neves]] 15:51, 12 September 2006 (WET)

== Romanian ==

The hunspell dictionaries are available at http://rospell.sourceforge.net/index.html , there's a google group also at https://groups.google.com/forum/#!forum/rospell . The dictionaries are released under Mozilla tri-license: GPL 2.0/LGPL 2.1/MPL 1.1 .

--[[User:Alexxed|alexxed]] 10:44, 3 May 2008 (PDT)

== Russian ==
There are three Russian Myspell dictionaries in Openoffice (all of them were converted from ispell format) - two of them are licensed under BSD License ( see ftp://scon155.phys.msu.ru/pub/russian/ispell/LICENSE ) and one is licensed under GPL/LGPL/MPL/CC-SA. --[[User:Unghost|Unghost]]

== Slovak ==
The open Slovak dictionaries are maintained by [[http://sk-spell.sk.cx/ sk-spell]] project. Both ispell and aspell dictionaries are released under GPL/LGPL. The myspell dictionary is licensed under GPL / LGPL / MPL
--[[User:Branor]]

== Serbian ==
The Serbian dictionary is made with Myspell. It was produced by Igor Miletić (Игор Милетић), based on the Serbian Aspell dictionary made by Goran Rakić (Горан Ракић). See [https://srpski.org/aspell/index-en.html Serbian Aspell]. The dictionary is released under MPL, GPL, and LGPL, the proof of which is given in the LICENSE.txt file of the localized spell checker directory.
[[User:Filmil|filmil]]

== Swedish [sv-SE] ==
A Swedish Hunspell dictionary made by [https://addons.mozilla.org/firefox/user/g%C3%B6ran-andersson/ Göran Andersson] is available from [https://addons.mozilla.org/firefox/addon/g%C3%B6rans-hemmasnickrade-ordli/ AMO]. The dictionary is released under LGPL 3.0.
([[User:Hasse|Hasse]],
[[User:Lakrits|Lakrits]])

== Thai [th] ==

Thai Hunspell dictionary (2006-12-12) - [https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/th_TH.zip zipped], from OpenOffice.org; [https://rpmfind.net//linux/RPM/fedora/8/i386/hunspell-th-0.20061212-1.fc7.noarch.html RPM], from Fedora 8.

Distributed in LGPL (as stated in RPM).

Maintained by Sila Chunwijitra <hin # opentle org>.

Words in the dictionary are partially from NECTEC's Lexitron dictionary ([https://dict.longdo.com/about/hintcontents/lexitron-license.txt license]), with additional geographical names, removal of words with Mai Yamok (repetition mark).

== Ukrainian [uk] ==
There is a project which produces myspell/aspell/ispell Ukrainian dictionaries from single source. More information can be found on wiki page of [https://code.google.com/p/spell-uk/wiki/aspell_uk Knowledge base for Ukrainian language]. Downloads, CVS etc can be found on [https://sourceforge.net/projects/ispell-uk/ SourceForge].
These spell dictionaries distributed under GPL, LGPL, and MPL.

== Vietnamese ==
There's currently an Aspell dictionary for Vietnamese that is licensed under the LGPL. [https://ftp.gnu.org/gnu/aspell/dict/0index.html] I've been contacted by someone creating a spellchecker for a Vietnamese distribution of OpenOffice.org (Hunspell?). A demo of that spellchecker is available. [https://wiki.openoffice.org/wiki/Dictionaries#Vietnamese_.28Vietnam.29] I haven't tried either, but I'd imagine creating a Vietnamese spell checker is a bit more straightforward than an English one, say. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 01:25, 7 June 2007 (PDT)

There's now a [https://code.google.com/p/hunspell-spellcheck-vi/ Hunspell dictionary] for Vietnamese, licensed under GPL v3. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 16:36, 21 May 2008 (PDT)

:I've packaged the dictionary as an extension, [https://addons.mozilla.org/en-US/firefox/addon/7479 Vietnamese Dictionary]. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 22:51, 17 June 2008 (PDT)

:The Hunspell dictionaries are now bundled with the Vietnamese localizations of Firefox 3.5 and above and Thunderbird 3.0 and above. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 02:16, 5 July 2009 (UTC)

The Vietnamese Hunspell dictionary project has moved from Google Code [https://github.com/1ec5/hunspell-vi to GitHub]. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 04:21, 10 November 2014 (PST)

The dictionary has been removed from the Vietname repository (see [https://bugzilla.mozilla.org/show_bug.cgi?id=1912392 bug 1912392]). As stated at the top of the page, dictionaries released under GPL are not suitable.

== Walloon (wa) ==
There is a Walloon dictionaries being enriched; it's main target is aspell, but myspell is easily built from it (there is a "make myspell" rule); also a rule to make an XPI for firefox; and a (quite rude) rule to make a myspell for OOo (copying the files to local directory tree, ouch :) )

It can be downloaded on http://chanae.walon.org/walon/aspell.php
license is LGPL. -- [[User:Srtxg|Srtxg]]

== Zulu ==
Provisional Zulu dictionaries are built for MySpell and aspell by [http://www.translate.org.za translate.org.za]. Releases available at [https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=106128 SourceForge]. They are released under LGPL. --[[User:Friedelwolff|Friedelwolff]] 07:57, 9 Feb 2006 (PST)

[[category:L10n]]

L10n:Dictionaries

2024-08-09T08:23:29Z

Flod: Note on Vietnamese dictionary removal

{{L10navbar}} 

If we ever want to improve our situation with dictionaries, it would be good to know:

* How many different dictionary formats there are
* Which ones different major projects use
* What dictionaries exist in each
* Who knows about their copyright status

To be included in the source tree, and therefore in builds shipped by Mozilla, a dictionary needs to have a licence compatible with the MPL 2.0. Examples of compatible licensing schemes include:

* MPL 2.0
* MPL 1.1/LGPL 2.1/GPL 2.0 tri-licence (the old Mozilla licence)
* Apache 2.0
* [https://www.opensource.org/licenses/bsd-license.php BSD] or [https://www.opensource.org/licenses/mit-license.php MIT]-style licences
* LGPL
* Public domain

Use of some of these licences may require an addition of some text to about:licence. Please file a mozilla.org::Licensing bug when including a new dictionary so the licensing team can check this.

== Afrikaans ==
Afrikaans dictionaries are built for MySpell and aspell by [http://www.translate.org.za translate.org.za]. Releases available at [https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=103504 SourceForge]. They are released under LGPL. --[[User:Friedelwolff|Friedelwolff]] 07:57, 9 Feb 2006 (PST)

== Albanian ==
Albanian has GPL-ed dictionary for Aspell, Ispell and MySpell. The project covering them is available at http://www.shkenca.org/k6i/index_sq.html.

== Arabic ==
There are GPL/LGPL/MPL Hunspell dictionaries for Firefox and Thunderbird 3
on http://ayaspell.sourceforge.net/ site. [[User:Nemethl|Nemethl]] 04:35, 28 January 2008 (PST)

== Armenian ==
[https://addons.mozilla.org/en-US/firefox/addon/armenian-spell-checker-diction Armenian spell checker dictionary] [[User:Armenzg]]

== Asturian ==
Hunspell dictionary based on Aspell for Firefox (2.0 and above) and Thunderbird (2.0a1 and above), under Mozilla tri-license. Actual version is 0.04 ([https://addons.mozilla.org/en-US/firefox/addon/Correutor_asturianu/ download]).

== Basque ==
MySpell (Firefox 2) and Hunspell (Firefox 3) dictionaries, licensed under GPL:
[http://www.euskara.euskadi.net/r59-20660/eu/contenidos/informacion/euskarazko_softwarea/eu_9567/xuxen.html http://www.euskara.euskadi.net/r59-20660/eu/contenidos/informacion/euskarazko_softwarea/eu_9567/xuxen.html].

== Breton [br] ==
Hunspell dictionary provided by the An Drouizig team (http://www.drouizig.org). It is the same dictionary as in OpenOffice.org. Licensed under the Mozilla tri-license

== Bulgarian [bg] ==
There is only one project dealing with free Bulgarian dictionaries and its releases can be found in [https://sourceforge.net/project/showfiles.php?group_id=52198 bgoffice Sourceforge project files]. Since 2010-04-15, the license is tri-licensed GPLv2 (or later) / LGPLv2.1 (or later) / MPLv1.1.

== Catalan ==
Catalan dictionaries are available in Hunspell, MySpell and Aspell formats under GPL 2+, LGPL 2.1+ License at https://www.softcatala.org/wiki/Corrector_ortogràfic --[[User:Toniher|Toniher]] ([[User talk:Toniher|talk]]) 06:53, 12 November 2013 (PST)

== Czech ==
The only open Czech dictionary I know is [[https://github.com/tvondra/ispell_czech Ispell]] that was coverted by OOo guys to [[https://lingucomponent.openoffice.org/spell_dic.html MySpell]]. Both dictionaries are under GPL/LGPL. However the original Ispell is kind of abandoned and its author doesn't communicate at all. Therefore, our efforts with relicencing failed.
--[[User:Pawell]]

Update 2017: With [https://wiki.l10n.cz/Kontrola_pravopisu:Nov%C3%BD_slovn%C3%ADk l10n.cz] We are trying to find open data for a new dictionary. So far we have found only data under viral copyleft licenses, so we would end up in the same situation we are now, only the dictionary quality would be slightly better. --[[User:mstanke]]

== Danish ==
An old [http://da.speling.org/ danish dictionary] is available as aspell/ispell/myspell under GPL2. This is used in the add-on on AMO (Used because Thunderbird 2 does not support hunspell).

A newer [http://www.stavekontrolden.dk/ dictionary] is available as hunspell under the MPL/GPL/LGPL tri-license. It is part of the Danish build starting at Firefox 3.5. [https://bugzilla.mozilla.org/show_bug.cgi?id=422162 Bug 422162]

== British English [en-GB] ==
The [[https://en-gb.pyxidium.co.uk/dictionary/en_GB.zip British English dictionary]] is released under the LGPL.

== Dutch ==
The [https://www.opentaal.org/bestanden dutch dictionary] is available as Hunspell. The project purposely wants to be very open, such that the list can be used anywhere. Therefore, it is available under BSD and CC-by.

== German ==
Unfortunately cannot ship with Firefox, only as add-ons ([https://addons.mozilla.org/addon/german-dictionary/ German], [https://addons.mozilla.org/addon/german-dictionary-extended-for/ extended for Austria], [https://addons.mozilla.org/addon/german-dictionary-switzerland/ variant for Switzerland]), as we are using the same as LibreOffice, which is the [https://www.j3e.de/ispell/igerman98/ igerman98] dictionary from Björn Jacke, licensed under GPL v2/v3 and the OASIS distribution license agreement.

== Hebrew ==
OpenOffice.org has a localized version in hebrew, that uses the [http://www.ivrix.org.il/projects/spell-checker/ Hspell] format, which is similar to MySpell. They converted it to MySpell for use with mozilla, and it's available [http://dictionaries.mozdev.org/installation.html here]. the MySpell format is GPL, and i think Hspell too. [[User:Tsahi|Tsahi]]

== Hungarian ==
There are new MySpell (Firefox 2) and Hunspell (Firefox 3) add-ons on the [http://magyarispell.sourceforge.net/ Hungarian spelling dictionary site].
Unfortunately, Hungarian add-on 1.1.3 of Mozilla Add-on site is bad, see
[https://bugzilla.mozilla.org/show_bug.cgi?id=412386 Bug 412386].
Hunspell dictionary is licensed under MPL, so we would like it, as default spelling dictionary of the Hungarian localized versions of Mozilla products:
[https://bugzilla.mozilla.org/show_bug.cgi?id=414344 Bug 414344]. [[User:Nemethl|Nemethl]] 04:25, 28 January 2008 (PST)

+1 [[User:Timar|Timar]] 04:40, 28 January 2008 (PST)

== Indonesian ==
MySpell id_ID dictionary is provided by OOo under GPL v2 [https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/id_ID.zip]. License notes: https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/README_id_ID.txt (in Indonesian and English). There is aspell dictionaries under GPL v2 too in [https://ftp.gnu.org/gnu/aspell/dict/id aspell project] made by the same author.
The author (Benitius Brevoort) is willing to make the dictionary files from OOo available under GPLv2/LGPLv2.1/MPLv1.1 licenses to be used in Mozilla products. The email conversation and licenses is available at https://www.ewesewes.net/fxspellcheck/permissions.txt. We would like this dictionary to be included in the Firefox 3 release, see [https://bugzilla.mozilla.org/show_bug.cgi?id=417095 Bug 417095]
--[[User:Rodin|Rodin]]

== Irish ==
The free Irish dictionary is available in aspell/ispell/myspell formats, licensed under the GPL. See http://borel.slu.edu/ispell/
--[[User:Kscanne|Kscanne]]

== Italian ==
The free Italian dictionary is available in aspell/myspell/OOo formats and as an .xpi for Mozilla, licensed only under the GPL. We asked about relicensing it, but the answer was negative. See [http://linguistico.sourceforge.net/ Linguistico] project.
--[[User:Prometeo|Prometeo]]

== Kurdish ==
The Kurdish free dictonary is available as aspell/ispell/myspell, licensed under the GPL. If necessary, we can license it under something else, too. The URL is https://sourceforge.net/projects/myspellkurdish --[[User:Erdal Ronahi|Erdal Ronahi]] 07:00, 21 Feb 2006 (PST)

== Latvian ==
Latvian myspell dictionary is available under a BSD licence from https://sourceforge.net/projects/openoffice-lv/.

== Lithuanian ==
Lithuanian ispell/aspell/myspell dictionary is available under a BSD licence from https://files.akl.lt/ispell-lt/.

== Macedonian [mk] ==
The macedonian dictionary is public domain.

== Polish ==

The Polish free dictonary is available as aspell/ispell/myspell, licensed under the MPL/GPL/LGPL and CC-SA: https://www.sjp.pl/

Other projects using this dictionary:
* OpenOffice.org (it uses the older, GPL/CC-SA licensed version, see https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/README_pl_PL.txt )

[[User:Marcoos|Marcoos]] 10:04, 19 July 2006 (PDT)

== Portuguese ==

The base dictionaries come from Project Natura's myspell dictionary. Fore Firefox 2 the dictionaries were licensed GPL2/BSD. In the meantime the license changed to GPL3. They've offered a triple-licensed (GPL2+, LGPL2.1+, MPL1.1) version for Firefox.

Dictionaries: https://natura.di.uminho.pt/natura/natura?&topic=Dicion%E1rios

[[User:JoaoNeves|Joao Miguel Neves]] 15:51, 12 September 2006 (WET)

== Romanian ==

The hunspell dictionaries are available at http://rospell.sourceforge.net/index.html , there's a google group also at https://groups.google.com/forum/#!forum/rospell . The dictionaries are released under Mozilla tri-license: GPL 2.0/LGPL 2.1/MPL 1.1 .

--[[User:Alexxed|alexxed]] 10:44, 3 May 2008 (PDT)

== Russian ==
There are three Russian Myspell dictionaries in Openoffice (all of them were converted from ispell format) - two of them are licensed under BSD License ( see ftp://scon155.phys.msu.ru/pub/russian/ispell/LICENSE ) and one is licensed under GPL/LGPL/MPL/CC-SA. --[[User:Unghost|Unghost]]

== Slovak ==
The open Slovak dictionaries are maintained by [[http://sk-spell.sk.cx/ sk-spell]] project. Both ispell and aspell dictionaries are released under GPL/LGPL. The myspell dictionary is licensed under GPL / LGPL / MPL
--[[User:Branor]]

== Serbian ==
The Serbian dictionary is made with Myspell. It was produced by Igor Miletić (Игор Милетић), based on the Serbian Aspell dictionary made by Goran Rakić (Горан Ракић). See [https://srpski.org/aspell/index-en.html Serbian Aspell]. The dictionary is released under MPL, GPL, and LGPL, the proof of which is given in the LICENSE.txt file of the localized spell checker directory.
[[User:Filmil|filmil]]

== Swedish [sv-SE] ==
A Swedish Hunspell dictionary made by [https://addons.mozilla.org/firefox/user/g%C3%B6ran-andersson/ Göran Andersson] is available from [https://addons.mozilla.org/firefox/addon/g%C3%B6rans-hemmasnickrade-ordli/ AMO]. The dictionary is released under LGPL 3.0.
([[User:Hasse|Hasse]],
[[User:Lakrits|Lakrits]])

== Thai [th] ==

Thai Hunspell dictionary (2006-12-12) - [https://ftp5.gwdg.de/pub/openoffice/contrib/dictionaries/th_TH.zip zipped], from OpenOffice.org; [https://rpmfind.net//linux/RPM/fedora/8/i386/hunspell-th-0.20061212-1.fc7.noarch.html RPM], from Fedora 8.

Distributed in LGPL (as stated in RPM).

Maintained by Sila Chunwijitra <hin # opentle org>.

Words in the dictionary are partially from NECTEC's Lexitron dictionary ([https://dict.longdo.com/about/hintcontents/lexitron-license.txt license]), with additional geographical names, removal of words with Mai Yamok (repetition mark).

== Ukrainian [uk] ==
There is a project which produces myspell/aspell/ispell Ukrainian dictionaries from single source. More information can be found on wiki page of [https://code.google.com/p/spell-uk/wiki/aspell_uk Knowledge base for Ukrainian language]. Downloads, CVS etc can be found on [https://sourceforge.net/projects/ispell-uk/ SourceForge].
These spell dictionaries distributed under GPL, LGPL, and MPL.

== Vietnamese ==
There's currently an Aspell dictionary for Vietnamese that is licensed under the LGPL. [https://ftp.gnu.org/gnu/aspell/dict/0index.html] I've been contacted by someone creating a spellchecker for a Vietnamese distribution of OpenOffice.org (Hunspell?). A demo of that spellchecker is available. [https://wiki.openoffice.org/wiki/Dictionaries#Vietnamese_.28Vietnam.29] I haven't tried either, but I'd imagine creating a Vietnamese spell checker is a bit more straightforward than an English one, say. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 01:25, 7 June 2007 (PDT)

There's now a [https://code.google.com/p/hunspell-spellcheck-vi/ Hunspell dictionary] for Vietnamese, licensed under GPL v3. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 16:36, 21 May 2008 (PDT)

:I've packaged the dictionary as an extension, [https://addons.mozilla.org/en-US/firefox/addon/7479 Vietnamese Dictionary]. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 22:51, 17 June 2008 (PDT)

:The Hunspell dictionaries are now bundled with the Vietnamese localizations of Firefox 3.5 and above and Thunderbird 3.0 and above. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 02:16, 5 July 2009 (UTC)

The Vietnamese Hunspell dictionary project has moved from Google Code [https://github.com/1ec5/hunspell-vi to GitHub]. – [[User:Minh Nguyen|Minh Nguyễn]] ([[User talk:Minh Nguyen|talk]], [[Special:Contributions/Minh Nguyen|contribs]]) 04:21, 10 November 2014 (PST)

The dictionary has been removed from the Vietname repository (see [https://bugzilla.mozilla.org/show_bug.cgi?id=1912392 bug 1912392]). As stated at the top of the page, dictionaries released under GPL are not suitable.

== Walloon (wa) ==
There is a Walloon dictionaries being enriched; it's main target is aspell, but myspell is easily built from it (there is a "make myspell" rule); also a rule to make an XPI for firefox; and a (quite rude) rule to make a myspell for OOo (copying the files to local directory tree, ouch :) )

It can be downloaded on http://chanae.walon.org/walon/aspell.php
license is LGPL. -- [[User:Srtxg|Srtxg]]

== Zulu ==
Provisional Zulu dictionaries are built for MySpell and aspell by [http://www.translate.org.za translate.org.za]. Releases available at [https://sourceforge.net/project/showfiles.php?group_id=91920&package_id=106128 SourceForge]. They are released under LGPL. --[[User:Friedelwolff|Friedelwolff]] 07:57, 9 Feb 2006 (PST)

[[category:L10n]]

Release Management/Requesting an Uplift

2024-08-07T05:59:15Z

Flod:

See [[Release_Management/Uplift_rules|the uplift rules Wiki page]] for more information on uplifts.

Please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Conduit&component=General file a bug] if you encounter issues requesting an uplift, or tell us about the problem in #uplift-pilot on Slack.

== Requesting an Uplift ==

Requesting a patch uplift is completed using the standard Mozilla code review and landing tools and processes. Creating an uplift request can be done either:

* By finding the patch in your local VCS and submitting via ''moz-phab uplift''.
* By finding the patch on Phabricator and submitting via Lando.

After submitting the patch stack via either method, you must complete the Uplift Request form on the tip of the patch stack. This will request review from Release Management.

=== Requesting Uplift using ''moz-phab'' ===

# '''Find the patch or series of patches in your local VCS.''' You can ''moz-phab patch'' onto your local machine if need be.
# '''Determine which uplift train you want to request an uplift for.''' You can see which trains are available with ''moz-phab uplift --list-trains''.
# '''Run ''moz-phab uplift <revset of patches> --train <train>''.''' Most of the arguments to ''moz-phab uplift'' are the same as ''moz-phab submit''. This will create new revisions in Phabricator that will be uplifted to the specified train. If ''moz-phab uplift'' is run from mozilla-unified, the stack of patches will be rebased onto the target that will be landed to. For example if you specify ''--train beta'', the patches will be rebased onto the ''beta'' head in your local VCS. If ''moz-phab uplift'' is run from central or another non-unified repo, the commits will be submitted without attempting to rebase them. Note you must use ''moz-phab uplift'', not ''moz-phab sumbit'' or any other unsupported tool to submit uplift requests.
# '''Open the URL as suggested at the bottom of the output.'''
# '''Complete the uplift request form. See the section below on how to submit the form.'''

=== Requesting Uplift using Lando ===

# '''Go to the Lando page for the stack of revisions to uplift.''' Note: the maximum stack size for use in the web UI is 5 patches. Please use moz-phab to submit larger patch stacks. You can get here from the Phabricator revision by using the “View stack in Lando” option on the right side menu.
# '''Log in to Lando.''' Click the Log In button in the top right.
# '''Add your Phabricator API token and save changes.''' Click your username in the top right corner and paste the Phabricator API token there. Tokens are in the form ''api-XXXXX…''. This token can be found here (replace <USERNAME> with your phab username): https://phabricator.services.mozilla.com/settings/user/<USERNAME>/page/apitokens/ [[File:Lando-phab-api-token.png|thumb|Click your username in the top right corner and paste the Phabricator API token there.]]
# '''Click the “Preview Landing” button. There should be a new button on the bottom right of the modal that is shown.''' Select the target repo (beta) from the list and click “request uplift”. This will create a new Phabricator diff against the requested target. [[File:Request-uplift-button-lando.png|thumb|Click the "Request uplift" button in the bottom right.]]
# '''Complete the uplift request form in the newly created diff. See the section below on how to submit the form.'''

== Submit the Uplift Request Form ==

Once your revision is created in Phabricator, you must complete the uplift request form. This form is a short questionnaire that helps Release Managers understand the reasoning behind the uplift request and the risk associated with this patch landing directly on a release repository without riding the release trains.

# '''Go to a revision in the uplift request stack.'''
# '''Navigate to the bottom of the page where you would “approve” or “request changes” for a patch and select “Change uplift request form”.''' [[File:Phab-Uplift-request-form-action.png|thumb|Select "Change uplift request form".]]
# '''Complete the form and press “request uplift”.''' [[File:Phab-Uplift-request-button.png|thumb|Complete the form and click "Request uplift".]]
# '''Wait for Release Manager approval.''' A bot will automatically set Release Managers as reviewers for the patch after submitting the form. If the patch stack does not apply cleanly to the uplift train due to a merge conflict, you may need to resolve merge conflicts and re-submit the stack. The uplift request will sit in a pending state until a Release Manager approves, the Release Manager will land after approval.

Modules/Desktop Firefox

2022-03-16T16:04:56Z

Flod: Added peers to Localization module

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
Owners and peers of the Desktop Firefox module may review code anywhere in the browser and toolkit directories. Reviews should be sent to the more specific submodules below where possible.

{{Module
|name=Desktop Firefox
|description=Standalone Web Browser.
|owner=[mailto:dtownsend@mozilla.com Dave Townsend], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|fallbackpeers=[mailto:dao@mozilla.com Dão Gottwald], [mailto:jwein@mozilla.com Jared Wein], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|ownersemeritus=
|peersemeritus=[mailto:netzen@gmail.com Brian Bondy], [mailto:lina@mozilla.com Lina Cambridge], [mailto:lchang@mozilla.com Luke Chang], [mailto:rchien@mozilla.com Ricky Chien], [mailto:dolske@mozilla.com Justin Dolske], [mailto:georg.fritzsche@googlemail.com Georg Fritzsche], [mailto:felipc@gmail.com Felipe Gomes], [mailto:tchien@mozilla.com Tim Guan-tin Chien], [mailto:jhofmann@mozilla.com Johann Hofmann], [mailto:rexboy@mozilla.com KM Lee Rex], [mailto:gasolin@mozilla.com Fred Lin], [mailto:ralin@mozilla.com Ray Lin], [mailto:fliu@mozilla.com Fischer Liu], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:mark@moxienet.com Mark Mentovai], [mailto:ted.mielczarek@gmail.com Ted Mielczarek], [mailto:bnicholson@mozilla.com Brian Nicholson], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:mano@mozilla.com Asaf Romano], [mailto:msamuel@mozilla.com Marina Samuel], [mailto:jryans@gmail.com J Ryan Stinnett], [mailto:gps@mozilla.com Gregory Szorc], [mailto:ttaubert@mozilla.com Tim Taubert],
|group=firefox-dev
|source_dirs=browser/, toolkit/
|url=[[Firefox/Code_Review|Code Review Guidelines]]
|components=Firefox, Toolkit
}}

== Submodules ==

{{Module
|name=Add-ons Manager
|description=Extension management back-end.
|owner=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:lgreco@mozilla.com Luca Greco]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong], [mailto:aswan@mozilla.com Andrew Swan], [mailto:kmaglione@mozilla.com Kris Maglione]
|peers=[mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:rwu@mozilla.com Rob Wu], [mailto:wdurand@mozilla.com William Durand]
|source_dirs=toolkit/mozapps/extensions/
|url=
|components=
}}

{{Module
|name=Add-ons Manager UI
|description=about:addons.
|owner=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:mstriemer@mozilla.com Mark Striemer]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong], [mailto:aswan@mozilla.com Andrew Swan]
|peers=[mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/content/
|url=
|components=
}}

{{Module
|name=Application Update
|description=The application update services.
|owner=[mailto:ksteuber@mozilla.com Kirk Steuber]
|peers=[mailto:mhowell@mozilla.com Molly Howell], [mailto:agashlin@mozilla.com Adam Gashlin]
|source_dirs=toolkit/mozapps/update/
|url=
|components=
}}

{{Module
|name=Bookmarks & History
|description=The bookmarks and history services (Places).
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:standard8@mozilla.com Mark Banner], [mailto:adw@mozilla.com Drew Willcoxon]
|source_dirs=browser/components/places/, toolkit/components/places/
|url=
|components=
}}

{{Module
|name=Desktop Theme
|description=The style rules used in the desktop UI.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=[mailto:htwyford@mozilla.com Harry Twyford], [mailto:itiel_yn8@walla.com Itiel]
|peersemeritus=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/themes/, toolkit/themes/
|url=
|components=Firefox::Theme, Toolkit::Themes
}}

{{Module
|name=Desktop UI
|description=The main browser UI except where covered by more specific submodules.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mconley@mozilla.com Mike Conley], [mailto:florian@queze.net Florian Quèze]
|source_dirs=browser/base/content/
|url=
|components=
}}

{{Module
|name=Download Manager
|description=The downloads UI and service.
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:mtigley@mozilla.com Micah Tigley]
|source_dirs=browser/components/downloads/, toolkit/mozapps/downloads/
|url=
|components=
}}

{{Module
|name=Enterprise Policies
|description=System policies for controlling Firefox.
|owner=[mailto:mkaply@mozilla.com Michael Kaply]
|peers=
|source_dirs=browser/components/enterprisepolicies/
|url=
|components=
}}

{{Module
|name=Form Autofill
|description=Form detection and autocomplete.
|owner=[mailto:tgiles@mozilla.com Tim Giles]
|ownersemeritus=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|peers=[mailto:sgalich@mozilla.com Sergey Galich], [mailto:dlee@mozilla.com Dimi Lee]
|source_dirs=browser/extensions/formautofill/, toolkit/components/satchel/
|url=
|components=
}}

{{Module
|name=In-product Messaging
|description=The system for delivering in-product messaging.
|owner=[mailto:aoprea@mozilla.com Andrei Oprea]
|peers=[mailto:najiang@mozilla.com Nan Jiang], [mailto:pdahiya@mozilla.com Punam Dahiya], [mailto:edilee@mozilla.com Ed Lee], [mailto:khudson@mozilla.com Kate Hudson],
|source_dirs=toolkit/components/messaging-system/
|url=
|components=Firefox::Messaging System
}}

{{Module
|name=Launcher Process
|description=Windows process for bootstrapping the browser process.
|owner=[mailto:tkikuchi@mozilla.com Toshihito Kikuchi]
|ownersemeritus=Aaron Klotz
|peers=[mailto:mhowell@mozilla.com Molly Howell]
|source_dirs=browser/app/winlauncher
|url=
|components=Firefox::Launcher Process
}}

{{Module
|name=Localization
|description=Tooling to enable translation and facilitate localization.
|owner=[mailto:francesco.lodolo@gmail.com Francesco Lodolo]
|ownersemeritus=
|peers=[mailto:m@owca.info Matjaž Horvat], [mailto:earo@mozilla.com Eemeli Aro]
|source_dirs=
|url=
|components=Mozilla Localizations, Localization Infrastructure and Tools
}}

{{Module
|name=New Tab Page
|description=The new tab/home page.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:khudson@mozilla.com Kate Hudson], [mailto:aoprea@mozilla.com Andrei Oprea], [mailto:sdowne@getpocket.com Scott Downe]
|source_dirs=browser/components/newtab/
|url=
|components=Firefox::New Tab Page
}}

{{Module
|name=Normandy
|description=The experiments and off-train deployments system.
|owner=[mailto:mcooper@mozilla.com Michael Cooper]
|peers=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=toolkit/components/normandy/
|url=
|components=Firefox::Normandy
}}

{{Module
|name=Onboarding
|description=The onboarding experience including UI tours.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|source_dirs=browser/components/uitour/
|url=
|components=Firefox::Tours
}}

{{Module
|name=Password Manager
|description=Managing, saving and filling logins.
|owner=[mailto:sgalich@mozilla.com Sergey Galich]
|ownersemeritus=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|peers=[mailto:sfoster@mozilla.com Sam Foster], [mailto:jwein@mozilla.com Jared Wein], [mailto:tgiles@mozilla.com Tim Giles], [mailto:dlee@mozilla.com Dimi Lee]
|peersemeritus=[mailto:bdanforth@mozilla.com Bianca Danforth], [mailto:srudie@mozilla.com Severin Rudie]
|source_dirs=toolkit/components/passwordmgr/, browser/components/aboutlogins
|url=https://wiki.mozilla.org/Toolkit:Password_Manager
|components=Toolkit::Password Manager, Toolkit::Password Manager: Site Compatibility, Firefox::about:logins
}}

{{Module
|name= Picture-in-Picture
|description= A component that allows video elements to be pulled out into an always-on-top window.
|owner=[mailto:mconley@mozilla.com Mike Conley], [mailto:mtigley@mozilla.com Micah Tigley], [mailto:mhowell@mozilla.com Molly Howell]
|peers=[mailto:kpatenio@mozilla.com Katherine Patenio], [mailto:nbaumgardner@mozilla.com Niklas Baumgardner]
|source_dirs=toolkit/components/pictureinpicture, browser/extensions/pictureinpicture
|url=https://firefox-source-docs.mozilla.org/toolkit/components/pictureinpicture/pictureinpicture/index.html
}}

{{Module
|name=Preferences
|description=The front-end preferences system.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mstriemer@mozilla.com Mark Striemer], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peersemeritus=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/components/preferences/, browser/themes/*/preferences, toolkit/mozapps/preferences
|url=
|components=
}}

{{Module
|name=Profile Migration
|description=Migrating data from other browsers.
|owner=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peers=[mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|source_dirs=browser/components/migration/
|url=
|components=
}}

{{Module
|name=Screenshots
|description=Code relating to Screenshots functionality
|owner=[mailto:sfoster@mozilla.com Sam Foster]
|peers=[mailto:jhirsch@mozilla.com Jared Hirsch], [mailto:nbaumgardner@mozilla.com Niklas Baumgardner],
|peersemeritus=[mailto:bchen@mozilla.com Barry Chen]
|ownersemeritus=[mailto:emmamalysz@gmail.com Emma Malysz], [mailto:ian@ianbicking.org Ian Bicking]
|source_dirs=browser/extensions/screenshots, browser/components/screenshots/
|components=Firefox::Screenshots
}}

{{Module
|name=Search and Address Bar
|description=The search service, address bar and address bar autocomplete.
|owner=[mailto:standard8@mozilla.com Mark Banner], [mailto:dwillcoxon@mozilla.com Drew Willcoxon]
|peers=[mailto:dharvey@mozilla.com Dale Harvey], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:dao@mozilla.com Dão Gottwald], [mailto:htwyford@mozilla.com Harry Twyford]
|peersemeritus=[mailto:info@mikedeboer.nl Michael de Boer]
|source_dirs=browser/components/search/, browser/components/urlbar/, toolkit/components/search/
|url=
|components=Firefox::Address Bar, Firefox::Search
}}

{{Module
|name=Security and Privacy UI
|description=The front-end to our security and privacy features, including Protections UI, Site Identity, Site Permissions and Certificate Errors
|owner=[mailto:pbz@mozilla.com Paul Zühlcke]
|peers=[mailto:prathiksha@mozilla.com Prathiksha]
|peersemeritus=[mailto:ewright@mozilla.com Erica Wright], Nihanth Subramanya
|ownersemeritus=[mailto:jhofmann@mozilla.com Johann Hofmann]
|source_dirs=browser/components/protections/, browser/components/controlcenter/
|url=
|components=Firefox::Security, Firefox::Protections UI, Firefox::Site Identity, Firefox::Site Permissions
}}

{{Module
|name=Session Restore
|description=Restoring a user's session after starting Firefox.
|owner=[mailto:dao@mozilla.com Dão Gottwald], [mailto:dharvey@mozilla.com Dale Harvey]
|peers=[mailto:afarre@mozilla.com Andreas Farre]
|ownersemeritus=[mailto:info@mikedeboer.nl Michael de Boer], Kashav Madan, Anny Gakhokidze
|source_dirs=browser/components/sessionstore/, toolkit/components/sessionstore/
|url=
|components=Firefox::Session Restore
}}

{{Module
|name=Tabbed Browser
|description=The UI component controlling browser tabs.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=
|source_dirs=browser/base/content/tabbrowser*, browser/modules/AsyncTabSwitcher.jsm
|url=
|components=Firefox::Tabbed Browser
}}

{{Module
|name=Windows Installer
|description=The installer for Windows.
|owner=[mailto:mhowell@mozilla.com Molly Howell]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin], [mailto:nalexander@mozilla.com Nick Alexander]
|source_dirs=browser/installer/, toolkit/mozapps/installer/
|url=
|components=Firefox::Installer
}}

L10n:Mozilla Team

2020-08-26T07:15:26Z

Flod: Remove Axel and Adrian from team

__NOTOC__
{{L10navbar}}

So you would like to learn more about the Mozilla L10n team? You've come to the right place! Click on the links below to learn about each team member, the weekly meetings, and the projects they're working on. 

 

== Team bios ==
=== Mozilla Corporation ===
;[http://informationisart.com/stas/ Staś Małolepszy] : Fluent release driver, including feature design, specification, and software engineering for Fluent.
;[http://jeffbeatty.org Jeff Beatty] : Head of localization. Talk to me about l10n technical and community strategy, cross-cultural design, and management.
;[http://horv.at/blog Matjaž Horvat] : [https://pontoon.mozilla.org/ Pontoon] owner.
;[http://blog.lebedel.net/ Delphine Lebédel] : L10n-driver for mobile products (Android and iOS). Community builder & enabler.
;[http://pbase.com/faerie_39/ Peiying Mo] : L10n driver for web projects: Mozilla.org, marketing, legal localization; vendor management; community builder.
;[https://flod.org/ Francesco Lodolo (:flod)] : L10n driver for Firefox desktop localization and Test Pilot. Owner for webdashboards and AppStores webapp, peer and technical support for mozilla.org and mobile, product l10n early review in mozilla-central.

=== Mozilla Foundation ===
;[https://mozillians.org/u/tchevalier/ Théo Chevalier] : L10n driver for Mozilla Foundation projects, Advocacy & fundraising in particular.

 

== Current projects ==

*[[L10n:Pontoon|Pontoon]]
*[https://wiki.mozilla.org/Fluent Fluent]
*[https://wiki.mozilla.org/Elmo Elmo]

== Contact ==

Send mail to [mailto:L10n-drivers@mozilla.org L10n driver's team] or subscribe to the [http://groups.google.com/group/mozilla.dev.l10n/topics Mozilla l10n forum]. 
[[Category:L10n]]

L10n:Bugogram

2020-04-28T07:13:19Z

Flod: /* shipping */

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

== shipping ==
; short_desc : [%(loc)s] Firefox release tracker %(language)s
; alias : fx-l10n-%(loc)s
; blocked : fx-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,pmo@mozilla.com
This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibility to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds Mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are [the dev-l10n-new-locales mailing list](http://www.mozilla.org/about/forums/#dev-l10n-new-locales) or [#l10n-community on Matrix](https://chat.mozilla.org/#/room/#l10n-community:mozilla.org). Ask in public, you shouldn't assume that you're the only one with the question.

== bugzilla ==
; short_desc : Create l10n Bugzilla component for %(language)s (%(loc)s), add value for Locale field
; product : bugzilla.mozilla.org
; component : Administration
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com
We need a Bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custom field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations
Component: %(loc)s / %(language)s
Description: %(language)s Localization (...)

Assignee: nobody
QA Contact: Empty
Triage owner: :flod (francesco.lodolo@gmail.com)

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description?

Once we have the description, this bug will be fixed by Mozilla staff.

== ldap ==
; short_desc : Create LDAP account for %(name)s <%(bugmail)s>
; product : Infrastructure & Operations
; component : Infrastructure: LDAP
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com

Please create an LDAP account for %(name)s. We'll want a password, and be part tableau_users group.

This bug is independent of repository access requests.

== hg_repo ==
; short_desc : l10n-central Mercurial repository for '%(loc)s'
; product : Developer Services
; component : Mercurial: hg.mozilla.org
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
Please create a new hg repository for Firefox localization. The repository should be:

- l10n-central/%(loc)s/

with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== build ==
; short_desc : Add '%(loc)s' to Firefox Nightly build
; product : Firefox Build System
; component : General
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
We need to add '%(loc)s' to browser/locales/all-locales on mozilla-central.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== Webservices ==
We'll have a separate bug for each web service area, namely
* search
* protocol handlers
* rss readers

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives:
Google, Bing, Amazon, DuckDuckGo, Twitter, Wikipedia, eBay

Adding brand new search engines, that not yet ship in any other language, needs approval from Business Development and requires more time to get authorization and assets from the provider. To avoid blocking the initial set up, this type of requests should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

The %(language)s team and flod will be driving this bug to completion.

=== protocol ===
; short_desc : [%(loc)s] Firefox protocol handler setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

== websetup ==
; short_desc : [%(loc)s] bootstrap %(language)s on GitHub
; product : Mozilla Localizations
; component : Infrastructure
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com
; blocked : fx-l10n-%(loc)s

Peiying, please add web pages to this locale's folder on mozilla.org.

Please notify in the actual translation bug when this is done.

== webparts ==
; short_desc : [%(loc)s] Firefox initial web parts for %(language)s
; product : www.mozilla.org
; component : L10N
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages.

Peying will follow up here when the initial setup work is done. After that, files will be added to GitHub, and will be available for localization in Pontoon at https://pontoon.mozilla.org/%(loc)s/mozillaorg/

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

== sumo ==
; short_desc : [%(loc)s] Enable %(language)s localization on SUMO
; product : support.mozilla.org
; component : Localization
; cc : %(bugmail)s
; blocked : fx-l10n-%(loc)s
We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

== done ==
That's all folks.

L10n:Bugogram

2019-11-05T10:52:46Z

Flod:

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

== shipping ==
; short_desc : [%(loc)s] Firefox release tracker %(language)s
; alias : fx-l10n-%(loc)s
; blocked : fx-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,pmo@mozilla.com
This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibility to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds Mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

== bugzilla ==
; short_desc : Create l10n Bugzilla component for %(language)s (%(loc)s), add value for Locale field
; product : bugzilla.mozilla.org
; component : Administration
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com
We need a Bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custom field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations
Component: %(loc)s / %(language)s
Description: %(language)s Localization (...)

Assignee: nobody
QA Contact: Empty
Triage owner: :flod (francesco.lodolo@gmail.com)

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description?

Once we have the description, this bug will be fixed by Mozilla staff.

== ldap ==
; short_desc : Create LDAP account for %(name)s <%(bugmail)s>
; product : Infrastructure & Operations
; component : Infrastructure: LDAP
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com

Please create an LDAP account for %(name)s. We'll want a password, and be part tableau_users group.

This bug is independent of repository access requests.

== hg_repo ==
; short_desc : l10n-central Mercurial repository for '%(loc)s'
; product : Developer Services
; component : Mercurial: hg.mozilla.org
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
Please create a new hg repository for Firefox localization. The repository should be:

- l10n-central/%(loc)s/

with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== build ==
; short_desc : Add '%(loc)s' to Firefox Nightly build
; product : Firefox Build System
; component : General
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
We need to add '%(loc)s' to browser/locales/all-locales on mozilla-central.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== Webservices ==
We'll have a separate bug for each web service area, namely
* search
* protocol handlers
* rss readers

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives:
Google, Bing, Amazon, DuckDuckGo, Twitter, Wikipedia, eBay

Adding brand new search engines, that not yet ship in any other language, needs approval from Business Development and requires more time to get authorization and assets from the provider. To avoid blocking the initial set up, this type of requests should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

The %(language)s team and flod will be driving this bug to completion.

=== protocol ===
; short_desc : [%(loc)s] Firefox protocol handler setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

== websetup ==
; short_desc : [%(loc)s] bootstrap %(language)s on GitHub
; product : Mozilla Localizations
; component : Infrastructure
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com
; blocked : fx-l10n-%(loc)s

Peiying, please add web pages to this locale's folder on mozilla.org.

Please notify in the actual translation bug when this is done.

== webparts ==
; short_desc : [%(loc)s] Firefox initial web parts for %(language)s
; product : www.mozilla.org
; component : L10N
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages.

Peying will follow up here when the initial setup work is done. After that, files will be added to GitHub, and will be available for localization in Pontoon at https://pontoon.mozilla.org/%(loc)s/mozillaorg/

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

== sumo ==
; short_desc : [%(loc)s] Enable %(language)s localization on SUMO
; product : support.mozilla.org
; component : Localization
; cc : %(bugmail)s
; blocked : fx-l10n-%(loc)s
We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

== done ==
That's all folks.

MozWeek/Berlin2020

2019-09-27T17:56:54Z

Flod: /* Ground Transportation */

'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor please inquire with your community manager/program manager about [[All_Hands/Contributor_nominations|contributor nominations]], interns please inquire to your coordinator. '''''

=='''Dates and Location'''==
Monday, January 27, 2020 - Friday, January 31, 2020 (travel days are Monday, Jan 27 & Saturday, Feb 1) in Berlin, Germany.

We have guestrooms at three hotels: [https://www.ihg.com/intercontinental/hotels/us/en/berlin/berha/hoteldetail InterContinental Berlin], [https://www.pullman-berlin-schweizerhof.com/en/ Hotel Pullman Schweizerhof], and [https://www.hotel-berlin.de/en/ Hotel Berlin, Berlin]. [https://drive.google.com/open?id=1eu_rYMxuc_hgSNqCJxW7Vn32pYMNayPa&usp=sharing View on map].

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to pre-approved and pre-arranged.''

=='''Registration'''==
This is an invite-only event. All full time and Elance/Upwork employees are expected to attend this all company event. Contractors, Vendors and seasonal employees are included on a case by case evaluation based upon team needs and upon executive review and approval.

Advance registration is required. Attendees will need to wear their event badge at all times, including to evening events. We will have security at our events who will be ensuring everyone in our space should be there. This includes facilitators, and other related business guests.

=====New Hires=====
We have a process to identify qualified regular full time new hires and Brianna will invite all new hires to register and book travel directly on their start date. No action is necessary from hiring managers other than to let them know about the event (please do not forward any links). Please work closely with your recruiting manager as they are aware of all deadlines.

All regular full time new hires must have a start date of January 6, 2020 or earlier and in workday by December 16, 2019. Final invites will be extended on December 17, 2019. Contractors/vendors will require executive approval and those who are hired after the approval will not be invited. If you have any questions, please email bmark@mozilla.com.

=='''Immigration'''==
If you have any questions about immigration, please email immigration@mozilla.com.

==== STEP ====
'''What is STEP?'''
The Smart Traveler Enrollment Program (STEP) is a free service to allow U.S. citizens and nationals traveling abroad to enroll their trip with the nearest U.S. Embassy or Consulate.
Benefits of Enrolling in STEP
* Receive important information from the Embassy about safety conditions in your destination country, helping you make informed decisions about your travel plans.
* Help the U.S. Embassy contact you in an emergency, whether natural disaster, civil unrest, or family emergency.
* Help family and friends get in touch with you in an emergency.

==== Visas ====
You do not need a visa if you hold a passport issued from the EU, USA, Australia, New Zealand, Taiwan, or Canada.
Please see here to confirm the entry document requirements for the country you’re from: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node/staatenlistevisumpflicht-node

If you are from a country that requires a visa to enter Germany, please plan to obtain one as early as possible as government processing times constantly change. You can find a broad overview of the process here: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node . For more detailed instructions regarding the visa process you will need to refer to the website of your nearest Mission/Consulate General. You will be able to learn more about the process by searching for “business visa” or “visitor visa” on the website for that German Mission.

'''Please keep in mind that while you are traveling for work, you are not traveling for a German based job.''' All Hands is a business conference/event. As you book your travel please also keep in mind that you could require a transit visa if you have a layover in a country that requires it.

If you have questions specific to your circumstances, please email immigration@mozilla.com.

==== Entering Germany ====
Your passport or identity card will be checked when you arrive at an EU port or airport to make sure you’re allowed to come into the country. The passport must be valid for the whole of your stay. You may also need a visa to come into or travel through Germany, depending on your nationality.
* If you are from an EEA country or Switzerland, you can enter Germany with either a valid passport or a national identity card issued by a EEA country.
* If you need a United States Passport, start here: https://travel.state.gov/content/passports/en/passports.html. Please note it can take 4-6 weeks to receive your passport. Please plan ahead.

==== EU Visa Waiver Program Suspension - Update ====
In March 2019 the EU announced that the visa free entry requirements for third country visitors to Europe would be changing. This change will not go into affect until 1 January 2021, note this is one year after our Berlin All Hands trip. After this date, citizens from certain countries, including the USA and Canada, will be required to obtain an ETIAS travel authorization before they can enter Europe.

==== More details: ====
Mission websites in popular Mozillian locations:
* United States: https://www.germany.info/us-en/service/05-VisaEinreise/business-visa/963542
* Canada: https://canada.diplo.de/ca-en/consular-services/visa/shortstay
* UK: https://uk.diplo.de/uk-en/02/visa
* Paris: https://allemagneenfrance.diplo.de/fr-de/service/00-visa-seite
* Taiwan: https://taipei.diplo.de/tw-en/service/visa
* Beijing: https://china.diplo.de/cn-zh/service/visa-einreise/schengenvisum/1343246
* India: https://india.diplo.de/in-en/service/-/1908794

=='''Travel to Berlin'''==
Bookings to Berlin have begun. The Egencia instructions have be emailed to '''anyone approved to attend'''. New hires will have individual deadlines based upon hire/start date. Approved contractors, vendors, seasonal, status employees will be notified with an email from bmark@mozilla.com with specific instructions.

Specific instructions were emailed to you about how to book, as we have a new process for anyone based outside the US, Canada & Central/South America. APAC employees will '''NOT''' be booking your All Hands travel in country based site, and will be using Egencia Americas. European employees '''WILL''' be booking in your country based site to allow access to trains and low cost airlines.

Should you need to reach someone at '''Egencia Americas''' for special circumstances or changes that can't be done online:
*Call+1 (800) 361-1120 or +1(702)939-2533; Hours of operations are Monday – Friday (except holidays) 5:00 AM– 6:00 PM PT or 8:00 AM – 9:00 PM ET or 12:00 PM - 1:00 AM UTC. If you call outside these hours, you will get an after-hours agent (not a meeting agent, who may not be as helpful) . Please ensure the agent you speak with knows you are booking for a meeting.
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday.

Other Egencia contact details:
*Egencia UK+EMEA - Email: customer_service@egencia.co.uk; UK Local #: +44 203 077 2536 (charged at local rate). For calls made outside the UK, please dial +00 44 161 233 5525. (From anywhere outside the EU, please dial +011 44...)
*Egencia FR - Email: service_client@egencia.fr; France Local #: +33 8 11 65 66 53. For calls made outside France, please dial +33 4 86 06 15 18 (From anywhere outside the EU, please dial +011 33)

'''Important Details:'''
Everyone should plan to arrive in Berlin Tegel Airport (TXL) on Monday, January 27 and leave on Saturday, February 1. Anyone who plans to arrive ahead of that or to stay longer, regardless of the reason, must follow the "arriving early/departing late guidelines." These guidelines also apply if you want to fly in or out of airports other than your home airport and Berlin Tegel (anything custom). A few notes:
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, those approved will be sent separate email.
*Volunteers will be handled separate from this process.
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.
*If you would like to invite someone who is a business partner, facilitator or some other category that isn't an employee or volunteer (not a personal guest/family), email bmark@mozilla.com.
*Change fees will be covered by Mozilla for business reasons only. Please email bmark@mozilla.com ahead of calling Egencia to make the change. Any changes for personal reasons must be paid by the employee directly to Egencia over the phone.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, January 27 and leave on Saturday, February 1. Here are some exceptions:

# If you plan to spend some extra '''personal time in Berlin/Europe''' or nearby (choosing to arrive before Monday, Jan 27 or depart after Saturday, Feb 1), you'll need to create a itinerary in Egencia for standard dates/locations within the Egencia Portal and compare to the custom dates/locations you'd like. Pricing for the standard dates should be ''Round Trip only''. Pricing for custom dates/locations should be for ''Round trip or Multi city trips only''. Please share the difference via email to bmark@mozilla.com and receive approval ahead of submission in Egencia. You can ''sway up to +$100 over'' and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of TXL w/ longer dates, and you personally book & cover the rest). Please note that one way trips are only approved on a case by case basis. Do not book one ways without prior approval. ''We '''do not''' have the ability for employees to reimburse Mozilla for any overage.'' This scenario also applies for routing through different airports to/from Berlin Tegel than your home airport (ex. a layover in London for a few days, or flying out of something other than TXL).

# If you are attending the '''Sunday/Monday CI event''' (by invite), you can arrive on Sunday, January 26.
# If you would like to arrive early to '''recover from jetlag''', you will need manager approval for any additional costs associated with the extension. There is '''no unilateral''' "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). This policy does not apply to volunteer contributors, any jetlag recovery costs must be self funded.
# If you are celebrating the '''Lunar New Year''', [https://wiki.mozilla.org/All_Hands/Berlin2020#Lunar_New_Year see here].
# If you live in a country where '''work travel is prohibited on weekends''', you may travel on Friday, Jan 24 and Monday, Feb 3, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively.
# If you live in a country where '''work travel is prohibited on Sunday''', you may travel on Saturday, Jam 24, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively.

====Booking Family Travel====
Whether your family will accompany you on your flight or join us later; and you have two options: direct with the airline (recommended) or through Egencia.

'''Direct (recommended):'''

First, figure out which flights you want to be on as an employee in Egencia. Hold them in Egencia. Find the flights you want for your family on the airline site and book them. Go back to Egencia and book your flights. Once you have both sets of confirmation numbers, call the airline and ask them to LINK your two reservations. This shows that you are traveling together and shouldn't be moved. When you call, you can also ask the airline agent to assign seats together. By booking your family direct on the airline, it gives them "priority" with the airline over people who book via a third party (expedia, booking.com, kayak, etc). These aren't guarantees, but they do help.

'''Via Egencia:'''

We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com

'''Notes:'''

* If your family is arriving on a different flights than you but would like to take advantage of the airport shuttles on Sunday/Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.
* We are unable to accommodate volunteer contributor families/guests.

====Not Flying====
Mozilla will reimburse U-Bahn tickets for those based in the Berlin area for getting to/from hotels. For more information on the U-Bahn, please see the Berlin office guide on [https://mana.mozilla.org/wiki/display/WPR/Berlin+Office+Guide#BerlinOfficeGuide-MovingAroundBerlin mana].

For those outside of the Berlin area who are taking the train, please add your name [https://docs.google.com/spreadsheets/d/1A8AKfpdaeD_gVoC6eZfxZoQ4zacgP8l_r9vM04RKyPI/edit#gid=0 here]. We will notify you when train bookings open (on or about Nov 1). You will book train via Egencia FR, UK, DE.

Parking is not reimbursable.

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members (unless required for visa application).

====Air Travel Fine Print====
*Change fees will be covered by Mozilla for '''business reasons only'''. If you need a change and have manager approval, email bmark@mozilla.com '''prior to requesting the change with Egencia'''. Once you have approval, call Egencia to make the change at 1-877-255-1090 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.
*Mozilla will '''not''' reimburse for Business/First class upgrades, tickets or seat reservations.
*Mozilla will reimburse for one checked bag each way.
*''Mozilla Frequent Flyer perks do not apply for All Hands''.
*Flights booked outside of Egencia will not be an approved expense unless email approval by Brianna is obtained prior to booking.
*Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

====Ground Transportation====
Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00.

Taxis and Addison Lee are not reimbursable.

If you are arriving by train to Hauptbahnhof:
To Hotel Berlin Berlin
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S5, S9 or S75 to the station “Zoologischer Garten” (20 min.). From there, take the bus 100 to the stop Lützowplatz.
* Via U-BAHN: Take the U-Bahn metro lines U2, U3 and U1 to the station “U-Nollendorfplatz”. Exit the station in the direction of “Karl-Heinrich-Ulrichs-Straße." The road leads directly to the hotel (approx 5 mins).
* [https://www.hotel-berlin.de/d/berlinberlinpro/media/PDF/Anfahrt_A4_E_Karl-Heinrich-Ulrichs-Strae_5c2ab7.pdf Map]

To InterCon Berlin and Pullman
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S3, S5, S7, or S9 to the station “Zoologischer Garten”. From there, walk 10 mins to hotel.

Berlin's integrated public transport is divided in 3 tariff zones (ABC). To travel within the city, including from Tegel airport to the hotels, you only need an AB ticket. Tickets can be bought at automated booths in most stations (accept credit cards), and on Metro (need coins). You can use the same ticket to travel on buses, metro, S-Bahn, U-Bahn. More information, including PDF maps, are available on [https://www.berlin.de/en/public-transportation/1772016-2913840-tickets-fares-and-route-maps.en.html this website]. A mobile app is available on stores ("BVG FahrInfo Plus") and allows to create routes between stations, or you can use directly the [https://www.bvg.de/en BVG] website.

=='''Families/Guests'''==
Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made. Please note that what are able to do for families varies by each location. We are unable to accommodate volunteer contributor or intern families/guests at our All Hands.

====Quick summary logistics====
* Air Travel: Employees do need to book via Egencia regardless of how families are booked.
* Hotel: Family/friends are welcome to stay with you. All room rates are based upon single occupancy and include breakfast. Guests must be added to reservations in advance and any additional room expenses will be yours to cover. Most of our hotel rooms have a maximum of double occupancy (2 adults), with very limited availability of rooms for higher occupancy. Higher occupancy rooms will be assigned in the order that you register. We will have extra rooms available for families to book and pay for at our hotels.
* Lunch & Dinner: Family will be on their own for lunch daily and dinner on Tuesday, Wednesday & Thursday.
* Monday & Friday Night Events: Family members who are registered for the event and registered with the hotel, are invited to join us for our evening events.
* Childcare Services: We will not provide centralized childcare services. We have found that every family has different needs and centralized childcare does not deliver on those needs. If you are in need of help finding options for your family, we are happy to connect you with staff whose families who are coming (#allhands-childcare and #parents are great places to start), as well we are happy to help support finding of resources (although you are likely better at it than us). Given every circumstance is unique, we defer to your manager to determine what Mozilla can support you with financially.

On demand babysitting services in Berlin:
* https://extra-arms.com/for-families-babysitting/
* https://www.withourbaby.com/

=='''Lunar New Year'''==
We are aware of the overlap in the Lunar New Year celebrations with the Berlin All Hands. To help folks who decide to attend the Berlin All Hands and who also celebrate Chinese New Year, we will offer the following:
* A higher airfare caps for air travel to allow for fewer layovers on Monday, January 27
* Assurance that Berlin is optional but if employee wants to attend they can shift their holiday days to another time.
* Live Airmo Feeds of Plenary (+ relevant team all hands meetings) + quick posting of recording to accommodate those who choose not to travel.
* Potentially shifting any main plenary session date/time

We are working with leadership and representatives of those most affected and will update wiki regularly with updates. Feel free to reach out to Brianna with questions.

=='''Safety & Security'''==
=====Alcohol at Events=====
To better support and sustain an environment (and workplace culture) where people feel safe and included, we have made a set of changes regarding alcohol at our events. In all cases, our approach aligns with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).
*All participants are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.
*We will '''limit bar-servings to beer and wine''' and ensure an equal number and quality (i.e. not just Coke) of non-alcoholic drink options are available and displayed.
*Team dinners should be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.
*Clearly outlined, communicated (to event teams, HR and managers) and understood '''escalation process''' for behavior that might be deemed counter to the spirit of our CPG.

=====Device Security=====
If you are traveling to the All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Physical Security=====
Badges are required to access all meeting spaces and evening events.

=='''Accessibility'''==
====Evenings====
Monday Night reception is at the InterContinental Berlin. No stairs or elevators required.

====Meeting spaces====
* InterCon: Most meeting space levels are accessible by elevators.
* Pullman: All meeting space levels are accessible by guestroom elevators.
* Hotel Berlin: All meeting space is on the ground level.

====Listen Systems====
We will have Listen Systems available for any meeting in the main plenary space. Visit the AV booth to pick one up.

====Bathrooms====
TBA

====Breastfeeding/pumping stations====
Milk Stork Services are reimbursable - please contact benefits@mozilla.com for more information.

=='''Sustainability'''==
'''Hotel Berlin, Berlin''' is certified partner of visitBerlin we stand for sustainable, green meetings and events. For more information, visit https://convention.visitberlin.de/en/sustain.

'''InterContinental Hotel Berlin''' is Green Globe Certified. Green Globe Certification is the worldwide sustainability system based on internationally accepted criteria for sustainable operation and management of travel and tourism businesses. Operating under a worldwide license, Green Globe Certification is based in California, USA and is represented in over 83 countries. Green Globe Certification is a member of the Global Sustainable Tourism Council, supported by the United Nations World Tourism Organization. Additonally, as part of IHG’s Green Engage™ program the InterContinental Berlin has implemented best practices at all operational levels. The innovative Environmental Management System not only measures the day-to-day energy, water and waste consumption, but also provides recommended actions – ‘green solutions’ – to improve energy conservation and the property’s carbon footprint score.

=='''All Hands Expense Policy'''==
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. Berlin All Hands Expense Report). Each expense must be tagged with "All Hands - Jan 2020"

2. It must contain only those expenses relative to the All Hands Event in Berlin.

3. If your submitted expense report for All Hands is submitted outside these guidelines, it will be rejected and you will be asked to re-submit with only All Hands Expenses

4. The deadline to submit the All Hands Expense Report is '''February 28, 2020'''.

5. Expenses related to team events (except those coordinated through Lisa Carlson), parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved.

'''The intention of our all hands are to centrally organize a structure that includes:'''
*Meals (2 evening events + breakfast, lunch, drinks and snacks Tuesday - Friday)
*Transportation
*Accommodations

Expenses submitted can not exceed the approved amounts. Any social events (except dinners/team building activities coordinated through Lisa Carlson) that are not part of our central plan will generally be self-organized and funded by participants.

=====Travel expenses policy=====
Reimbursement will be made for necessary and reasonable expenses.

* Getting to/from home to your airport: We ask that you use the most economical option, while balancing your personal needs - whether that be mileage/parking, public transportation or ride shares. We will not reimburse for private towncar services or car rental.
* Per standard Mozilla travel policy, Travel Meal Policy: Employees are eligible for travel meals when traveling. For Meals: There is a $75 USD per day meal policy while traveling. This covers breakfast (est. $15), lunch (est. $20), and dinner (est. $40). Receipts: Receipts are required. When submitting a meal for reimbursement, please include how many people attended the meal. There is no need to include names.
* We will not reimburse for seat/class upgrades. Frequent flyer status does not apply for All Hands.
* We will reimburse for bag checking fees for one bag.

Any other expenses must be approved by your manager ahead of time. Any expenses for extending your stay for business reasons - such as additional hotel nights, meals, etc must be approved by your manager before booking and travel.

=====Cell phone reimbursement policy=====
Cell phone reimbursement must be approved by your manager prior to submitting the expense. Teams will decide for their staff what is appropriate to expense.

=====Internet reimbursement policy=====
Internet will be provided in all guestrooms and meeting space in all hotels. If you opt to upgrade/add service, those costs are not reimbursable, unless previously approved by your manager and are for business reasons.

=='''Activities'''==

MozWeek/Berlin2020

2019-09-27T17:54:27Z

Flod: /* Ground Transportation */

'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor please inquire with your community manager/program manager about [[All_Hands/Contributor_nominations|contributor nominations]], interns please inquire to your coordinator. '''''

=='''Dates and Location'''==
Monday, January 27, 2020 - Friday, January 31, 2020 (travel days are Monday, Jan 27 & Saturday, Feb 1) in Berlin, Germany.

We have guestrooms at three hotels: [https://www.ihg.com/intercontinental/hotels/us/en/berlin/berha/hoteldetail InterContinental Berlin], [https://www.pullman-berlin-schweizerhof.com/en/ Hotel Pullman Schweizerhof], and [https://www.hotel-berlin.de/en/ Hotel Berlin, Berlin]. [https://drive.google.com/open?id=1eu_rYMxuc_hgSNqCJxW7Vn32pYMNayPa&usp=sharing View on map].

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to pre-approved and pre-arranged.''

=='''Registration'''==
This is an invite-only event. All full time and Elance/Upwork employees are expected to attend this all company event. Contractors, Vendors and seasonal employees are included on a case by case evaluation based upon team needs and upon executive review and approval.

Advance registration is required. Attendees will need to wear their event badge at all times, including to evening events. We will have security at our events who will be ensuring everyone in our space should be there. This includes facilitators, and other related business guests.

=====New Hires=====
We have a process to identify qualified regular full time new hires and Brianna will invite all new hires to register and book travel directly on their start date. No action is necessary from hiring managers other than to let them know about the event (please do not forward any links). Please work closely with your recruiting manager as they are aware of all deadlines.

All regular full time new hires must have a start date of January 6, 2020 or earlier and in workday by December 16, 2019. Final invites will be extended on December 17, 2019. Contractors/vendors will require executive approval and those who are hired after the approval will not be invited. If you have any questions, please email bmark@mozilla.com.

=='''Immigration'''==
If you have any questions about immigration, please email immigration@mozilla.com.

==== STEP ====
'''What is STEP?'''
The Smart Traveler Enrollment Program (STEP) is a free service to allow U.S. citizens and nationals traveling abroad to enroll their trip with the nearest U.S. Embassy or Consulate.
Benefits of Enrolling in STEP
* Receive important information from the Embassy about safety conditions in your destination country, helping you make informed decisions about your travel plans.
* Help the U.S. Embassy contact you in an emergency, whether natural disaster, civil unrest, or family emergency.
* Help family and friends get in touch with you in an emergency.

==== Visas ====
You do not need a visa if you hold a passport issued from the EU, USA, Australia, New Zealand, Taiwan, or Canada.
Please see here to confirm the entry document requirements for the country you’re from: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node/staatenlistevisumpflicht-node

If you are from a country that requires a visa to enter Germany, please plan to obtain one as early as possible as government processing times constantly change. You can find a broad overview of the process here: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node . For more detailed instructions regarding the visa process you will need to refer to the website of your nearest Mission/Consulate General. You will be able to learn more about the process by searching for “business visa” or “visitor visa” on the website for that German Mission.

'''Please keep in mind that while you are traveling for work, you are not traveling for a German based job.''' All Hands is a business conference/event. As you book your travel please also keep in mind that you could require a transit visa if you have a layover in a country that requires it.

If you have questions specific to your circumstances, please email immigration@mozilla.com.

==== Entering Germany ====
Your passport or identity card will be checked when you arrive at an EU port or airport to make sure you’re allowed to come into the country. The passport must be valid for the whole of your stay. You may also need a visa to come into or travel through Germany, depending on your nationality.
* If you are from an EEA country or Switzerland, you can enter Germany with either a valid passport or a national identity card issued by a EEA country.
* If you need a United States Passport, start here: https://travel.state.gov/content/passports/en/passports.html. Please note it can take 4-6 weeks to receive your passport. Please plan ahead.

==== EU Visa Waiver Program Suspension - Update ====
In March 2019 the EU announced that the visa free entry requirements for third country visitors to Europe would be changing. This change will not go into affect until 1 January 2021, note this is one year after our Berlin All Hands trip. After this date, citizens from certain countries, including the USA and Canada, will be required to obtain an ETIAS travel authorization before they can enter Europe.

==== More details: ====
Mission websites in popular Mozillian locations:
* United States: https://www.germany.info/us-en/service/05-VisaEinreise/business-visa/963542
* Canada: https://canada.diplo.de/ca-en/consular-services/visa/shortstay
* UK: https://uk.diplo.de/uk-en/02/visa
* Paris: https://allemagneenfrance.diplo.de/fr-de/service/00-visa-seite
* Taiwan: https://taipei.diplo.de/tw-en/service/visa
* Beijing: https://china.diplo.de/cn-zh/service/visa-einreise/schengenvisum/1343246
* India: https://india.diplo.de/in-en/service/-/1908794

=='''Travel to Berlin'''==
Bookings to Berlin have begun. The Egencia instructions have be emailed to '''anyone approved to attend'''. New hires will have individual deadlines based upon hire/start date. Approved contractors, vendors, seasonal, status employees will be notified with an email from bmark@mozilla.com with specific instructions.

Specific instructions were emailed to you about how to book, as we have a new process for anyone based outside the US, Canada & Central/South America. APAC employees will '''NOT''' be booking your All Hands travel in country based site, and will be using Egencia Americas. European employees '''WILL''' be booking in your country based site to allow access to trains and low cost airlines.

Should you need to reach someone at '''Egencia Americas''' for special circumstances or changes that can't be done online:
*Call+1 (800) 361-1120 or +1(702)939-2533; Hours of operations are Monday – Friday (except holidays) 5:00 AM– 6:00 PM PT or 8:00 AM – 9:00 PM ET or 12:00 PM - 1:00 AM UTC. If you call outside these hours, you will get an after-hours agent (not a meeting agent, who may not be as helpful) . Please ensure the agent you speak with knows you are booking for a meeting.
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday.

Other Egencia contact details:
*Egencia UK+EMEA - Email: customer_service@egencia.co.uk; UK Local #: +44 203 077 2536 (charged at local rate). For calls made outside the UK, please dial +00 44 161 233 5525. (From anywhere outside the EU, please dial +011 44...)
*Egencia FR - Email: service_client@egencia.fr; France Local #: +33 8 11 65 66 53. For calls made outside France, please dial +33 4 86 06 15 18 (From anywhere outside the EU, please dial +011 33)

'''Important Details:'''
Everyone should plan to arrive in Berlin Tegel Airport (TXL) on Monday, January 27 and leave on Saturday, February 1. Anyone who plans to arrive ahead of that or to stay longer, regardless of the reason, must follow the "arriving early/departing late guidelines." These guidelines also apply if you want to fly in or out of airports other than your home airport and Berlin Tegel (anything custom). A few notes:
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, those approved will be sent separate email.
*Volunteers will be handled separate from this process.
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.
*If you would like to invite someone who is a business partner, facilitator or some other category that isn't an employee or volunteer (not a personal guest/family), email bmark@mozilla.com.
*Change fees will be covered by Mozilla for business reasons only. Please email bmark@mozilla.com ahead of calling Egencia to make the change. Any changes for personal reasons must be paid by the employee directly to Egencia over the phone.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, January 27 and leave on Saturday, February 1. Here are some exceptions:

# If you plan to spend some extra '''personal time in Berlin/Europe''' or nearby (choosing to arrive before Monday, Jan 27 or depart after Saturday, Feb 1), you'll need to create a itinerary in Egencia for standard dates/locations within the Egencia Portal and compare to the custom dates/locations you'd like. Pricing for the standard dates should be ''Round Trip only''. Pricing for custom dates/locations should be for ''Round trip or Multi city trips only''. Please share the difference via email to bmark@mozilla.com and receive approval ahead of submission in Egencia. You can ''sway up to +$100 over'' and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of TXL w/ longer dates, and you personally book & cover the rest). Please note that one way trips are only approved on a case by case basis. Do not book one ways without prior approval. ''We '''do not''' have the ability for employees to reimburse Mozilla for any overage.'' This scenario also applies for routing through different airports to/from Berlin Tegel than your home airport (ex. a layover in London for a few days, or flying out of something other than TXL).

# If you are attending the '''Sunday/Monday CI event''' (by invite), you can arrive on Sunday, January 26.
# If you would like to arrive early to '''recover from jetlag''', you will need manager approval for any additional costs associated with the extension. There is '''no unilateral''' "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). This policy does not apply to volunteer contributors, any jetlag recovery costs must be self funded.
# If you are celebrating the '''Lunar New Year''', [https://wiki.mozilla.org/All_Hands/Berlin2020#Lunar_New_Year see here].
# If you live in a country where '''work travel is prohibited on weekends''', you may travel on Friday, Jan 24 and Monday, Feb 3, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively.
# If you live in a country where '''work travel is prohibited on Sunday''', you may travel on Saturday, Jam 24, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively.

====Booking Family Travel====
Whether your family will accompany you on your flight or join us later; and you have two options: direct with the airline (recommended) or through Egencia.

'''Direct (recommended):'''

First, figure out which flights you want to be on as an employee in Egencia. Hold them in Egencia. Find the flights you want for your family on the airline site and book them. Go back to Egencia and book your flights. Once you have both sets of confirmation numbers, call the airline and ask them to LINK your two reservations. This shows that you are traveling together and shouldn't be moved. When you call, you can also ask the airline agent to assign seats together. By booking your family direct on the airline, it gives them "priority" with the airline over people who book via a third party (expedia, booking.com, kayak, etc). These aren't guarantees, but they do help.

'''Via Egencia:'''

We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com

'''Notes:'''

* If your family is arriving on a different flights than you but would like to take advantage of the airport shuttles on Sunday/Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.
* We are unable to accommodate volunteer contributor families/guests.

====Not Flying====
Mozilla will reimburse U-Bahn tickets for those based in the Berlin area for getting to/from hotels. For more information on the U-Bahn, please see the Berlin office guide on [https://mana.mozilla.org/wiki/display/WPR/Berlin+Office+Guide#BerlinOfficeGuide-MovingAroundBerlin mana].

For those outside of the Berlin area who are taking the train, please add your name [https://docs.google.com/spreadsheets/d/1A8AKfpdaeD_gVoC6eZfxZoQ4zacgP8l_r9vM04RKyPI/edit#gid=0 here]. We will notify you when train bookings open (on or about Nov 1). You will book train via Egencia FR, UK, DE.

Parking is not reimbursable.

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members (unless required for visa application).

====Air Travel Fine Print====
*Change fees will be covered by Mozilla for '''business reasons only'''. If you need a change and have manager approval, email bmark@mozilla.com '''prior to requesting the change with Egencia'''. Once you have approval, call Egencia to make the change at 1-877-255-1090 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.
*Mozilla will '''not''' reimburse for Business/First class upgrades, tickets or seat reservations.
*Mozilla will reimburse for one checked bag each way.
*''Mozilla Frequent Flyer perks do not apply for All Hands''.
*Flights booked outside of Egencia will not be an approved expense unless email approval by Brianna is obtained prior to booking.
*Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

====Ground Transportation====
Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00.

Taxis and Addison Lee are not reimbursable.

If you are arriving by train to Hauptbahnhof:
To Hotel Berlin Berlin
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S5, S9 or S75 to the station “Zoologischer Garten” (20 min.). From there, take the bus 100 to the stop Lützowplatz.
* Via U-BAHN: Take the U-Bahn metro lines U2, U3 and U1 to the station “U-Nollendorfplatz”. Exit the station in the direction of “Karl-Heinrich-Ulrichs-Straße." The road leads directly to the hotel (approx 5 mins).
* [https://www.hotel-berlin.de/d/berlinberlinpro/media/PDF/Anfahrt_A4_E_Karl-Heinrich-Ulrichs-Strae_5c2ab7.pdf Map]

To InterCon Berlin and Pullman
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S3, S5, S7, or S9 to the station “Zoologischer Garten”. From there, walk 10 mins to hotel.

Berlin's integrated public transport is divided in 3 tariff zones (ABC). To travel within the city, including from Tegel airport to the hotels, you only need an AB ticket. Tickets can be bought at automated booths in most stations (accept credit cards), and on Metro (need coins). You can use the same ticket to travel on buses, metro, S-Bahn, U-Bahn. More information, including PDF maps, are available on [https://www.berlin.de/en/public-transportation/1772016-2913840-tickets-fares-and-route-maps.en.html this website]. A mobile app is also available on stores ("BVG FahrInfo Plus") and allows to create routes between stations.

=='''Families/Guests'''==
Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made. Please note that what are able to do for families varies by each location. We are unable to accommodate volunteer contributor or intern families/guests at our All Hands.

====Quick summary logistics====
* Air Travel: Employees do need to book via Egencia regardless of how families are booked.
* Hotel: Family/friends are welcome to stay with you. All room rates are based upon single occupancy and include breakfast. Guests must be added to reservations in advance and any additional room expenses will be yours to cover. Most of our hotel rooms have a maximum of double occupancy (2 adults), with very limited availability of rooms for higher occupancy. Higher occupancy rooms will be assigned in the order that you register. We will have extra rooms available for families to book and pay for at our hotels.
* Lunch & Dinner: Family will be on their own for lunch daily and dinner on Tuesday, Wednesday & Thursday.
* Monday & Friday Night Events: Family members who are registered for the event and registered with the hotel, are invited to join us for our evening events.
* Childcare Services: We will not provide centralized childcare services. We have found that every family has different needs and centralized childcare does not deliver on those needs. If you are in need of help finding options for your family, we are happy to connect you with staff whose families who are coming (#allhands-childcare and #parents are great places to start), as well we are happy to help support finding of resources (although you are likely better at it than us). Given every circumstance is unique, we defer to your manager to determine what Mozilla can support you with financially.

On demand babysitting services in Berlin:
* https://extra-arms.com/for-families-babysitting/
* https://www.withourbaby.com/

=='''Lunar New Year'''==
We are aware of the overlap in the Lunar New Year celebrations with the Berlin All Hands. To help folks who decide to attend the Berlin All Hands and who also celebrate Chinese New Year, we will offer the following:
* A higher airfare caps for air travel to allow for fewer layovers on Monday, January 27
* Assurance that Berlin is optional but if employee wants to attend they can shift their holiday days to another time.
* Live Airmo Feeds of Plenary (+ relevant team all hands meetings) + quick posting of recording to accommodate those who choose not to travel.
* Potentially shifting any main plenary session date/time

We are working with leadership and representatives of those most affected and will update wiki regularly with updates. Feel free to reach out to Brianna with questions.

=='''Safety & Security'''==
=====Alcohol at Events=====
To better support and sustain an environment (and workplace culture) where people feel safe and included, we have made a set of changes regarding alcohol at our events. In all cases, our approach aligns with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).
*All participants are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.
*We will '''limit bar-servings to beer and wine''' and ensure an equal number and quality (i.e. not just Coke) of non-alcoholic drink options are available and displayed.
*Team dinners should be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.
*Clearly outlined, communicated (to event teams, HR and managers) and understood '''escalation process''' for behavior that might be deemed counter to the spirit of our CPG.

=====Device Security=====
If you are traveling to the All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Physical Security=====
Badges are required to access all meeting spaces and evening events.

=='''Accessibility'''==
====Evenings====
Monday Night reception is at the InterContinental Berlin. No stairs or elevators required.

====Meeting spaces====
* InterCon: Most meeting space levels are accessible by elevators.
* Pullman: All meeting space levels are accessible by guestroom elevators.
* Hotel Berlin: All meeting space is on the ground level.

====Listen Systems====
We will have Listen Systems available for any meeting in the main plenary space. Visit the AV booth to pick one up.

====Bathrooms====
TBA

====Breastfeeding/pumping stations====
Milk Stork Services are reimbursable - please contact benefits@mozilla.com for more information.

=='''Sustainability'''==
'''Hotel Berlin, Berlin''' is certified partner of visitBerlin we stand for sustainable, green meetings and events. For more information, visit https://convention.visitberlin.de/en/sustain.

'''InterContinental Hotel Berlin''' is Green Globe Certified. Green Globe Certification is the worldwide sustainability system based on internationally accepted criteria for sustainable operation and management of travel and tourism businesses. Operating under a worldwide license, Green Globe Certification is based in California, USA and is represented in over 83 countries. Green Globe Certification is a member of the Global Sustainable Tourism Council, supported by the United Nations World Tourism Organization. Additonally, as part of IHG’s Green Engage™ program the InterContinental Berlin has implemented best practices at all operational levels. The innovative Environmental Management System not only measures the day-to-day energy, water and waste consumption, but also provides recommended actions – ‘green solutions’ – to improve energy conservation and the property’s carbon footprint score.

=='''All Hands Expense Policy'''==
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. Berlin All Hands Expense Report). Each expense must be tagged with "All Hands - Jan 2020"

2. It must contain only those expenses relative to the All Hands Event in Berlin.

3. If your submitted expense report for All Hands is submitted outside these guidelines, it will be rejected and you will be asked to re-submit with only All Hands Expenses

4. The deadline to submit the All Hands Expense Report is '''February 28, 2020'''.

5. Expenses related to team events (except those coordinated through Lisa Carlson), parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved.

'''The intention of our all hands are to centrally organize a structure that includes:'''
*Meals (2 evening events + breakfast, lunch, drinks and snacks Tuesday - Friday)
*Transportation
*Accommodations

Expenses submitted can not exceed the approved amounts. Any social events (except dinners/team building activities coordinated through Lisa Carlson) that are not part of our central plan will generally be self-organized and funded by participants.

=====Travel expenses policy=====
Reimbursement will be made for necessary and reasonable expenses.

* Getting to/from home to your airport: We ask that you use the most economical option, while balancing your personal needs - whether that be mileage/parking, public transportation or ride shares. We will not reimburse for private towncar services or car rental.
* Per standard Mozilla travel policy, Travel Meal Policy: Employees are eligible for travel meals when traveling. For Meals: There is a $75 USD per day meal policy while traveling. This covers breakfast (est. $15), lunch (est. $20), and dinner (est. $40). Receipts: Receipts are required. When submitting a meal for reimbursement, please include how many people attended the meal. There is no need to include names.
* We will not reimburse for seat/class upgrades. Frequent flyer status does not apply for All Hands.
* We will reimburse for bag checking fees for one bag.

Any other expenses must be approved by your manager ahead of time. Any expenses for extending your stay for business reasons - such as additional hotel nights, meals, etc must be approved by your manager before booking and travel.

=====Cell phone reimbursement policy=====
Cell phone reimbursement must be approved by your manager prior to submitting the expense. Teams will decide for their staff what is appropriate to expense.

=====Internet reimbursement policy=====
Internet will be provided in all guestrooms and meeting space in all hotels. If you opt to upgrade/add service, those costs are not reimbursable, unless previously approved by your manager and are for business reasons.

=='''Activities'''==

L10n:Goals/H2-2019

2019-08-12T17:52:57Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==

==Roundtable==

=== Axel ===

=== Delphine ===

=== Flod ===

Ensure that the process to add new languages to Firefox desktop is correctly documented, and plan overall cleanup of existing documentation.
* [] Update internal documentation related to search settings for Firefox desktop.
* [] Integrate existing localizer documentation for testing Firefox desktop.
* [] Analyze existing internal documentation, remove content covering obsolete tools, and file issues for the respective owners to update or remove obsolete content.

Increase the pool of reviewers for Fluent changes and reduce the review load on our team by including front-end developers in the process.
* [] Onboard and add at least one developer to the fluent-reviewers group in Phabricator.
* [] Remove existing Mercurial hook on FTL files.

=== Jeff ===
;Executing on the BWX transition.
* Terminology working group is using BWX for terminology management.
** Create a process for adding target language term equivalents.
* Work with BWX to tackle all P1 projects on schedule.

;Define role of MT in the l10n process and collect list of candidate vendors of production MT.
* Define three use cases for MT at Mozilla.
* Identify where MT use cases fit within l10n process.
* Define our linguistic data story for MT.
* Develop a pilot project with a MT vendor.

=== Matjaž ===

* [] Implement Batch actions in Translate.Next
* [] Implement Filters in Translate.Next
* [] Implement 3-column Translation Workbench
* [] Implement Pre-Translation functionality

=== Peiying ===

=== Stas ===

=== Adrian ===

* '''Organize a Pontoon Community Meetup'''
** Objective of the meetup is to devise a plan of action to increase support for 3rd party (non-Mozilla) users of Pontoon.
** Get contributors from various backgrounds there, invite people who are using Pontoon outside of Mozilla's instance.
** Draft a vision for Pontoon.
** Create processes for developing features that are not a priority for Mozilla.
* '''Log all actions happening in Pontoon and expose that data'''
** Create a data store to log every single action that happens in Pontoon (user actions, automated actions [sync], manager actions, etc. ).
** Estimate the amount of data that represents, choose a storing technology that can handle that load.
** Expose that data through the public API.

=== Theo (optional) ===

L10n:Teams:nl

2019-04-24T16:04:14Z

Flod:

__NOTOC__
=== Dutch (nl) ===
[[File:Mozilla_nl_logo.png|Mozilla Nederland Logo|right|140px]]
Team website: [http://www.mozilla-nl.org Mozilla Nederland]

Support forum: [http://www.mozbrowser.nl Mozbrowser forum]

Team group on Mozillians: [https://mozillians.org/nl/group/l10n-nl/ Mozillians l10n:nl]

Bugzilla: [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=nl%20/%20Dutch file a bug for Dutch localization]

====Active team members====
{| border="1" class="wikitable"
|-
! Name
! Email
! Nickname
! Role (owner)
! Hg Access?
! SVN Access?
|-
| [https://mozillians.org/nl/u/84afd10fdb/ Mark Heijl]
| markh(at)babelzilla.org
| markh
| AMO
| NO
| NO
|-
| [https://mozillians.org/nl/u/moZes/ Wim Benes]
| frysk(at)mozilla-nl.org
| Mozes
|
| YES
| YES
|-
| [https://mozillians.org/u/oeekker/ Onno Ekker]
| o.e.ekker(at)gmail.com
| nONoNonO
| Thunderbird SeaMonkey
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1006104 YES]
| NO
|}

====Localizers in training====
{| border="1" class="wikitable"
|-
! Name
! Email
! Nick
! Project assignment
|-
|
|
|
|

|}

====Previous localizers====
{| border="1" class="wikitable"
|-
! Name
! Nick
! Role
|-
| Ton Kessen
| tonnes
| Gaia, Calendar, SUMO
|-
| [https://mozillians.org/nl/u/Mad_maks/ Tim Maks van den Broek]
| mad_maks
| Browser, Mail, Toolkit, Mobile, Suite
|-
| Gert-Paul van der Beek
|
| Toolkit/Browser/Mail
|-
| Koen Hendrckx
|
| Calendar
|-
| Ben Branders
|
| Mozilla Europe
|-
| René van Roon
|
| Thunderbird
|-
| Hendrik Maryns
|
|
|-
| Niek Dekker
|
| Seamonkey
|-
| Martijn Ras
|
| Mozilla Suite
|}

====Active projects====
;Software projects
* Calendar
* Firefox (desktop)
* Firefox (Android)
* Firefox OS (Gaia)
* SeaMonkey
* Thunderbird

Current status of all software projects is available on the [https://l10n.mozilla.org/shipping/dashboard?locale=nl Dutch Dashboard].

;Web Projects
* [https://support.mozilla.org/ SUMO] ([https://support.mozilla.org/nl/localization current status])
* [http://addons.mozilla.org/ AMO/Marketplace] ([https://localize.mozilla.org/nl/amo/ current status])
* [http://www.mozilla.org/en-US/persona/ Persona] ([https://localize.mozilla.org/nl/browserid/ current status])
* [https://firefoxflicks.mozilla.org/ Firefox Flicks] ([https://localize.mozilla.org/nl/firefoxflicks/ current status])

====L10n kit====
;Tools:
We use the Mercurial version control system (Hg) to manage our source code and localizations. Localizers in training can get a updated zipfile with the localization files or pull the files from [https://developer.mozilla.org/en-US/docs/Localizing_with_Mercurial?redirectlocale=en-US&redirectslug=L10n_on_Mercurial Mercurial]

All localizers working on software projects use a texteditor. The localization process is managed individually by each module owner on his own schedule. When possible web content is managed on [https://localize.mozilla.org/nl/ Verbatim], in order to let more people cooperate.

;Translation Memory:
We currently use [http://transvision.mozfr.org/ Transvision]. This tool is useful in several situations, for example to check if wrong strings belong to the software or an add-on, identify in which file a particular string is saved or check how an English string is localized (this is extremely important for SUMO articles).
;Glossary:
Our team doesn't have an official glossary. The most common terms are available in our [http://www.mozilla-nl.org/nl/woordenboek Style guide], if a term is missing we rely on [http://transvision.mozfr.org/ Transvision]'s search.
;Style Guide:
A brief [http://www.mozilla-nl.org/nl/woordenboek Style guide] is available on our website.

====How to join this l10n team====

Send a mail to one of the teammembers and he/she will help you with the next steps

===== Localizing SUpport.MOzilla.org (SUMO) =====
If you want to help localize http://support.mozilla.org/nl into your language, please do the following:
# [https://support.mozilla.org/users/authcontributor Create a SUMO account]
# If you can, [https://support.mozilla.org/groups/dutch-localization get in touch with the Group Leader(s) listed here via a Private Message]. If there is nobody listed there, please get in touch with [http://support.mozilla.org/user/vesper Michał / vesper].
# [https://support.mozilla.org/kb/localize-mozilla-support Read our universal l10n documentation here]. For language-specific documentation, please get in touch with your Group Leader(s).
# [https://support.mozilla.org/forums/l10n-forum/711094 Visit our forums and introduce yourself to the community]. We don’t bite, unless you’re made of cake ;-)
# You're ready to go! If you have any questions, ask them on the forums.


====Team communication====
We use our [http://mozbrowser.nl support forum] for all the QA process and coordinate the localization of all current projects.

<noinclude>[[category:L10n Teams|nl]]</noinclude>

GitHub

2019-03-31T15:05:52Z

Flod:

This page is specifically about [https://github.com/mozilla the "mozilla" organization on github]. There are several other github organizations you may be interested in, cf. the incomplete list [[#other_github|below]].
<div id="contact">
{| class="wikitable"
|-
! [[File:Red_question_mark.png|144px|Send us an email!|link=]] Got a GitHub administration question?
|-
| Email {{emailentry|github-owners|mozilla.org|at=is}} 
Bugzilla [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& mozilla.org :: Github: Administration] 
irc #github on [[IRC|moznet]]
|}

== News ==
* 2019-02-19 - Mozilla's Code of Conduct is required to be included in every repository, following [[/Repository Requirements|this procedure]].
* 2018-03-29 - new [[/Repository Security|Guidelines for securing sensitive repositories]] published. These are good practices for any repository that does "releases", and some groups my require adherence on their repositories.

== Recommendations and FAQ ==

=== Where should I ask additional questions? ===
* Send an email to '''{{emailentry|github-owners|mozilla.org|at=is}}''' and we'll respond right away! We're also available on #github on irc.

=== How do I hook up a new 3rd party application to a repository in the mozilla org? ===
{{note|There are now multiple 3rd pary application types. "GitHub Apps" (nee integrations) are the new approach and preferred.|gotcha}}
{{note|Some 3rd party apps use GitHub as an OAuth identity provider for their website (e.g. for a dashboard). An ''OAuth Application'' will block the installation process if the app is not already approved. The "Request access" block is what this section describes.|gotcha}}

Each type has it's own installation and approval process. Please follow the instructions in the correct section below.

==== GitHub Apps Installation & Approval Process ====

GitHub Apps (formerly called "integrations") are "Installed" into either the entire organization, or into individual repositories. Each integration has a documented and granular access to repository resources. This is good.

However, the GitHub App installation can only be done by an organization owner, who may have to do additional housekeeping. This is not so good, so please plan accordingly (you may need to coordinate with [[#contact|GitHub owners]]).

* File a request using this [https://bugzilla.mozilla.org/enter_bug.cgi?cc=gene%40mozilla.com&comment=I%20want%20to%20use%20the%20NAME_HERE%20addon%20in%20ORG_NAME_HERE%20for%20the%20following%20reasons%3A%0D%0A%0D%0ABelow%20are%20my%20answers%20to%20your%20stock%20questions%3A%0D%0A%0D%0A%2A%2A%20Which%20repositories%20do%20you%20want%20to%20have%20access%3F%20%28all%20or%20list%29%0D%0A%0D%0A%2A%2A%20Are%20any%20of%20those%20repositories%20private%3F%0D%0A%0D%0A%2A%2A%20Provide%20link%20to%20vendor%27s%20description%20of%20permissions%20needed%20and%20why%0D%0A%0D%0A%2A%2A%20Provide%20the%20Install%20link%20for%20a%20GitHub%20app%0D%0A&component=Github%3A%20Administration&product=mozilla.org&short_desc=Assess%20use%20of%20external%20addon%20NAME_HERE%20in%20Mozilla%27s%20GitHub%20organization%20ORG_NAME_HERE bug template]
* Include answers to these questions:
** Which repositories do you want to have access? (all or list)
** Do any of those repositories contain "sensitive" data? (e.g. private repos or ones where unauthorized code changes could have significant impact to Mozilla)
** Provide link to vendor's description of permissions needed and why
** Provide installation instructions:
*** Please include the GitHub App's "install" link
* If you are not an "admin" for the repository, an "admin" will have to approve the request.

===== Initial Installation =====
If this is the first time this GitHub App is being installed in the organization, a few extra checks and coordination are needed. An organization owner will need to perform these steps:
* Determine if the GitHub App previously had an OAUTH version.
** If so, it is likely that installing the integration will disable all repositories in the organization using the OAUTH version of the application.
** Find all current repositories using the classic OAUTH application (this is non-trivial, scripts exist to help)
** Install the Integration for all current repositories, and the new one (organization owner permissions needed.)

'''Please do not install GitHub apps with organization wide scope without first discussing with [[#contact|GitHub owners]].'''

===== Additional Installations or Removals =====
If the GitHub App has already been installed in the organization, the new repository simply needs to be added or removed from the list. An organization owner has to make this change. Please still [https://bugzilla.mozilla.org/enter_bug.cgi?cc=gene%40mozilla.com&comment=I%20want%20to%20use%20the%20NAME_HERE%20addon%20in%20ORG_NAME_HERE%20for%20the%20following%20reasons%3A%0D%0A%0D%0ABelow%20are%20my%20answers%20to%20your%20stock%20questions%3A%0D%0A%0D%0A%2A%2A%20Which%20repositories%20do%20you%20want%20to%20have%20access%3F%20%28all%20or%20list%29%0D%0A%0D%0A%2A%2A%20Are%20any%20of%20those%20repositories%20private%3F%0D%0A%0D%0A%2A%2A%20Provide%20link%20to%20vendor%27s%20description%20of%20permissions%20needed%20and%20why%0D%0A%0D%0A%2A%2A%20Provide%20the%20Install%20link%20for%20a%20GitHub%20app%0D%0A&component=Github%3A%20Administration&product=mozilla.org&short_desc=Assess%20use%20of%20external%20addon%20NAME_HERE%20in%20Mozilla%27s%20GitHub%20organization%20ORG_NAME_HERE file a bug]. As before, a repository admin has to approve the request.

If you're an org owner, you can [https://github.com/organizations/mozilla/settings/installations see what has already been installed].

==== OAUTH (classic) Applications ====

* Authorizing an application to work with GitHub utilizes the permissions your account has -- so, any repositories you have access to the application will have access to as well (including private ones). If you want to grant access to an application that no one else has used with the Mozilla organization yet you'll see a "Request access" button during the set up flow. You'll need to click that button to request approval. See below for an example:

[[File:github_approval.png]]

* In some cases, the application does not need to be "approved" to function correctly, as it has read only access to any public repository. (Some applications only want write access to help you configure the application first time.)

* In other cases, the application does need write permission, and/or permission to read a private repository. In these cases, open a bug using [https://bugzilla.mozilla.org/enter_bug.cgi?cc=gene%40mozilla.com&comment=I%20want%20to%20use%20the%20NAME_HERE%20addon%20in%20ORG_NAME_HERE%20for%20the%20following%20reasons%3A%0D%0A%0D%0ABelow%20are%20my%20answers%20to%20your%20stock%20questions%3A%0D%0A%0D%0A%2A%2A%20Which%20repositories%20do%20you%20want%20to%20have%20access%3F%20%28all%20or%20list%29%0D%0A%0D%0A%2A%2A%20Are%20any%20of%20those%20repositories%20private%3F%0D%0A%0D%0A%2A%2A%20Provide%20link%20to%20vendor%27s%20description%20of%20permissions%20needed%20and%20why%0D%0A%0D%0A%2A%2A%20Provide%20the%20Install%20link%20for%20a%20GitHub%20app%0D%0A&component=Github%3A%20Administration&product=mozilla.org&short_desc=Assess%20use%20of%20external%20addon%20NAME_HERE%20in%20Mozilla%27s%20GitHub%20organization%20ORG_NAME_HERE this template].
** Please be sure to have clicked the "Request Approval" link before submitting bug.
* Include answers to these questions:
** Provide link to vendor's description of permissions needed and why
** Provide installation instructions (both may be needed):

=== Reviewing owners and permissions ===
As an owner or repository admin you're responsible for maintaining the list of people with access to your projects. Please be active and prudent about maintaining this list.

=== Can I be an Owner of the Mozilla Organization? ===
The Owners group on GitHub has complete administrative power and will be limited to a minimal number of people and reviewed regularly. If a person is an owner, they are expected to actively participate in the group and assist others as requested. Owners will be added as a need arises (for example, support in another timezone) as determined by the current owners.

=== Can I be a Member of the Mozilla Organization? ===
<div id="join"> </div>
==== Contributor Information ====
Good news! You do not need to be a member of the Mozilla organization on GitHub before you can contribute to Mozilla!!!! We have several sites which can help you find the best fit for contribution:
* General [https://www.mozilla.org/en-US/contribute/ volunteering options],
* Or pick from [http://whatcanidoformozilla.org/ these areas],
* Or jump right into [http://www.joshmatthews.net/bugsahoy/ fixing a bug].
* If you're already a contributor (THANK YOU!) looking for a place to have your work recognized (even if not coding related), please see the [https://www.mozilla.org/credits/FAQ Credits FAQ] for inclusion in the [https://www.mozilla.org/credits/ credits].

Once you're working on a project, the project leaders can help you get access to anything you need.

==== Team Maintainers & Project Leads ====

Project owners and team maintainers may find the following information helpful when asking for access for a new team member:

* We prefer the use of github teams.
* All members of the [https://github.com/mozilla/ Mozilla organization on github] agree to be bound by [https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/ Mozilla's Commit Access Requirements], and should follow the intent of the [https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ Mozilla's Commit Access Policy] as much as practical.
** "Outside Collaborator": repository admins can grant outside collaborator to any GitHub account. "Outside Collaborator" is roughly analogous to "Level 1a" access to Mozilla-hosted repositories.
** "Team Member": team maintainers can add GitHub users to a team, if they are already a member of the organization. If you are not yet a member of the organization, the team maintainer should [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%23Team_Maintainers_.26_Project_Leads%2C%20and%20need%20help%20adding%20a%20contributor%20to%20the%20org%3A%0D%0A%0D%0AName%3A%20%0D%0AMozilla%20Email%3A%20%0D%0AGithub%20Profile%20link%3A%20%0D%0AGithub%20Team%28s%29%3A%20%0D%0A%0D%0AIf%20this%20is%20not%20being%20requested%20by%20a%20team%20maintainer%2C%20please%20request%20their%20approval%20via%20need-info.&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org file a bug using this link] to add you to their team, as a form of vouching. "Team Member" is roughly analogous to "Level 2" or "Level 3", with the distinction being the content of the repositories managed by the team.

To get access for a new Contributor, please [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%23Team_Maintainers_.26_Project_Leads%2C%20and%20need%20help%20adding%20a%20contributor%20to%20the%20org%3A%0D%0A%0D%0AName%3A%20%0D%0AMozilla%20Email%3A%20%0D%0AGithub%20Profile%20link%3A%20%0D%0AGithub%20Team%28s%29%3A%20%0D%0A%0D%0AIf%20this%20is%20not%20being%20requested%20by%20a%20team%20maintainer%2C%20please%20request%20their%20approval%20via%20need-info.&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org file a bug using this link], and fill in the details.

'''Please Note:'''
* We will cancel any invitation to the organization which is not accepted within 2 weeks.
* All members of the Mozilla organization on GitHub '''MUST''' have [https://help.github.com/articles/about-two-factor-authentication/ 2FA enabled].
* Automation accounts are also required to have 2FA enabled. Scripts should use [https://help.github.com/articles/creating-an-access-token-for-command-line-use/ access tokens] with minimum permissions to accomplish the task.

=== Should I make a separate github organization or just create a repository in an existing one? ===
This is a personal preference, in general. (Some product lines may have policies about source code locations.) If you have a large enough project or organization feel free. We suggest you use the strategies and recommendations here as a model to manage the details. Additional resources on establishing an organization are:
* [https://mana.mozilla.org/wiki/display/POLICIES/Standard%3A+GitHub+repositories+and+organizations Mozilla Standards] ''login required''
* [[/Repository Security|Guidelines for securing sensitive repositories]]
* If you need any paid services, contact github owners for access to [https://github.com/mozilla/admin_for_mozilla_private/wiki/Billing-Notes Billing Notes]

=== Forking vs Transferring ===
'''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it.

If you have created a repo on your own account (for example, myuser/myrepo) and it should live under the Mozilla organization, here are the steps:

# If you're not a member of any team, talk to an [[#contact|org admin]].
# Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.
# Choose which teams should be given access. All chosen teams will have only 'read' access at this point.
# [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&bug_file_loc=http%3A%2F%2F&bug_ignored=0&bug_severity=normal&bug_status=NEW&cc=gene%40mozilla.com&cf_fx_iteration=---&cf_fx_points=---&comment=I%20just%20transferred%20the%20NAME_HERE%20repository%20to%20the%20ORG_NAME_HERE%20organization%2C%20and%20thus%20no%20longer%20have%20admin%20access.%0D%0A%0D%0APlease%20enable%20admin%20access%20for%3A%0D%0A-%20the%20TEAM_NAME%20team%20%28preferred%29%2C%20or%0D%0A-%20just%20me%20--%20I%27ll%20take%20care%20of%20the%20rest&component=Github%3A%20Administration&contenttypemethod=list&contenttypeselection=text%2Fplain&defined_groups=1&flag_type-4=X&flag_type-607=X&flag_type-800=X&flag_type-803=X&form_name=enter_bug&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Unspecified&priority=--&product=mozilla.org&rep_platform=Unspecified&short_desc=Admin%20access%20needed%20to%20transferred%20repository&target_milestone=---&version=other File a bug] to grant admin permissions to a team or yourself. {{note|As soon as you transfer, your repository will be in "limbo" (only you will have write access) due to a GitHub bug. Make arrangements in advance to have an owner available to process the bug.|gotcha}}
# Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating myuser/myrepo). While the transferred repo becomes the root of the network on GitHub (e.g. all forks are now forks of mozilla/myrepo) other users may be pointing to your repo by URL. (Optional, github will redirect old URLs for transfers, but you probably want a local repo if you use the PR workflow.)

=== Do I need to be an owner to create repositories? ===
Not in the 'mozilla' organization. If you are a member, you can create a repository. Other organizations may restrict repository creation. However, it's preferred that you create repositories in the context of a team. Teams are created [https://github.com/orgs/mozilla/teams here], if necessary. Once you have created a repo, you can configure it to give rights to members of particular teams.

{{note|Remember that all repositories must comply with the [[GitHub/Repository Requirements]].|reminder}}

As the creator, you will automatically have "admin" permissions on the repository. Repository Admins are responsible for the security settings of the repository. This includes approving (or not) requests for GitHub Apps to be added to the app.

Please review all the settings for your new repository, and disable features you will not be using. The default values can change, and new services added, so specific guidance can't be given. But do you really need that wiki? Or the project board? You can always enable them later if you decide you need them.

=== We have sensitive code or data in this repository - any extra steps I should take? ===
Yes. Even if your repository is private, there are steps you can take to ensure you know if something has changed. See the [[GitHub/Repository Security]] page for additional information and a checklist.

=== We're done with this project - what should we do with the repository? ===

That is really up to the team. However, if you have forks or other active user participation, it's a good idea to be clear about the status of Mozilla's commitment to the project. Your options include:
* Delete the repo (obviously the worst alternative).
* Add the [http://unmaintained.tech/ Unmaintained] badge to the readme
* Archive the repository, using [https://help.github.com/articles/about-archiving-repositories/ GitHub's suggestions].

'''PLEASE''' make sure the repository is clearly licensed before leaving it. Without a license, many other folks can not build upon your work.

=== Are there requirements for when or how I should create a new team? ===
No. When requirements were proposed they all seemed too rigid and time consuming. Instead we recommend staying flexible and using good naming and documentation for projects (similar to naming CSS classes or variables).

On large teams we recommend you separate teams for read/write and repository administration.

<div id="other_github"></div>
=== Is "mozilla" the only github "organization" related to Mozilla? ===
No, there are plenty of Mozilla-related "organizations" on github. As a rule of thumb, initiatives that create a large number of sub-repositories will create their own "organization". Here is a (probably incomplete) list of them:
{| class="wikitable sortable"
|-
! Organization !! Description !! Contact Owner
|-
| [https://github.com/mozilla-it mozilla-it] || Mozilla IT's repositories || ?
|-
|[https://github.com/mozillabrasil mozillabrasil] || Mozilla Brazil|| ?
|-
| [https://github.com/bugzilla bugzilla] || Bugzilla (the product, not bugzilla.mozilla.org) || #bugzilla
|-
| [https://github.com/drumbeat-badge-sprint drumbeat-badge-sprint] || Drumbeat Badge Lab || ?
|-
| [https://github.com/hackasaurus hackasaurus] || Hackasaurus || ?
|-
| [https://github.com/jetpack-labs jetpack-labs] || Jetpack Labs || ?
|-
| [https://github.com/mdn mdn] || Mozilla Developer Network || [https://github.com/jwhitlock John Whitlock]
|-
| [https://github.com/mozbrick mozbrick] || Mozilla Brick (web components library) || ?
|-
| [https://github.com/mozilla-appmaker mozilla-appmaker] || Mozilla Appmaker || ?
|-
| [https://github.com/mozilla-b2g mozilla-b2g] || Mozilla Boot2Gecko / Firefox OS || ?
|-
| [https://github.com/mozilla-bteam mozilla-bteam] || Bugzilla.Mozilla.org || #bteam
|-
| [https://github.com/mozilla-cit mozilla-cit] || Mozilla Community Ops || {{Mozillians|tanner|Tanner Filip}} or {{Mozillians|yalam96|Yousef Alam}}
|-
| [https://github.com/mozilla-comm mozilla-comm] || Calendaring and Messaging related projects || ?
|-
| [https://github.com/mozilla-cordova mozilla-cordova] || Firefox OS Support for Apache Cordova || ?
|-
| [https://github.com/mozilla-iam mozilla-iam] || Mozilla's identity and access management || kang
|-
| [https://github.com/mozilla-iot mozilla-iot] || Mozilla's Internet of Things program || {{Mozillian|dbryant|David Bryant}}, {{Mozillian|bfrancis|Ben Francis}}
|-
| [https://github.com/mozilla-lockbox mozilla-lockbox] || Mozilla Lockbox iOS, Android, desktop extension || [https://github.com/orgs/mozilla-lockbox/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-lockbox owners]
|-
| [https://github.com/mozilla-metrics mozilla-metrics] || Mozilla Metrics || ?
|-
| [https://github.com/mozilla-platform-ops mozilla-platform-ops] || Mozilla Platform Operations || [[Platform_Operations]]
|-
| [https://github.com/mozilla-raptor mozilla-raptor] || Mozilla Raptor / Firefox OS Performance || {{Mozillian|eliperelman|Eli Perelman}}, {{Mozillian|rwood|Rob Wood}}
|-
| [https://github.com/mozilla-releng mozilla-releng] || Mozilla Release Engineering || #releng
|-
| [https://github.com/mozilla-services mozilla-services] || Mozilla Services || [https://github.com/orgs/mozilla-services/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-services owners]
|-
| [https://github.com/mozilla-mobile/ mozilla-mobile] || Mobile: Android Product Team & Firefox iOS teams || [https://github.com/orgs/mozilla-mobile/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-mobile owners]
|-
| [https://github.com/mozilla-standards mozilla-standards] || Mozilla Standards (for IPR Contributions) || [https://mozillians.org/u/dbaron/ dbaron], [https://mozillians.org/u/annevk/ annevk]
|-
| [https://github.com/mozilla-svcops mozilla-svcops] || Mozilla Cloud Services Ops || {{Mozillian|relud|Daniel Thornton}}
|-
| [https://github.com/Mozilla-TWQA Mozilla-TWQA] || Mozilla Taiwan QA || ?
|-
| [https://github.com/mozillahispano mozillahispano] || Mozilla Hispano || ?
|-
| [https://github.com/MozillaScience MozillaScience] || Mozilla Science Lab || ?
|-
| [https://github.com/MozillaSecurity MozillaSecurity] || Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it. || ?
|-
| [https://github.com/MozillaWiki MozillaWiki] || MozillaWiki (wiki.mozilla.org) || {{Mozillian|ckoehler|Christie Koehler}}, {{Mozillian|gphemsley|Gordon P. Hemsley}}
|-
| [https://github.com/mozillayvr mozillayvr] || Mozilla Vancouver @MozillaYVR || {{Mozillian|bclark|Brian Clark}}, {{Mozillian|shobson|Stephanie Hobson}}
|-
| [https://github.com/mozfr mozfr] || Mozilla Francophone || Pascal Chevrel https://mozillians.org/fr/u/pascalc/
|-
| [https://github.com/opennews opennews] || Knight-Mozilla OpenNews || ?
|-
| [https://github.com/rust-lang rust-lang] || The Rust Programming Language || {{Mozillian|aturon|Aaron Turon}}
|-
| [https://github.com/servo servo] || Servo (browser engine written in Rust) || {{Mozillian|larsberg|Lars Bergstrom}}, Jack Moffitt
|-
| [https://github.com/tabulapdf tabulapdf] || Tabula project (extract data from PDF files) || ?
|-
| [https://github.com/webcompat webcompat] || Web Compatibility Team || {{Mozillian|miketaylr|Mike Taylor}}
|-
| [https://github.com/mozilla-l10n mozilla-l10n] || Mozilla l10n-drivers team || Francesco Lodolo https://mozillians.org/u/flod/
|-
| [https://github.com/taskcluster taskcluster] || [[TaskCluster]] Team || [https://github.com/gregarndt Greg Arndt]
|-
| [https://github.com/MozillaCH MozillaCH] || Mozilla [[Switzerland]] || {{Mozillian|mkohler|Michael Kohler}}, {{Mozillian|freaktechnik|freaktechnik}}
|-
| [https://github.com/mozmeao MozMEAO] || Mozilla [[Marketing]] || {{Mozillian|bensternthal|Benjamin Sternthal}}, {{Mozillian|pmac|Paul McLanahan}}
|-
| [https://github.com/mozilla-payments mozilla-payments] || Implementation of Web Payment APIs || {{Mozillian|Marcos Caceres}}
|-
| [https://github.com/mozilla-jetpack mozilla-jetpack] || Resources for Mozilla's Add-on SDK || ?
|-
| [https://github.com/web-ext-experiments web-ext-experiments] || WebExtension API Experiments || {{Mozillian|andym|Andy McKay}}
|-
| [https://github.com/mozilla-conduit mozilla-conduit] || Mozilla Conduit work || {{Mozillian|mcote|Mark Côté}}
|-
| [https://github.com/mozsearch mozsearch] || The code that runs Searchfox.org || {{Mozillian|kats|Kartikaya Gupta}}
|-
| [https://github.com/MozillaCZ/ MozillaCZ] || [https://www.mozilla.cz/ Mozilla.cz] || {{Mozillian|mstanke|Michal Stanke}}, {{Mozillian|MekliCZ|Michal Vašíček}}, {{Mozillian|zelitomas|Tomáš Zelina}}
|-
| [https://github.com/MozillaSK/ MozillaSK] || [https://www.mozilla.sk/ Mozilla.sk] || {{Mozillian|mstanke|Michal Stanke}}, {{Mozillian|kusavica|Juraj Cigáň}}
|}

=== Are there other unofficial or Mozilla-related repositories hosted on Github? ===
Why, yes! In no particular order:

* [https://github.com/kinetiknz/cubeb/ https://github.com/kinetiknz/cubeb/] : Cubeb cross platform audio library.
* [https://github.com/djg/cubeb-rs/ https://github.com/djg/cubeb-rs/] : Rust bindings for cubeb.
* [https://github.com/kinetiknz/nestegg/ https://github.com/kinetiknz/nestegg/] : WebM demuxer.
* [https://github.com/xiph/opus/ https://github.com/xiph/opus/] : Modern audio compression for the internet.
* [https://github.com/webmproject/libvpx https://github.com/webmproject/libvpx] : Mirror only. Please do not send pull requests.
* [https://github.com/campd/fxdt-adapters https://github.com/campd/fxdt-adapters] : Firefox Developer Tools protocol adapters
* [https://github.com/kripken/emscripten https://github.com/kripken/emscripten] : Emscripten: An LLVM-to-JavaScript Compiler
* [https://github.com/bbondy/codefirefox https://github.com/bbondy/codefirefox] : Video and exercise based tutorial site for coding Firefox and other Mozilla related technology
* [https://github.com/nickdesaulniers/where-is-firefox-os https://github.com/nickdesaulniers/where-is-firefox-os] : A map showing where in the world Firefox OS phones are being sold.
* [https://github.com/jdm/bugsahoy https://github.com/jdm/bugsahoy] : A landing page to make finding relevant bugs easier for new Mozilla contributors.
* [https://github.com/w3c/web-platform-tests https://github.com/w3c/web-platform-tests] : Test Suites for Web Platform specifications
* [https://github.com/w3c/wptserve https://github.com/w3c/wptserve] : Web server designed for use with web-platform-tests
* [https://github.com/w3c/wptrunner https://github.com/w3c/wptrunner] : Cross-browser and multi-platform test runner for web-platform-tests. Used in mozilla-central and servo.
* [https://github.com/w3c/testharness.js https://github.com/w3c/testharness.js] : (no description)
* [https://github.com/jdm/asknot https://github.com/jdm/asknot] : Ask not what Mozilla can do for you but what you can do for Mozilla.
* [https://github.com/jeffbryner/MozDef https://github.com/jeffbryner/MozDef]: Mozilla Defense Platform.
* [https://github.com/jgraham/webdriver-rust https://github.com/jgraham/webdriver-rust]: WebDriver library for Rust.
* [https://github.com/ehsan/mozilla-cvs-history https://github.com/ehsan/mozilla-cvs-history]: A git conversion of the full Mozilla CVS history, useful for code archaeology.
* [https://github.com/djg/audioipc-2 https://github.com/djg/audioipc-2]: Audio IPC for Gecko.
* [https://github.com/hsivonen/encoding_rs https://github.com/hsivonen/encoding_rs]: encoding_rs (character encoding converters for Gecko)
* [https://github.com/choller/firefox-asan-reporter https://github.com/choller/firefox-asan-reporter] : Internal addon used in conjunction with special ASan builds of Firefox.
* [https://github.com/jrmuizel/qcms https://github.com/jrmuizel/qcms] : Fork of 'quick color management' for Firefox

L10n:Goals/H2-2018

2019-03-12T06:11:14Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==
Please ensure that individual goals (all or part) are contributing to our [https://docs.google.com/spreadsheets/d/1ZO4OfDZEA7zweUULaoxvmS8Vhyc1ZgXtl7v7pAIdoSg/edit#gid=0 2018 OKRs for localization]. Citing the OKR that your H2 goal contributes to in your goal section is preferred.
* Fluent in Gecko - '''Zibi''', Ax, F, S
* Multilingual Firefox - '''Flod''', Z, J, Ax
* Fluent 1.0 - '''Stas''', Z, Ax
* New brand translation policy - '''Peiying''', Z, F, D
* compare-locales in Pontoon - '''Matjaz'''
* Pontoon translate view in React/Fluent - '''Adrian'''
* Android strings.xml - '''Axel''', M, D

==Roundtable==

=== Axel ===
* '''Cross-channel for git and Android projects'''
** Supporting Android strings.xml
** Generate a single repository with ''all'' Android strings
*** Focus/Klar, Firefox for TV
*** Optional, TBC: Rocket
* '''Support for Strings.xml in compare-locales'''
** Supporting Android strings.xml
** tier0 and tier1, https://bugzilla.mozilla.org/buglist.cgi?bug_id=1472157%2C1473577%2C1465342%2C1472150%2C1466088%2C1465341%2C1465517%2C1466836%2C1472149%2C1465711
* Support for Android Components
** Supporting Android strings.xml
** Multiple strings.xml files against one cross-channel
** Multiple reference files for one localized file support in compare-locales

=== Delphine ===
* OKR: Android products can be rapidly bootstrapped and continuously localized.
** '''We need to bootstrap new localizations on mobile faster. We’re going to experiment with at least 2 possible methods for this, and evaluate which one is more effective. I'll create a comparison of how each method went, which one(s) can scale in which regions and in which situations'''
** '''Get at least 4 Indic locales ready to ship on Rocket for the initial India launch'''
** Co-create scope document for Pre-Translation feature

* OKR: Increase l10n community's organizational and procedural efficiency.
** Experiment with 2 methods, and with 2 communities, to reduce unreviewed suggestions, and then evaluate and create a report on how well each of them went.
** '''Organize design sprint to design a translation feedback solution'''

* Not WorkDay - Probably Q1 2019 stuff
** [Translate.Next] Spread the word and get people engaged in Adrian's A/B testing for an improved review process

=== Flod ===

===== Firefox Desktop =====

Supporting '''Multilingual Firefox''':
* [DONE] Finalize first iteration of language switcher in preferences (copy, userflow, design), land it in Firefox 63/64 (M1).
* [DONE] Define, start collecting telemetry data relevant for multilingual users (M1).
* [BLOCKED] Help designing, driving implemention and testing improvements of download page for mozilla.org (M2).
* [PARTIAL] Define scope and actionable items for next milestones (M3-M5).

Supporting '''Fluent in Gecko''':
* [DONE] Support migrations to Fluent of existing parts of Gecko:
** Review and test all FTL patches for Firefox.
** Run migration on l10n repositories.
** Update and integrate documentation to cover FTL features and Pontoon UI updates.

No OKR:
* [NOT DONE] Start shipping updates to dot releases, pending further syntax issues with Fluent.

===== Other =====

Supporting '''Increase l10n community's organizational and procedural efficiency''':
* [DONE] Design 2 prototypes for translation/review solution with Matjaz and Adrian, evaluate them in a community design sprint.

No OKR:
* [DROPPED] Familiarize with CLDR Survey Tool.

=== Gandalf ===

* '''Enable full Firefox migration to Fluent'''
** Enable DTD->Fluent migration in all contexts
** Enable fluent-react in Firefox
** Enable properties->Fluent migration in all contexts
** Experiment with fluent-rs in Gecko
* '''Multilingual Firefox'''
** Support Flod with M1-5.
* '''Fluent 1.0'''
** Support Stas with Fluent 1.0 release.

=== Jeff ===
;Workday goals

'''Internal terminology management workflow will be streamlined.'''

Corresponding OKR: ''Establish consistent practice of managing Mozilla terminology for all products and brand/product names.''

This goal will be completed when:
* We define requirements for a terminology management solution.
* We evaluate at least 3 candidate solutions against our requirements.
* We make a selection and formulate/execute a migration plan for existing terminology data.
* We educate UX, SUMO, and others on using the solution and define an effective, streamlined pipeline for proposing, evaluating, and finalizing new terms.
* We create a product requirement document (PRD) for terminology management in Mozilla l10n toolchain to determine the investment and its return if we were to build our own solution.

'''L10n team is ready to scale localization for more mobile projects on faster timelines.'''

Corresponding OKR: ''Android products can be rapidly bootstrapped and continuously localized.''

This goal will be completed when:
* Existing technical pain points in mobile l10n projects have been identified and scoped.
* We can predict scale challenges in human overhead and technical inefficiencies.
* We have a plan to account for scale challenges that is approved by leadership.

=== Matjaž ===
* Make localizer-critical data available in Pontoon
** '''[DONE]''' Implement support for errors and warnings in dashboards and filters
** '''[DONE]''' Implement file-level priorities
** '''[DONE]''' Implement file-level deadlines

* Improve path to first contribution to localization at Mozilla
** '''[DONE]''' Implement new Pontoon homepage (mentor a GSoC student)
** '''[DONE]''' Create a guided tour of Pontoon (co-mentor a GSoC student)
** '''[DONE]''' Implement the ability to request a new locale through Pontoon

* Make Android products rapidly bootstrappable and continuously localizable in Pontoon
** '''[DONE]''' Add support for XML file format used in Android
** '''[DONE]''' Find source files (en-US) through project configuration
** '''[DONE]''' Find localization files through project configuration
** '''[DONE]''' Expose localizable files by using project configuration

* Improve translation review & feedback process in Pontoon
** '''[DONE]''' Co-design two translation review & feedback proposals
** '''[DONE]''' Create prototype of one translation review & feedback proposal
** '''[DONE]''' Choose the translation review & feedback proposal at the community meetup

=== Peiying ===
* [OKR]Brand name localization guideline, documentation and implementation
** Make recommendations based on Firefox desktop user base to prioritize top 3 language and country for potential branding trademark registration(s).
** Create documentation for trademarked brand names (existing and newly approved) on implementing them into products and projects.
** Incorporate brand names (trademarked, declensed, and/or transliterated) into Mozilla terminology system and for all products. 
* [OKR] Modernize localization technology and process for mozilla.org
** Requirements doc for mozilla.org finalized among l10n, bedrock, and marketing.
** Redefine minimum pages/content required for a new locale: must have, good to have and optional.
* L10n Vendor Evaluation Selection Process
** Standardize the test content for easy comparison.
** Create matrix template to measure each vendor going through evaluation process, and establish a scoring system with the intent to share matrix scores and the strengths of each vendor on file.
** Expand vendor list by two more to broaden coverage of localization need.

=== Stas ===

* '''Release Fluent 1.0'''
** Fluent Syntax 1.0 Spec is published.
*** The reference parser is used to validate the spec.
*** The Syntax Guide is up-to-date.
** Implementations have been updated to Syntax 1.0.
*** The runtime fluent module.
*** The tooling fluent-syntax module.
*** The python-fluent module.
** L20n is deprecated.
** Post-1.0 plan (end of 2017 and 2018) has been proposed.

=== Adrian ===

* [Translate.Next] Rewrite Translate into a Single Page Application
** ''Key Result: All of Pontoon’s translate view UI is re-written using React and is internationalized using fluent-react.''
** All features from current Translate application are ported to the new one
** 100% of the code uses React and other efficient front-end technologies
** All new code is fully localizable
** All new code is unit tested and has decent code coverage (> 80%)

* [Translate.Next] Improve the review process
** ''Key Result: Translators and managers can give translation feedback when testing and reviewing translations within Pontoon.''
** Design a better review process for translations
*** Design 2 ideas for an improved review process
*** Organize a local community meetup to test, improve, and choose the better option
*** Define scope for the implementation of the chosen option

* Non-Workday goals
** Mentor a GSoC student
** Implement the review process that has been chosen with the community
** Organize testing of the new review process with the larger community

=== Theo (optional) ===

L10n:Goals/H1-2019

2019-03-12T06:08:51Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==

==Roundtable==

=== Axel ===

=== Delphine ===

=== Flod ===

Reduce the amount of work required by Fluent reviews for mozilla-central:
* [] Identify tasks that can be automated via linting and tests.
* [] Create documentation for reviewers describing common problems and expectations.
* [] Drop the mandatory review for FTL files by end of H1.

Ensure team’s productivity and success in Q2 while standing in as a manager.:
* [] Ensure that at least 70% of the team OKR defined for Q2 are completed.
* [] (Personal growth) Use feedback and experience to identify areas where I need to invest for personal growth, evaluate becoming a manager as a potential career path, and use this information to define an Individual Development Plan in H2.

=== Jeff ===

=== Matjaž ===

=== Peiying ===

=== Stas ===

=== Adrian ===

=== Theo (optional) ===

L10n:Bugogram

2019-02-26T16:14:40Z

Flod: /* webparts */

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

== shipping ==
; short_desc : [%(loc)s] Firefox release tracker %(language)s
; alias : fx-l10n-%(loc)s
; blocked : fx-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,pmo@mozilla.com
This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibility to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds Mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

== bugzilla ==
; short_desc : Create l10n Bugzilla component for %(language)s (%(loc)s), add value for Locale field
; product : bugzilla.mozilla.org
; component : Administration
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com
We need a Bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custom field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations
Component: %(loc)s / %(language)s
Description: %(language)s Localization (...)

Assignee: nobody
QA Contact: Empty
Triage owner: :flod (francesco.lodolo@gmail.com)

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description?

Once we have the description, this bug will be fixed by Mozilla staff.

== ldap ==
; short_desc : Create LDAP account for %(name)s <%(bugmail)s>
; product : Infrastructure & Operations
; component : Infrastructure: LDAP
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com

Please create an LDAP account for %(name)s. We'll want a password, and be part tableau_users group.

This bug is independent of repository access requests.

== hg_repo ==
; short_desc : l10n-central Mercurial repository for '%(loc)s'
; product : Developer Services
; component : Mercurial: hg.mozilla.org
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
Please create a new hg repository for Firefox localization. The repository should be:

- l10n-central/%(loc)s/

with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s

Please make sure that dxr is updated to pick up the new repository.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== build ==
; short_desc : Add '%(loc)s' to Firefox Nightly build
; product : Firefox Build System
; component : General
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
We need to add '%(loc)s' to browser/locales/all-locales on mozilla-central.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== product-details ==
; short_desc : Add '%(loc)s' to product-details
; product : Release Engineering
; component : Ship It
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com,francesco.lodolo@gmail.com
We need to add '%(loc)s' to the Firefox Nightly l10n builds on mozilla.org:
* Locale needs to be added to the list of supported Nightly locales.
* If missing, add an entry in languages.json with both the English and localized name for this locale.

P.S. To be clear to the localization team, this bug is handled by Mozilla staff.

== Webservices ==
We'll have a separate bug for each web service area, namely
* search
* protocol handlers
* rss readers

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives:
Google, Bing, Amazon, DuckDuckGo, Twitter, Wikipedia, eBay

Adding brand new search engines, that not yet ship in any other language, needs approval from Business Development and requires more time to get authorization and assets from the provider. To avoid blocking the initial set up, this type of requests should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.

The %(language)s team and flod will be driving this bug to completion.

=== protocol ===
; short_desc : [%(loc)s] Firefox protocol handler setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

== websetup ==
; short_desc : [%(loc)s] bootstrap %(language)s on GitHub
; product : Mozilla Localizations
; component : Infrastructure
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com
; blocked : fx-l10n-%(loc)s

flod, Peiying, please add web pages to this locale's folder on mozilla.org.

Please notify in the actual translation bug when this is done.

== webparts ==
; short_desc : [%(loc)s] Firefox initial web parts for %(language)s
; product : www.mozilla.org
; component : L10N
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages.

flod or Peying will follow up here when the initial setup work is done. After that, files will be added to GitHub, and will be available for localization in Pontoon at https://pontoon.mozilla.org/%(loc)s/mozillaorg/

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

== sumo ==
; short_desc : [%(loc)s] Enable %(language)s localization on SUMO
; product : support.mozilla.org
; component : Localization
; cc : %(bugmail)s
; blocked : fx-l10n-%(loc)s
We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

== done ==
That's all folks.

L10n:Bugogram

2019-02-26T16:11:16Z

Flod: Remove references to webdashboard

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

== shipping ==
; short_desc : [%(loc)s] Firefox release tracker %(language)s
; alias : fx-l10n-%(loc)s
; blocked : fx-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,pmo@mozilla.com
This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibility to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds Mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

== bugzilla ==
; short_desc : Create l10n Bugzilla component for %(language)s (%(loc)s), add value for Locale field
; product : bugzilla.mozilla.org
; component : Administration
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com
We need a Bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custom field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations
Component: %(loc)s / %(language)s
Description: %(language)s Localization (...)

Assignee: nobody
QA Contact: Empty
Triage owner: :flod (francesco.lodolo@gmail.com)

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description?

Once we have the description, this bug will be fixed by Mozilla staff.

== ldap ==
; short_desc : Create LDAP account for %(name)s <%(bugmail)s>
; product : Infrastructure & Operations
; component : Infrastructure: LDAP
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com

Please create an LDAP account for %(name)s. We'll want a password, and be part tableau_users group.

This bug is independent of repository access requests.

== hg_repo ==
; short_desc : l10n-central Mercurial repository for '%(loc)s'
; product : Developer Services
; component : Mercurial: hg.mozilla.org
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
Please create a new hg repository for Firefox localization. The repository should be:

- l10n-central/%(loc)s/

with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s

Please make sure that dxr is updated to pick up the new repository.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== build ==
; short_desc : Add '%(loc)s' to Firefox Nightly build
; product : Firefox Build System
; component : General
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
We need to add '%(loc)s' to browser/locales/all-locales on mozilla-central.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== product-details ==
; short_desc : Add '%(loc)s' to product-details
; product : Release Engineering
; component : Ship It
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com,francesco.lodolo@gmail.com
We need to add '%(loc)s' to the Firefox Nightly l10n builds on mozilla.org:
* Locale needs to be added to the list of supported Nightly locales.
* If missing, add an entry in languages.json with both the English and localized name for this locale.

P.S. To be clear to the localization team, this bug is handled by Mozilla staff.

== Webservices ==
We'll have a separate bug for each web service area, namely
* search
* protocol handlers
* rss readers

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives:
Google, Bing, Amazon, DuckDuckGo, Twitter, Wikipedia, eBay

Adding brand new search engines, that not yet ship in any other language, needs approval from Business Development and requires more time to get authorization and assets from the provider. To avoid blocking the initial set up, this type of requests should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.

The %(language)s team and flod will be driving this bug to completion.

=== protocol ===
; short_desc : [%(loc)s] Firefox protocol handler setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

== websetup ==
; short_desc : [%(loc)s] bootstrap %(language)s on GitHub
; product : Mozilla Localizations
; component : Infrastructure
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com
; blocked : fx-l10n-%(loc)s

flod, Peiying, please add web pages to this locale's folder on mozilla.org.

Please notify in the actual translation bug when this is done.

== webparts ==
; short_desc : [%(loc)s] Firefox initial web parts for %(language)s
; product : www.mozilla.org
; component : L10N
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages. There's a set of pages that are essential to having a successful Firefox localization and promotion, and those depend on the files listed below.

flod or Peying will follow up here when the initial setup work is done. After that, you'll find the files to localize in GitHub.

The repository you want to work with is located at https://github.com/mozilla-l10n/www.mozilla.org/tree/master/%(loc)s/

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

== sumo ==
; short_desc : [%(loc)s] Enable %(language)s localization on SUMO
; product : support.mozilla.org
; component : Localization
; cc : %(bugmail)s
; blocked : fx-l10n-%(loc)s
We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

== done ==
That's all folks.

L10n:Meetings/Paris Pontoon Sprint

2018-12-11T07:17:05Z

Flod: /* Accessing the Mozilla Paris office */

[[Category:L10n meetings|{{SUBPAGENAME}}]]

==Basic Info==
;Where:
Mozilla Paris Office

16bis Boulevard Montmartre

75009 Paris, France

==Accessing the Mozilla Paris office==
* https://wiki.mozilla.org/Paris has some general information - please pay particular attention to the notes on the wiki about how to open doors to exit the office
* On both Saturday and Sunday we will have someone who will coordinate letting you in to the office entrance.

Google maps: https://goo.gl/maps/Nv7dTQbebWz
;When: 15-16 December
;Arriving at hotel:
#Find the [https://www.parisaeroport.fr/en/passengers/access/paris-charles-de-gaulle/public-transport/roissybus/ Roissy Bus] outside of CDG. You can buy tickets from machines near the bus stop (buy also the return ticket directly, so you can get reimbursed). Note that Roissy Bus tickets can also be bought at metro stations automatic machines in the city, it doesn't have to be a Roissy Bus stop.
#Take the Roissy Bus from CDG to the Ópera stop.
#Walk from there to your hotel.

;Holiday Inn Opera:
30-32 Boulevard Poissonnière, 75009 Paris, France

+33 1 47 70 25 55

==Meals==
* Breakfast: breakfast is available at the hotel
** The office has coffee and tea so that should be available throughout the event.
* Lunches
** Catered to the office
* Dinners
** Dinner Saturday night at restaurant
** Dinner Sunday night at restaurant
* Snacks
** You are welcome to help yourself to snacks and drinks in the office, but please be aware we do get charged for each snack and drink consumed. Please only take what you will eat/drink, and make sure to discard any trash. The office is well equipped with recycling in the kitchen as well as in the first floor.

==Mozilla Staff Contacts==
*Delphine Lebedel - delphine at mozilla dot com, +1 650 898 3639
*Francesco Lodolo - flod at mozilla dot com
*Théo Chevalier - theo at mozillafoundation dot org, +44 7491 890 281
* Adrian
* Matjaz

==Agenda==
;Morning - 930AM
*
;Lunch -- 1230PM

;Afternoon
*

;Finish 5pm

;Dinner --

===Saturday 15 December===
;Morning -- 930AM
*

;Lunch -- 1230PM
;Afternoon
*
;Finish 5pm
;Dinner -- TBD

L10n:Bugogram

2018-11-15T13:41:39Z

Flod:

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

== shipping ==
; short_desc : [%(loc)s] Firefox release tracker %(language)s
; alias : fx-l10n-%(loc)s
; blocked : fx-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,pmo@mozilla.com
This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibility to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds Mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

== bugzilla ==
; short_desc : Create l10n Bugzilla component for %(language)s (%(loc)s), add value for Locale field
; product : bugzilla.mozilla.org
; component : Administration
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com
We need a Bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custom field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations
Component: %(loc)s / %(language)s
Description: %(language)s Localization (...)

Assignee: nobody
QA Contact: Empty
Triage owner: :flod (francesco.lodolo@gmail.com)

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description?

Once we have the description, this bug will be fixed by Mozilla staff.

== ldap ==
; short_desc : Create LDAP account for %(name)s <%(bugmail)s>
; product : Infrastructure & Operations
; component : Infrastructure: LDAP
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com

Please create an LDAP account for %(name)s. We'll want a password, and be part of the locale_peer and tableau_users groups.

This bug is independent of repository access requests.

== hg_repo ==
; short_desc : l10n-central Mercurial repository for '%(loc)s'
; product : Developer Services
; component : Mercurial: hg.mozilla.org
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
Please create a new hg repository for Firefox localization. The repository should be:

- l10n-central/%(loc)s/

with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s

Please make sure that dxr is updated to pick up the new repository.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== build ==
; short_desc : Add '%(loc)s' to Firefox Nightly build
; product : Firefox Build System
; component : General
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
We need to add '%(loc)s' to browser/locales/all-locales on mozilla-central.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== product-details ==
; short_desc : Add '%(loc)s' to product-details
; product : Release Engineering
; component : Ship It
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com,francesco.lodolo@gmail.com
We need to add '%(loc)s' to the Firefox Nightly l10n builds on mozilla.org:
* Locale needs to be added to the list of supported Nightly locales.
* If missing, add an entry in languages.json with both the English and localized name for this locale.

P.S. To be clear to the localization team, this bug is handled by Mozilla staff.

== Webservices ==
We'll have a separate bug for each web service area, namely
* search
* protocol handlers
* rss readers

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives:
Google, Bing, Amazon, DuckDuckGo, Twitter, Wikipedia, eBay

Adding brand new search engines, that not yet ship in any other language, needs approval from Business Development and requires more time to get authorization and assets from the provider. To avoid blocking the initial set up, this type of requests should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.

The %(language)s team and flod will be driving this bug to completion.

=== protocol ===
; short_desc : [%(loc)s] Firefox protocol handler setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

== websetup ==
; short_desc : [%(loc)s] bootstrap %(language)s on GitHub and the web dashboard
; product : Mozilla Localizations
; component : Infrastructure
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com
; blocked : fx-l10n-%(loc)s

flod, Peiying, please set up the webdashboard for %(language)s, and add web pages to this locale's folder on mozilla.org.

Please notify in the actual translation bug when this is done.

== webparts ==
; short_desc : [%(loc)s] Firefox initial web parts for %(language)s
; product : www.mozilla.org
; component : L10N
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages. There's a set of pages that are essential to having a successful Firefox localization and promotion, and those depend on the files listed below.

flod or Peying will follow up here when the initial setup work is done. After that, you'll find the files to localize in GitHub.

The repository you want to work with is located at https://github.com/mozilla-l10n/www.mozilla.org/tree/master/%(loc)s/

The status of web parts for your locale on GitHub can be checked at this URL (updated every 15 minutes)
http://l10n.mozilla-community.org/webdashboard/?locale=%(loc)s

Please start by translating files with higher priority according to the dashboard.

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

== sumo ==
; short_desc : [%(loc)s] Enable %(language)s localization on SUMO
; product : support.mozilla.org
; component : Localization
; cc : %(bugmail)s
; blocked : fx-l10n-%(loc)s
We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

== done ==
That's all folks.

L10n:Goals/H2-2018

2018-08-01T12:16:22Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==
Please ensure that individual goals (all or part) are contributing to our [https://docs.google.com/spreadsheets/d/1ZO4OfDZEA7zweUULaoxvmS8Vhyc1ZgXtl7v7pAIdoSg/edit#gid=0 2018 OKRs for localization]. Citing the OKR that your H2 goal contributes to in your goal section is preferred.
* Fluent in Gecko - '''Zibi''', Ax, F, S
* Multilingual Firefox - '''Flod''', Z, J, Ax
* Fluent 1.0 - '''Stas''', Z, Ax
* New brand translation policy - '''Peiying''', Z, F, D
* compare-locales in Pontoon - '''Matjaz'''
* Pontoon translate view in React/Fluent - '''Adrian'''
* Android strings.xml - '''Axel''', M, D

==Roundtable==

=== Axel ===
* '''Cross-channel for git and Android projects'''
** Supporting Android strings.xml
** Generate a single repository with ''all'' Android strings
*** Focus/Klar, Firefox for TV
*** Optional, TBC: Rocket
* '''Support for Strings.xml in compare-locales'''
** Supporting Android strings.xml
** tier0 and tier1, https://bugzilla.mozilla.org/buglist.cgi?bug_id=1472157%2C1473577%2C1465342%2C1472150%2C1466088%2C1465341%2C1465517%2C1466836%2C1472149%2C1465711
* Support for Android Components
** Supporting Android strings.xml
** Multiple strings.xml files against one cross-channel
** Multiple reference files for one localized file support in compare-locales

=== Delphine ===
* OKR: Android products can be rapidly bootstrapped and continuously localized.
** '''We need to bootstrap new localizations on mobile faster. We’re going to experiment with at least 2 possible methods for this, and evaluate which one is more effective. I'll create a comparison of how each method went, which one(s) can scale in which regions and in which situations'''
** '''Get at least 4 Indic locales ready to ship on Rocket for the initial India launch'''
** Co-create scope document for Pre-Translation feature

* OKR: Increase l10n community's organizational and procedural efficiency.
** Experiment with 2 methods, and with 2 communities, to reduce unreviewed suggestions, and then evaluate and create a report on how well each of them went.
** '''Organize design sprint to design a translation feedback solution'''

* Not WorkDay - Probably Q1 2019 stuff
** [Translate.Next] Spread the word and get people engaged in Adrian's A/B testing for an improved review process

=== Flod ===

===== Firefox Desktop =====

Supporting '''Multilingual Firefox''':
* [] Finalize first iteration of language switcher in preferences (copy, userflow, design), land it in Firefox 63/64 (M1).
* [] Define, start collecting telemetry data relevant for multilingual users (M1).
* [] Help designing, driving implemention and testing improvements of download page for mozilla.org (M2).
* [] Define scope and actionable items for next milestones (M3-M5).

Supporting '''Fluent in Gecko''':
* [] Support migrations to Fluent of existing parts of Gecko:
** Review and test all FTL patches for Firefox.
** Run migration on l10n repositories.
** Update and integrate documentation to cover FTL features and Pontoon UI updates.

No OKR:
* [] Start shipping updates to dot releases, pending further syntax issues with Fluent.

===== Other =====

Supporting '''Increase l10n community's organizational and procedural efficiency''':
* [] Design 2 prototypes for translation/review solution with Matjaz and Adrian, evaluate them in a community design sprint.

No OKR:
* [] Familiarize with CLDR Survey Tool.

=== Gandalf ===

* '''Enable full Firefox migration to Fluent'''
** Enable DTD->Fluent migration in all contexts
** Enable fluent-react in Firefox
** Enable properties->Fluent migration in all contexts
** Experiment with fluent-rs in Gecko
* '''Multilingual Firefox'''
** Support Flod with M1-5.
* '''Fluent 1.0'''
** Support Stas with Fluent 1.0 release.

=== Jeff ===
;Workday goals

'''Internal terminology management workflow will be streamlined.'''

Corresponding OKR: ''Establish consistent practice of managing Mozilla terminology for all products and brand/product names.''

This goal will be completed when:
* We define requirements for a terminology management solution.
* We evaluate at least 3 candidate solutions against our requirements.
* We make a selection and formulate/execute a migration plan for existing terminology data.
* We educate UX, SUMO, and others on using the solution and define an effective, streamlined pipeline for proposing, evaluating, and finalizing new terms.
* We create a product requirement document (PRD) for terminology management in Mozilla l10n toolchain to determine the investment and its return if we were to build our own solution.

'''L10n team is ready to scale localization for more mobile projects on faster timelines.'''

Corresponding OKR: ''Android products can be rapidly bootstrapped and continuously localized.''

This goal will be completed when:
* Existing technical pain points in mobile l10n projects have been identified and scoped.
* We can predict scale challenges in human overhead and technical inefficiencies.
* We have a plan to account for scale challenges that is approved by leadership.

=== Matjaž ===
* Make localizer-critical data available in Pontoon
** Implement support for errors and warnings in dashboards and filters
** Implement file-level priorities
** Implement file-level deadlines
* Improve path to first contribution to localization at Mozilla
** Implement new Pontoon homepage (mentor a GSoC student)
** Implement new main menu for the translate view
** Implement the ability to request a new locale through Pontoon
* Design two translation review & feedback solutions
* Become comfortable with using Translate.next technologies
* Add support for XML file format used in Android

=== Peiying ===
* [OKR]Brand name localization guideline, documentation and implementation
** Make recommendations based on Firefox desktop user base to prioritize top 3 language and country for potential branding trademark registration(s).
** Create documentation for trademarked brand names (existing and newly approved) on implementing them into products and projects.
** Incorporate brand names (trademarked, declensed, and/or transliterated) into Mozilla terminology system and for all products. 
* [OKR] Modernize localization technology and process for mozilla.org
** Requirements doc for mozilla.org finalized among l10n, bedrock, and marketing.
** Redefine minimum pages/content required for a new locale: must have, good to have and optional.
* L10n Vendor Evaluation Selection Process
** Standardize the test content for easy comparison.
** Create matrix template to measure each vendor going through evaluation process, and establish a scoring system with the intent to share matrix scores and the strengths of each vendor on file.
** Expand vendor list by two more to broaden coverage of localization need.

=== Stas ===

* '''Release Fluent 1.0'''
** Fluent Syntax 1.0 Spec is published.
*** The reference parser is used to validate the spec.
*** The Syntax Guide is up-to-date.
** Implementations have been updated to Syntax 1.0.
*** The runtime fluent module.
*** The tooling fluent-syntax module.
*** The python-fluent module.
** L20n is deprecated.
** Post-1.0 plan (end of 2017 and 2018) has been proposed.

=== Adrian ===

* [Translate.Next] Rewrite Translate into a Single Page Application
** ''Key Result: All of Pontoon’s translate view UI is re-written using React and is internationalized using fluent-react.''
** All features from current Translate application are ported to the new one
** 100% of the code uses React and other efficient front-end technologies
** All new code is fully localizable
** All new code is unit tested and has decent code coverage (> 80%)

* [Translate.Next] Improve the review process
** ''Key Result: Translators and managers can give translation feedback when testing and reviewing translations within Pontoon.''
** Design a better review process for translations
*** Design 2 ideas for an improved review process
*** Organize a local community meetup to test, improve, and choose the better option
*** Define scope for the implementation of the chosen option

* Non-Workday goals
** Mentor a GSoC student
** Implement the review process that has been chosen with the community
** Organize testing of the new review process with the larger community

=== Theo (optional) ===

L10n:Goals/H2-2018

2018-07-23T15:02:34Z

Flod: /* Other */

[[Category:L10n goals]]
==Team Goals==
Please ensure that individual goals (all or part) are contributing to our [https://docs.google.com/spreadsheets/d/1ZO4OfDZEA7zweUULaoxvmS8Vhyc1ZgXtl7v7pAIdoSg/edit#gid=0 2018 OKRs for localization]. Citing the OKR that your H2 goal contributes to in your goal section is preferred.
* Fluent in Gecko - '''Zibi''', Ax, F, S
* Multilingual Firefox - '''Flod''', Z, J, Ax
* Fluent 1.0 - '''Stas''', Z, Ax
* New brand translation policy - '''Peiying''', Z, F, D
* compare-locales in Pontoon - '''Matjaz'''
* Pontoon translate view in React/Fluent - '''Adrian'''
* Android strings.xml - '''Axel''', M, D

==Roundtable==

=== Axel ===
* '''Cross-channel for git and Android projects'''
** Supporting Android strings.xml
** Generate a single repository with ''all'' Android strings
*** Focus/Klar, Firefox for TV
*** Optional, TBC: Rocket
* '''Support for Strings.xml in compare-locales'''
** Supporting Android strings.xml
** tier0 and tier1, https://bugzilla.mozilla.org/buglist.cgi?bug_id=1472157%2C1473577%2C1465342%2C1472150%2C1466088%2C1465341%2C1465517%2C1466836%2C1472149%2C1465711
* Support for Android Components
** Supporting Android strings.xml
** Multiple strings.xml files against one cross-channel
** Multiple reference files for one localized file support in compare-locales

=== Delphine ===
* OKR: Android products can be rapidly bootstrapped and continuously localized.
** '''We need to bootstrap new localizations on mobile faster. We’re going to experiment with at least 2 possible methods for this, and evaluate which one is more effective. I'll create a comparison of how each method went, which one(s) can scale in which regions and in which situations'''
** '''Get at least 4 Indic locales ready to ship on Rocket for the initial India launch'''
** Co-create scope document for Pre-Translation feature

* OKR: Increase l10n community's organizational and procedural efficiency.
** Experiment with 2 methods, and with 2 communities, to reduce unreviewed suggestions, and then evaluate and create a report on how well each of them went.
** '''Organize design sprint to design a translation feedback solution'''

* Not WorkDay - Probably Q1 2019 stuff
** [Translate.Next] Spread the word and get people engaged in Adrian's A/B testing for an improved review process

=== Flod ===

===== Firefox Desktop =====

Supporting '''Multilingual Firefox''':
* [] Finalize first iteration of language switcher in preferences (copy, userflow, design), land it in Firefox 63/64 (M1).
* [] Define, start collecting telemetry data relevant for multilingual users (M1).
* [] Help designing, driving implemention and testing improvements of download page for mozilla.org (M2).
* [] Define scope and actionable items for next milestones (M3-M5).

Supporting '''Fluent in Gecko''':
* [] Support migrations to Fluent of existing parts of Gecko:
** Review and test all FTL patches for Firefox.
** Run migration on l10n repositories.
** Update and integrate documentation to cover FTL features and Pontoon UI updates.

No OKR:
* [] Start shipping updates to dot releases, pending further syntax issues with Fluent.

===== Other =====

Supporting '''Increase l10n community's organizational and procedural efficiency''':
* [] Help designing 2 prototypes for a translation feedback/review solution to evaluate in a design sprint with community members.
* [] (to be reworded) Contribute to Translate.Next in Pontoon (feedback, testing, documentation).

No OKR:
* [] Familiarize with CLDR Survey Tool.

=== Gandalf ===

* '''Enable full Firefox migration to Fluent'''
** Enable DTD->Fluent migration in all contexts
** Enable fluent-react in Firefox
** Enable properties->Fluent migration in all contexts
** Experiment with fluent-rs in Gecko
* '''Multilingual Firefox'''
** Support Flod with M1-5.
* '''Fluent 1.0'''
** Support Stas with Fluent 1.0 release.

=== Jeff ===
;Workday goals

'''Internal terminology management workflow will be streamlined.'''

Corresponding OKR: ''Establish consistent practice of managing Mozilla terminology for all products and brand/product names.''

This goal will be completed when:
* We define requirements for a terminology management solution.
* We evaluate at least 3 candidate solutions against our requirements.
* We make a selection and formulate/execute a migration plan for existing terminology data.
* We educate UX, SUMO, and others on using the solution and define an effective, streamlined pipeline for proposing, evaluating, and finalizing new terms.
* We create a product requirement document (PRD) for terminology management in Mozilla l10n toolchain to determine the investment and its return if we were to build our own solution.

'''L10n team is ready to scale localization for more mobile projects on faster timelines.'''

Corresponding OKR: ''Android products can be rapidly bootstrapped and continuously localized.''

This goal will be completed when:
* Existing technical pain points in mobile l10n projects have been identified and scoped.
* We can predict scale challenges in human overhead and technical inefficiencies.
* We have a plan to account for scale challenges that is approved by leadership.

=== Matjaž ===
* Make localizer-critical data available in Pontoon
** Implement support for errors and warnings in dashboards and filters
** Implement file-level priorities
** Implement file-level deadlines
* Improve path to first contribution to localization at Mozilla
** Implement new Pontoon homepage (mentor a GSoC student)
** Implement new main menu for the translate view
** Implement the ability to request a new locale through Pontoon
* Design two translation review & feedback solutions
* Become comfortable with using Translate.next technologies
* Add support for XML file format used in Android

=== Peiying ===
* [OKR]Brand name localization guideline, documentation and implementation
** Make recommendations based on Firefox desktop user base to prioritize top 3 language and country for potential branding trademark registration(s).
** Create documentation for trademarked brand names (existing and newly approved) on implementing them into products and projects.
** Incorporate brand names (trademarked, declensed, and/or transliterated) into Mozilla terminology system and for all products. 
* [OKR] Modernize localization technology and process for mozilla.org
** Requirements doc for mozilla.org finalized among l10n, bedrock, and marketing.
** Redefine minimum pages/content required for a new locale: must have, good to have and optional.
* L10n Vendor Evaluation Selection Process
** Standardize the test content for easy comparison.
** Create matrix template to measure each vendor going through evaluation process, and establish a scoring system with the intent to share matrix scores and the strengths of each vendor on file.
** Expand vendor list by two more to broaden coverage of localization need.

=== Stas ===

* '''Release Fluent 1.0'''
** Fluent Syntax 1.0 Spec is published.
*** The reference parser is used to validate the spec.
*** The Syntax Guide is up-to-date.
** Implementations have been updated to Syntax 1.0.
*** The runtime fluent module.
*** The tooling fluent-syntax module.
*** The python-fluent module.
** L20n is deprecated.
** Post-1.0 plan (end of 2017 and 2018) has been proposed.

=== Adrian ===

* [Translate.Next] Rewrite Translate into a Single Page Application
** ''Key Result: All of Pontoon’s translate view UI is re-written using React and is internationalized using fluent-react.''
** All features from current Translate application are ported to the new one
** 100% of the code uses React and other efficient front-end technologies
** All new code is fully localizable
** All new code is unit tested and has decent code coverage (> 80%)

* [Translate.Next] Improve the review process
** ''Key Result: Translators and managers can give translation feedback when testing and reviewing translations within Pontoon.''
** Design a better review process for translations
*** Design 2 ideas for an improved review process
*** Organize a local community meetup to test, improve, and choose the better option
*** Define scope for the implementation of the chosen option

* Non-Workday goals
** Mentor a GSoC student
** Implement the review process that has been chosen with the community
** Organize testing of the new review process with the larger community

=== Theo (optional) ===

L10n:Goals/H2-2018

2018-07-19T10:28:33Z

Flod: /* Other */

[[Category:L10n goals]]
==Team Goals==
Please ensure that individual goals (all or part) are contributing to our [https://docs.google.com/spreadsheets/d/1ZO4OfDZEA7zweUULaoxvmS8Vhyc1ZgXtl7v7pAIdoSg/edit#gid=0 2018 OKRs for localization]. Citing the OKR that your H2 goal contributes to in your goal section is preferred.
* Fluent in Gecko - '''Zibi''', Ax, F, S
* Multilingual Firefox - '''Flod''', Z, J, Ax
* Fluent 1.0 - '''Stas''', Z, Ax
* New brand translation policy - '''Peiying''', Z, F, D
* compare-locales in Pontoon - '''Matjaz'''
* Pontoon translate view in React/Fluent - '''Adrian'''
* Android strings.xml - '''Axel''', M, D

==Roundtable==

=== Axel ===
* '''Cross-channel for git and Android projects'''
** Supporting Android strings.xml
** Generate a single repository with ''all'' Android strings
*** Focus/Klar, Firefox for TV
*** Optional, TBC: Rocket
* '''Support for Strings.xml in compare-locales'''
** Supporting Android strings.xml
** tier0 and tier1, https://bugzilla.mozilla.org/buglist.cgi?bug_id=1472157%2C1473577%2C1465342%2C1472150%2C1466088%2C1465341%2C1465517%2C1466836%2C1472149%2C1465711
* Support for Android Components
** Supporting Android strings.xml
** Multiple strings.xml files against one cross-channel
** Multiple reference files for one localized file support in compare-locales

=== Delphine ===
* OKR: Android products can be rapidly bootstrapped and continuously localized.
** '''We need to bootstrap new localizations on mobile faster. We’re going to experiment with at least 2 possible methods for this, and evaluate which one is more effective. I'll create a comparison of how each method went, which one(s) can scale in which regions and in which situations'''
** '''Get at least 4 Indic locales ready to ship on Rocket for the initial India launch'''
** Co-create scope document for Pre-Translation feature

* OKR: Increase l10n community's organizational and procedural efficiency.
** Experiment with 2 methods, and with 2 communities, to reduce unreviewed suggestions, and then evaluate and create a report on how well each of them went.
** '''Organize design sprint to design a translation feedback solution'''

* Not WorkDay - Probably Q1 2019 stuff
** [Translate.Next] Spread the word and get people engaged in Adrian's A/B testing for an improved review process

=== Flod ===

===== Firefox Desktop =====

Supporting '''Multilingual Firefox''':
* [] Finalize first iteration of language switcher in preferences (copy, userflow, design), land it in Firefox 63/64 (M1).
* [] Define, start collecting telemetry data relevant for multilingual users (M1).
* [] Help designing, driving implemention and testing improvements of download page for mozilla.org (M2).
* [] Define scope and actionable items for next milestones (M3-M5).

Supporting '''Fluent in Gecko''':
* [] Support migrations to Fluent of existing parts of Gecko:
** Review and test all FTL patches for Firefox.
** Run migration on l10n repositories.
** Update and integrate documentation to cover FTL features and Pontoon UI updates.

No OKR:
* [] Start shipping updates to dot releases, pending further syntax issues with Fluent.

===== Other =====

Supporting '''Increase l10n community's organizational and procedural efficiency''':
* [] Help designing 2 propotypes for a translation feedback/review solution to evaluate in a design sprint with community members.
* [] (to be reworded) Contribute to Translate.Next in Pontoon (feedback, testing, documentation).

No OKR:
* [] Familiarize with CLDR Survey Tool.

=== Gandalf ===

* '''Enable full Firefox migration to Fluent'''
** Enable DTD->Fluent migration in all contexts
** Enable fluent-react in Firefox
** Enable properties->Fluent migration in all contexts
** Experiment with fluent-rs in Gecko
* '''Multilingual Firefox'''
** Support Flod with M1-5.
* '''Fluent 1.0'''
** Support Stas with Fluent 1.0 release.

=== Jeff ===
;Workday goals

'''Internal terminology management workflow will be streamlined.'''

Corresponding OKR: ''Establish consistent practice of managing Mozilla terminology for all products and brand/product names.''

This goal will be completed when:
* We define requirements for a terminology management solution.
* We evaluate at least 3 candidate solutions against our requirements.
* We make a selection and formulate/execute a migration plan for existing terminology data.
* We educate UX, SUMO, and others on using the solution and define an effective, streamlined pipeline for proposing, evaluating, and finalizing new terms.
* We create a product requirement document (PRD) for terminology management in Mozilla l10n toolchain to determine the investment and its return if we were to build our own solution.

'''L10n team is ready to scale localization for more mobile projects on faster timelines.'''

Corresponding OKR: ''Android products can be rapidly bootstrapped and continuously localized.''

This goal will be completed when:
* Existing technical pain points in mobile l10n projects have been identified and scoped.
* We can predict scale challenges in human overhead and technical inefficiencies.
* We have a plan to account for scale challenges that is approved by leadership.

=== Matjaž ===
* Make localizer-critical data available in Pontoon
** Implement support for errors and warnings in dashboards and filters
** Implement file-level priorities
** Implement file-level deadlines
* Improve path to first contribution to localization at Mozilla
** Implement new Pontoon homepage (mentor a GSoC student)
** Implement new main menu for the translate view
** Implement the ability to request a new locale through Pontoon
* Design two translation review & feedback solutions
* Become comfortable with using Translate.next technologies
* Add support for XML file format used in Android

=== Peiying ===

=== Stas ===

* '''Release Fluent 1.0'''
** Fluent Syntax 1.0 Spec is published.
*** The reference parser is used to validate the spec.
*** The Syntax Guide is up-to-date.
** Implementations have been updated to Syntax 1.0.
*** The runtime fluent module.
*** The tooling fluent-syntax module.
*** The python-fluent module.
** L20n is deprecated.
** Post-1.0 plan (end of 2017 and 2018) has been proposed.

=== Adrian ===

* [Translate.Next] Rewrite Translate into a Single Page Application
** ''Key Result: All of Pontoon’s translate view UI is re-written using React and is internationalized using fluent-react.''
** All features from current Translate application are ported to the new one
** 100% of the code uses React and other efficient front-end technologies
** All new code is fully localizable
** All new code is unit tested and has decent code coverage (> 80%)

* [Translate.Next] Improve the review process
** ''Key Result: Translators and managers can give translation feedback when testing and reviewing translations within Pontoon.''
** Design a better review process for translations
*** Design 2 ideas for an improved review process
*** Organize a local community meetup to test, improve, and choose the better option
*** Define scope for the implementation of the chosen option

* Non-Workday goals
** Mentor a GSoC student
** Implement the review process that has been chosen with the community
** Organize testing of the new review process with the larger community

=== Theo (optional) ===

L10n:Goals/H2-2018

2018-07-19T10:28:13Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==
Please ensure that individual goals (all or part) are contributing to our [https://docs.google.com/spreadsheets/d/1ZO4OfDZEA7zweUULaoxvmS8Vhyc1ZgXtl7v7pAIdoSg/edit#gid=0 2018 OKRs for localization]. Citing the OKR that your H2 goal contributes to in your goal section is preferred.
* Fluent in Gecko - '''Zibi''', Ax, F, S
* Multilingual Firefox - '''Flod''', Z, J, Ax
* Fluent 1.0 - '''Stas''', Z, Ax
* New brand translation policy - '''Peiying''', Z, F, D
* compare-locales in Pontoon - '''Matjaz'''
* Pontoon translate view in React/Fluent - '''Adrian'''
* Android strings.xml - '''Axel''', M, D

==Roundtable==

=== Axel ===
* '''Cross-channel for git and Android projects'''
** Supporting Android strings.xml
** Generate a single repository with ''all'' Android strings
*** Focus/Klar, Firefox for TV
*** Optional, TBC: Rocket
* '''Support for Strings.xml in compare-locales'''
** Supporting Android strings.xml
** tier0 and tier1, https://bugzilla.mozilla.org/buglist.cgi?bug_id=1472157%2C1473577%2C1465342%2C1472150%2C1466088%2C1465341%2C1465517%2C1466836%2C1472149%2C1465711
* Support for Android Components
** Supporting Android strings.xml
** Multiple strings.xml files against one cross-channel
** Multiple reference files for one localized file support in compare-locales

=== Delphine ===
* OKR: Android products can be rapidly bootstrapped and continuously localized.
** '''We need to bootstrap new localizations on mobile faster. We’re going to experiment with at least 2 possible methods for this, and evaluate which one is more effective. I'll create a comparison of how each method went, which one(s) can scale in which regions and in which situations'''
** '''Get at least 4 Indic locales ready to ship on Rocket for the initial India launch'''
** Co-create scope document for Pre-Translation feature

* OKR: Increase l10n community's organizational and procedural efficiency.
** Experiment with 2 methods, and with 2 communities, to reduce unreviewed suggestions, and then evaluate and create a report on how well each of them went.
** '''Organize design sprint to design a translation feedback solution'''

* Not WorkDay - Probably Q1 2019 stuff
** [Translate.Next] Spread the word and get people engaged in Adrian's A/B testing for an improved review process

=== Flod ===

===== Firefox Desktop =====

Supporting '''Multilingual Firefox''':
* [] Finalize first iteration of language switcher in preferences (copy, userflow, design), land it in Firefox 63/64 (M1).
* [] Define, start collecting telemetry data relevant for multilingual users (M1).
* [] Help designing, driving implemention and testing improvements of download page for mozilla.org (M2).
* [] Define scope and actionable items for next milestones (M3-M5).

Supporting '''Fluent in Gecko''':
* [] Support migrations to Fluent of existing parts of Gecko:
** Review and test all FTL patches for Firefox.
** Run migration on l10n repositories.
** Update and integrate documentation to cover FTL features and Pontoon UI updates.

No OKR:
* [] Start shipping updates to dot releases, pending further syntax issues with Fluent.

===== Other =====

Supporting '''Increase l10n community's organizational and procedural efficiency''':
* [] Help designing 2 propotypes for a translation feedback/review solution to evaluate in a design sprint with community members.
* [] (to be reworder) Contribute to Translate.Next in Pontoon (feedback, testing, documentation).

No OKR:
* [] Familiarize with CLDR Survey Tool.

=== Gandalf ===

* '''Enable full Firefox migration to Fluent'''
** Enable DTD->Fluent migration in all contexts
** Enable fluent-react in Firefox
** Enable properties->Fluent migration in all contexts
** Experiment with fluent-rs in Gecko
* '''Multilingual Firefox'''
** Support Flod with M1-5.
* '''Fluent 1.0'''
** Support Stas with Fluent 1.0 release.

=== Jeff ===
;Workday goals

'''Internal terminology management workflow will be streamlined.'''

Corresponding OKR: ''Establish consistent practice of managing Mozilla terminology for all products and brand/product names.''

This goal will be completed when:
* We define requirements for a terminology management solution.
* We evaluate at least 3 candidate solutions against our requirements.
* We make a selection and formulate/execute a migration plan for existing terminology data.
* We educate UX, SUMO, and others on using the solution and define an effective, streamlined pipeline for proposing, evaluating, and finalizing new terms.
* We create a product requirement document (PRD) for terminology management in Mozilla l10n toolchain to determine the investment and its return if we were to build our own solution.

'''L10n team is ready to scale localization for more mobile projects on faster timelines.'''

Corresponding OKR: ''Android products can be rapidly bootstrapped and continuously localized.''

This goal will be completed when:
* Existing technical pain points in mobile l10n projects have been identified and scoped.
* We can predict scale challenges in human overhead and technical inefficiencies.
* We have a plan to account for scale challenges that is approved by leadership.

=== Matjaž ===
* Make localizer-critical data available in Pontoon
** Implement support for errors and warnings in dashboards and filters
** Implement file-level priorities
** Implement file-level deadlines
* Improve path to first contribution to localization at Mozilla
** Implement new Pontoon homepage (mentor a GSoC student)
** Implement new main menu for the translate view
** Implement the ability to request a new locale through Pontoon
* Design two translation review & feedback solutions
* Become comfortable with using Translate.next technologies
* Add support for XML file format used in Android

=== Peiying ===

=== Stas ===

* '''Release Fluent 1.0'''
** Fluent Syntax 1.0 Spec is published.
*** The reference parser is used to validate the spec.
*** The Syntax Guide is up-to-date.
** Implementations have been updated to Syntax 1.0.
*** The runtime fluent module.
*** The tooling fluent-syntax module.
*** The python-fluent module.
** L20n is deprecated.
** Post-1.0 plan (end of 2017 and 2018) has been proposed.

=== Adrian ===

* [Translate.Next] Rewrite Translate into a Single Page Application
** ''Key Result: All of Pontoon’s translate view UI is re-written using React and is internationalized using fluent-react.''
** All features from current Translate application are ported to the new one
** 100% of the code uses React and other efficient front-end technologies
** All new code is fully localizable
** All new code is unit tested and has decent code coverage (> 80%)

* [Translate.Next] Improve the review process
** ''Key Result: Translators and managers can give translation feedback when testing and reviewing translations within Pontoon.''
** Design a better review process for translations
*** Design 2 ideas for an improved review process
*** Organize a local community meetup to test, improve, and choose the better option
*** Define scope for the implementation of the chosen option

* Non-Workday goals
** Mentor a GSoC student
** Implement the review process that has been chosen with the community
** Organize testing of the new review process with the larger community

=== Theo (optional) ===

L10n:Goals/H2-2018

2018-07-18T13:27:41Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==
Please ensure that individual goals (all or part) are contributing to our [https://docs.google.com/spreadsheets/d/1ZO4OfDZEA7zweUULaoxvmS8Vhyc1ZgXtl7v7pAIdoSg/edit#gid=0 2018 OKRs for localization]. Citing the OKR that your H2 goal contributes to in your goal section is preferred.
* Fluent in Gecko - '''Zibi''', Ax, F, S
* Multilingual Firefox - '''Flod''', Z, J, Ax
* Fluent 1.0 - '''Stas''', Z, Ax
* New brand translation policy - '''Peiying''', Z, F, D
* compare-locales in Pontoon - '''Matjaz'''
* Pontoon translate view in React/Fluent - '''Adrian'''
* Android strings.xml - '''Axel''', M, D

==Roundtable==

=== Axel ===
* '''Cross-channel for git and Android projects'''
** Supporting Android strings.xml
** Generate a single repository with ''all'' Android strings
*** Focus/Klar, Firefox for TV
*** Optional, TBC: Rocket
* '''Support for Strings.xml in compare-locales'''
** Supporting Android strings.xml
** tier0 and tier1, https://bugzilla.mozilla.org/buglist.cgi?bug_id=1472157%2C1473577%2C1465342%2C1472150%2C1466088%2C1465341%2C1465517%2C1466836%2C1472149%2C1465711
* Support for Android Components
** Supporting Android strings.xml
** Multiple strings.xml files against one cross-channel
** Multiple reference files for one localized file support in compare-locales

=== Delphine ===
* OKR: Android products can be rapidly bootstrapped and continuously localized.
** '''We need to bootstrap new localizations on mobile faster. We’re going to experiment with at least 2 possible methods for this, and evaluate which one is more effective. I'll create a comparison of how each method went, which one(s) can scale in which regions and in which situations'''
** '''Get at least 4 Indic locales ready to ship on Rocket for the initial India launch'''
** Co-create scope document for Pre-Translation feature

* OKR: Increase l10n community's organizational and procedural efficiency.
** Experiment with 2 methods, and with 2 communities, to reduce unreviewed suggestions, and then evaluate and create a report on how well each of them went.
** '''Organize design sprint to design a translation feedback solution'''

* Not WorkDay - Probably Q1 2019 stuff
** [Translate.Next] Spread the word and get people engaged in Adrian's A/B testing for an improved review process

=== Flod ===

===== Firefox Desktop =====

Supporting '''Multilingual Firefox''':
* [] Finalize first iteration of language switcher in preferences (copy, userflow, design), land it in Firefox 63/64 (M1).
* [] Define, start collecting telemetry data relevant for multilingual users (M1).
* [] Help designing, driving implemention and testing improvements of download page for mozilla.org (M2).
* [] Define scope and actionable items for next milestones (M3-M5).

Supporting '''Fluent in Gecko''':
* [] Support migrations to Fluent of existing parts of Gecko:
** Review and test all FTL patches for Firefox.
** Run migration on l10n repositories.
** Update and integrate documentation to cover FTL features and Pontoon UI updates.

No OKR:
* [] Start shipping updates to dot releases, pending further syntax issues with Fluent.

===== Other =====

Supporting '''Increase l10n community's organizational and procedural efficiency''':
* [] Contribute to discussion about Translation feedback solution in Pontoon.
* [] Contribute to Translate.Next in Pontoon (feedback, testing, documentation).

No OKR:
* [] Familiarize with CLDR Survey Tool.

=== Gandalf ===

* '''Enable full Firefox migration to Fluent'''
** Enable DTD->Fluent migration in all contexts
** Enable fluent-react in Firefox
** Enable properties->Fluent migration in all contexts
** Experiment with fluent-rs in Gecko
* '''Multilingual Firefox'''
** Support Flod with M1-5.
* '''Fluent 1.0'''
** Support Stas with Fluent 1.0 release.

=== Jeff ===
;Workday goals

'''Internal terminology management workflow will be streamlined.'''

Corresponding OKR: ''Establish consistent practice of managing Mozilla terminology for all products and brand/product names.''

This goal will be completed when:
* We define requirements for a terminology management solution.
* We evaluate at least 3 candidate solutions against our requirements.
* We make a selection and formulate/execute a migration plan for existing terminology data.
* We educate UX, SUMO, and others on using the solution and define an effective, streamlined pipeline for proposing, evaluating, and finalizing new terms.
* We create a product requirement document (PRD) for terminology management in Mozilla l10n toolchain to determine the investment and its return if we were to build our own solution.

'''L10n team is ready to scale localization for more mobile projects on faster timelines.'''

Corresponding OKR: ''Android products can be rapidly bootstrapped and continuously localized.''

This goal will be completed when:
* Existing technical pain points in mobile l10n projects have been identified and scoped.
* We can predict scale challenges in human overhead and technical inefficiencies.
* We have a plan to account for scale challenges that is approved by leadership.

=== Matjaž ===
* Make localizer-critical data available in Pontoon
** Implement support for errors and warnings in dashboards and filters
** Implement file-level priorities
** Implement file-level deadlines
* Improve path to first contribution to localization at Mozilla
** Implement new Pontoon homepage (mentor a GSoC student)
** Implement new main menu for the translate view
** Implement the ability to request a new locale through Pontoon
* Design two translation review & feedback solutions
* Become comfortable with using Translate.next technologies
* Add support for XML file format used in Android

=== Peiying ===

=== Stas ===

* '''Release Fluent 1.0'''
** Fluent Syntax 1.0 Spec is published.
*** The reference parser is used to validate the spec.
*** The Syntax Guide is up-to-date.
** Implementations have been updated to Syntax 1.0.
*** The runtime fluent module.
*** The tooling fluent-syntax module.
*** The python-fluent module.
** L20n is deprecated.
** Post-1.0 plan (end of 2017 and 2018) has been proposed.

=== Adrian ===

* [Translate.Next] Rewrite Translate into a Single Page Application
** ''Key Result: All of Pontoon’s translate view UI is re-written using React and is internationalized using fluent-react.''
** All features from current Translate application are ported to the new one
** 100% of the code uses React and other efficient front-end technologies
** All new code is fully localizable
** All new code is unit tested and has decent code coverage (> 80%)

* [Translate.Next] Improve the review process
** ''Key Result: Translators and managers can give translation feedback when testing and reviewing translations within Pontoon.''
** Design a better review process for translations
*** Design 2 ideas for an improved review process
*** Organize a local community meetup to test, improve, and choose the better option
*** Define scope for the implementation of the chosen option

* Non-Workday goals
** Mentor a GSoC student
** Implement the review process that has been chosen with the community
** Organize testing of the new review process with the larger community

=== Theo (optional) ===

L10n:Goals/H1-2018

2018-07-02T08:00:56Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==
Please ensure that individual goals (all or part) are contributing to our [https://docs.google.com/document/d/1frLayrTL0TOChoezK_i2mueYchXDiawvry4HSZJyauc/edit?ts=5a3940b2 2018 OKRs for localization]. Citing the OKR that your H1 goal contributes to in your goal section is preferred.
* Rich editor UI for FTL - '''Matjaz''', S, Ax, Ad, Z
* Community leadership pilot - '''Jeff''', D, P, T
* Fluent in Gecko - '''Zibi''', Ax, F, S
* Multilingual Firefox - '''Zibi''', Ax, F, J
* Unified effort around language resources - '''Jeff''', F, D, P, T
* Fluent 1.0 - '''Stas''', Z, Ax
* New brand translation policy - '''Peiying''', Z, F, D
* Translate/review modes - '''Adrian''', M, Ax, F, D, P, J
* String tiers - '''Ryan''', M, Ad, Ax , F
* AWS Migration - '''Axel''', J, F
* Locale data in CLDR - '''Flod''', Z, F, D

==Roundtable==

=== Axel ===
* [ ][Q1] Migrate elmo to AWS
* [ ][Q2] Elmo support for github and Android/iOS formats
* [ ][H1] Create organization understanding of continuous localization
** prepare a slide deck
** circulate said slide deck in the Firefox org

I'll also be acting in a supporting rule for Fluent in Gecko, Fluent in Pontoon, and Translate.Next

=== Delphine ===
* Enable “all things l10n” for Firefox for Amazon Fire TV
** Recruit at least 5 localizers for this new project
** Work with flod and :boek on getting Firefox for Fire TV localizable and in Pontoon
** Create project in Pontoon
** Locale switcher is on the roadmap and in active development
** Test plan for the first Mozilla localized version of ffTV
** Test l10n on the upcoming builds for ffTV
** L10n Screenshots are on the roadmap and being developed

* CLDR
** Work with Kekoa/Zibi/Flod to build a mechanism to collect data for new locales and submit it to CLDR
** Compare Mozilla and CLDR data to identify potential issues with supported locales

* Open Innovation and Community Health
** Clearly defined process for gathering data on l10n communities, evaluating l10n community health, proposing solutions to community issues, and measuring their impact on the community.

* Brent Internship (not in Workday)
** Scope out work for Brent’s summer internship
** Initiate and share a document reflecting what that work will look like
** Collaborate with l10n-drivers on further refining this document

* Firefox iOS RTL (not in Workday)
** Still on roadmap
** Community engagement

* GSoC idea: Android XML support for Pontoon (not in Workday)
** Identify opportunities there. Might be more of a H2 thing - need to further investigate

=== Flod ===
Firefox Desktop
* [BLOCKED] Start shipping updates to dot releases and ESR channel (depending on Fluent status in 60).
* [DONE] Support migration of Preferences to Fluent:
** FTL patch reviews and testing.
** Run migration on l10n repositories.
** Update and integrate documentation to cover FTL features and Pontoon UI updates.
* [ONGOING, H2] Contribute to Project Medley with UX/Frontend/Zibi (Language Selector, multilingual Firefox)

CLDR data - Language and Region names
* [PARTIAL] Identify holes in CLDR data that would negatively affect migration to CLDR as datasource.
* [PARTIAL] Compare Mozilla and CLDR data to identify potential issues with supported locales.
* [BLOCKED] Support/test switch to CLDR as datasource.

CLDR data - Other
* [DONE] Verify plural rules for Firefox locales, comparing Gecko setting with Pontoon and CLDR.
* [PARTIAL] Support research/work on extending CLDR data (support for seed locales, or local sources in mozilla-data).
* [BLOCKED] Work with Kekoa/Zibi/Delphine to build a mechanism to collect data for new locales and submit it to CLDR.

Pontoon
* [DONE] Support string tiers implementation.
* [BLOCKED] Contribute to Translate.Next discussion.

Other products, tools, support for mozilla.org and mobile
* [DONE] Centralize search engine default and search order settings, clean up region.properties and update internal documentation.
* [DONE] Start assessing the impact of switching personal scripts and tools to Python 3.

Back-burner
* [] (from Q4-2017) Identify tool to localize documentation repositories.
* [] Identify inactive locales, reach out to them, try to find new contributors, remove them from builds if that fails (long term goal for 2017/2018).
* [] MDN l10n docs cleanup.

=== Gandalf ===

My planned work ('''in bold''' items put on my H1 goals list):

* Fluent in Gecko
** '''[][P1][Q1/Q2] Moving forward with milestones (complete Preferences migration at least?)'''
** '''[][P2][Q2] Make Fluent work with unprivileged content'''
** '''[][P2][Q2] Make Fluent work with System Addons'''
** '''[][P2][Q2] Make Fluent fast enough to put on startup path'''
** [][P2][Q1/Q2] Support Flod in CLDR in Gecko work
** [][P2][Q2] Mentoring Kekoa
** [][P3][Q2] Write "Fluent for Firefox Engineers" on MDN (covering best practices, test writing etc.)
* Gecko Intl module peer work
** JS Intl API (2018 edition and stage 3 proposals)
*** '''[][P2][Q1] mozIntl.RelativeTimeFormat'''
*** [][P2][Q1] Intl.Locale
*** [][P4][Q2] Intl.ListFormat
*** [][P4][Q1] Intl.RelativeTime updates for stage 4
** Gecko Intl module
*** [][P5][Q2] firstDay in OSPreferences
*** [][P4][Q2] further BCP47 tightening (ja-JP-mac normalization)
* Multilingual Firefox
** '''[][P2][Q1] Support UX/FrontEnd/Addons/Flod with Language Selector in Preferences'''
** [][P3][Q2] Pursue automatic langpack installation in Fennec
** '''[][P3][Q2] Instigate Firefox Installer Language Selector work'''
** '''[][P4][Q2] Propose changes to Firefox Download page UX to improve locale discoverability'''
* ECMA
** [][P2][Q1/Q2] Pursue Stage 4 for Intl.Locale
** [][P3][Q2] Pursue Stage 4 for Intl.LocaleList
** [][P5][Q2] Pursue Stage 2 for Intl.UnitFormat
* Support Stas in work on Fluent 1.0
** [][P3][Q1] Indentation relaxation decisions and parser patches (0.7)
** [][P4][Q2] Post-0.7 feedback round
** [][P3][Q2] Pseudolocales implementation
** '''[][P3][Q1/Q2] Semantic comments (arguments, message versioning, context)'''
** [][P3][Q2] Developer productivity (useful error messages, tooling)
** [][P5][Q2] WASM parser exploration
** [][P4][Q2] Testing infrastructure improvements
** [][P4][Q1/Q2] fluent-rs updates toward 1.0

=== Jeff ===
* '''Multilingual Firefox is on the roadmap'''
* '''Legal, Creative, and Firefox Product Management sign-off and begin implementing our recommended branding policy changes.'''
* '''Fluent as l10n framework for Geckoview native apps.'''
* Define community health criteria with Participation to be used to evaluate health pre-leadership agreements and post-leadership agreements.
* Define all P1 terms with UX.
* Evaluate ways to make use of new termbase data (e.g., Memsource, or other alternatives).
* Determine which paid MT services we'll work to incorporate into Pontoon (and a strategy for long-tail locales).

=== Matjaž ===

=== Peiying ===
*Drive the review of brand name localization policy
**[]Draft documentation on current practice and the reasons for change.
**[]Present 3 alternative solutions, their benefits, and implementation flows.
**[]Review the final document with Legal and Creative contacts to get their buy-ins.
**[]Drive the discussions of policy review with individual team product owners.
**[]Communicate to l10n communities on the policy change and the implementation flows for each alternative solution.

*SLA with marketing team
**[]Service agreement with Marketing team on mozilla.org on detailed terms and other marketing projects tailored for each product team.

*Legal documentation
**[]Review current locale coverage for Firefox desktop, mobile and Mozilla.
**[]Reference locale coverage in other tech companies of similar documentation
**[]Work with localization agency to on locale expansion, cost estimate; balance between legal budget for the year and the requested coverage.

*Others
**[]Common Voice: be the POC for the team, communicate with the communities, set up process and have the web pages ready by end of H1.
**[]Open Innovation and Community Health
**[]Write new and update localization documentation on github

=== Stas ===

* '''Release Fluent 1.0'''
** Fluent Syntax 1.0 Spec is published.
** Implementations in JS, Python and Rust are published.
** The developer experience of contributing to Fluent has improved:
*** Fluent API documentation is autogenerated from source.
*** Test fixtures are shared between fluent.js, python-fluent and fluent-rs.
*** We have test coverage reporting in CI in fluent.js.
** L20n is deprecated.
* Fluent in Gecko
** fluent-migrate is used for all Gecko UI migration work and doesn't block progress
** fluent-migrate doesn't break localization files used in xchannel
* Fluent in Pontoon
** Editing source FTL is a viable alternative to using the rich editor.
* Pontoon API
** We have a strong foundation for building an API which will power Translate.Next.
** The API doesn't fetch the same objects more than once during a single query.
** The API doesn't suffer from the N+1 queries problem.

=== Adrian ===

* [Translate.Next] Rewrite Translate into a Single Page Application
** Keep the same features as current app, do not break anything
** Rewrite using React and other efficient front-end technologies
** Build for flexibility, modularity and ease of maintenance
** All new code is fully localizable
** All new code is unit tested and has decent code coverage (> 80%)

* [Translate.Next] Help build a rich Fluent editor for translation
** Code infrastructure makes the integration of a rich Editor as easy as possible
** Rich Editor supports the most important Fluent features

* Non-Workday goals
** Replace Suggested state with Missing and introduce Unreviewed Suggestions ([https://bugzilla.mozilla.org/show_bug.cgi?id=1377969 bug 1377969])
** Improve Pontoon documentation for new contributors
** Mentor a GSoC student

* Stretch goals
** Expand the Pontoon API [note: only if Stas cannot do it]

=== Ryan ===

=== Theo (optional) ===

L10n:Meetings/SF-All-Hands

2018-06-08T06:59:31Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==
*

==Roundtable==

=== Delphine ===
* [PMs] Community events discussion. Set firm dates for all of them
* [PMs] Next steps since Brent won't be doing internship - what goals are we going to have to change
* [PMs/Areej] Discussion about localization processes with Areej, and how she can bring new people in when she goes back to Jordan
* [Flod/Zibi/Jeff] CLDR - What's next?
* [Axel] Fenix - latest updates (if needed)
* [Jeff] Video with Alcides
* [Personal] Finish pending localizer/internal docs (or at least, get as much done as possible)
* [Personal/OI] At least 4 meetings already set up about next steps for Open Innovation and l10n projects
* [Personal/Emma] D&I meetings
* [Personal/Mobile] Meeting with all Fenix/Rocket/Amazon/Focus/ etc (mobile) folks
* [Persona] Chat with Lockbox folks

=== Flod ===
* Get a better picture about upcoming community events, and where I might be involved
* Get a clear picture of Fluent 1.0 schedule, and how it impacts work on Gecko and Firefox
* Figure out CLDR next steps
** People involved: Jeff, Zibi, Delphine
* Discussion about mozilla.org l10n infrastructure, and how to change it
** People involved: Axel, Peiying, mozilla.org folks
* Discuss ownership of Multilingual Firefox discussion with Zibi
* Multilingual Firefox M1: finalize copy and UX, define scope
** People involved: Zibi, Emanuela, Michelle
* Multilingual Firefox M3: kick-off discussions
* Terminology discussion
* Meeting with Open Innovation about Community and l10n (if available)

=== Gandalf ===

* Unblock document.l10n - unprivileged/chrome
* Unblock browser.fluent - the other part of system addons
* Align document.l10n proposed changes with L10nRegistry v2 and Fluent 1.0
* Aid Stas in Fluent 1.0 pursue
* Kick-off Multilingual Firefox M3
* Help Emanuela finalize Multilingual Firefox M1 UX

=== Jeff ===
* Advance Fluent and Multilingual Firefox stories.
* Finalize list of H2 team OKRs.
* Learn and plan for Rocket roadmap with Delphine.
* Coordinate feedback discussions about community leadership roles and submit updates to descriptions in documentation.
* Help Jakob achieve his goals.
* Create final schedule for trips in H2 2018.

=== Matjaž ===
* Finalize list of H2 Pontoon OKRs.
* Fix 2 Fluent in Pontoon OKR bugs.
* Add-Ons localization talks.
* Help Michal achieve his goals.

=== Pei ===

=== Stas ===
* Plan the release of Fluent 0.7, 0.8 and 1.0
* Plan Q3 and Q4 for Fluent
* Plan 2019 for Fluent
* Move arewefluentyet.com forward
* Gather fluent-react feedback from Common Voice, Devtools

=== Axel ===

=== Areej ===
* Re-build the Mozilla community in Jordan and empower WoMoz
* Learn what best practices of the successful communities, and involve in regional projects, so the contributions can be sustainable
* Know more about localization process and reviewing
* Communicate with the different teams and catch up with the latest projects

=== Fauzan ===
* Re-arrange Mozilla ID L10n community, due to the departure of Benny as manager
* Planning ID community event in Indonesia
* Do preparation on bringing Rocket to more Indonesian locale, such as Sundanese (su) and Javanese (jv)
* Prepare a short guide for local community if they're interested to localize Rocket/Fennec to other Indonesian locale

=== Jakob ===

=== Michal ===

=== Dan ===

=== Kekoa ===
* Understand roadmap for Terminology.
* Become a bonafide member of the Fluent team.
* Determine internship projects and define deliverables.
* Establish relationships with people I will work with on internship projects.

L10n:Meetings/SF-All-Hands

2018-06-08T06:59:04Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==
*

==Roundtable==

=== Delphine ===
* [PMs] Community events discussion. Set firm dates for all of them
* [PMs] Next steps since Brent won't be doing internship - what goals are we going to have to change
* [PMs/Areej] Discussion about localization processes with Areej, and how she can bring new people in when she goes back to Jordan
* [Flod/Zibi/Jeff] CLDR - What's next?
* [Axel] Fenix - latest updates (if needed)
* [Jeff] Video with Alcides
* [Personal] Finish pending localizer/internal docs (or at least, get as much done as possible)
* [Personal/OI] At least 4 meetings already set up about next steps for Open Innovation and l10n projects
* [Personal/Emma] D&I meetings
* [Personal/Mobile] Meeting with all Fenix/Rocket/Amazon/Focus/ etc (mobile) folks
* [Persona] Chat with Lockbox folks

=== Flod ===
* Get a better picture about upcoming community events, and where I might be involved
* Get a clear picture of Fluent 1.0 schedule, and how it impacts work on Gecko and Firefox
* Figure out CLDR next steps
* People involved: Jeff, Zibi, Delphine
* Discussion about mozilla.org l10n infrastructure, and how to change it
* People involved: Axel, Peiying, mozilla.org folks
* Discuss ownership of Multilingual Firefox discussion with Zibi
* Multilingual Firefox M1: finalize copy and UX, define scope
* People involved: Zibi, Emanuela, Michelle
* Multilingual Firefox M3: kick-off discussions
* Terminology discussion
* Meeting with Open Innovation about Community and l10n (if available)

=== Gandalf ===

* Unblock document.l10n - unprivileged/chrome
* Unblock browser.fluent - the other part of system addons
* Align document.l10n proposed changes with L10nRegistry v2 and Fluent 1.0
* Aid Stas in Fluent 1.0 pursue
* Kick-off Multilingual Firefox M3
* Help Emanuela finalize Multilingual Firefox M1 UX

=== Jeff ===
* Advance Fluent and Multilingual Firefox stories.
* Finalize list of H2 team OKRs.
* Learn and plan for Rocket roadmap with Delphine.
* Coordinate feedback discussions about community leadership roles and submit updates to descriptions in documentation.
* Help Jakob achieve his goals.
* Create final schedule for trips in H2 2018.

=== Matjaž ===
* Finalize list of H2 Pontoon OKRs.
* Fix 2 Fluent in Pontoon OKR bugs.
* Add-Ons localization talks.
* Help Michal achieve his goals.

=== Pei ===

=== Stas ===
* Plan the release of Fluent 0.7, 0.8 and 1.0
* Plan Q3 and Q4 for Fluent
* Plan 2019 for Fluent
* Move arewefluentyet.com forward
* Gather fluent-react feedback from Common Voice, Devtools

=== Axel ===

=== Areej ===
* Re-build the Mozilla community in Jordan and empower WoMoz
* Learn what best practices of the successful communities, and involve in regional projects, so the contributions can be sustainable
* Know more about localization process and reviewing
* Communicate with the different teams and catch up with the latest projects

=== Fauzan ===
* Re-arrange Mozilla ID L10n community, due to the departure of Benny as manager
* Planning ID community event in Indonesia
* Do preparation on bringing Rocket to more Indonesian locale, such as Sundanese (su) and Javanese (jv)
* Prepare a short guide for local community if they're interested to localize Rocket/Fennec to other Indonesian locale

=== Jakob ===

=== Michal ===

=== Dan ===

=== Kekoa ===
* Understand roadmap for Terminology.
* Become a bonafide member of the Fluent team.
* Determine internship projects and define deliverables.
* Establish relationships with people I will work with on internship projects.

L10n:Mozilla Team

2018-05-24T09:14:13Z

Flod: Clean up roles, remove Team Resources section

__NOTOC__
{{L10navbar}}

So you would like to learn more about the Mozilla L10n team? You've come to the right place! Click on the links below to learn about each team member, the weekly meetings, and the projects they're working on. 

 

== Team bios ==
=== Mozilla Corporation ===
;[https://wiki.mozilla.org/User:AxelHecht Axel Hecht] : Team technical lead. Owner for elmo, compare-locales, and l10n automation.
;[http://informationisart.com/stas/ Staś Małolepszy] : Fluent release driver, including feature design, specification, and software engineering for Fluent.
;[http://diary.braniecki.net/ Zibi Braniecki] : Gecko, Intl, Fluent, L10n, Tools
;[http://jeffbeatty.org Jeff Beatty] : Head of localization. Talk to me about l10n technical and community strategy, cross-cultural design, and management.
;[http://horv.at/blog Matjaž Horvat] : [https://pontoon.mozilla.org/ Pontoon] owner.
;[http://adrian.gaudebert.fr/home_en Adrian Gaudebert] : [https://pontoon.mozilla.org/ Pontoon] minion.
;[http://blog.lebedel.net/ Delphine Lebédel] : L10n-driver for mobile products (Android and iOS). Community builder & enabler.
;[http://pbase.com/faerie_39/ Peiying Mo] : L10n driver for web projects: Mozilla.org, marketing, legal localization; vendor management; community builder.
;[https://flod.org/ Francesco Lodolo (:flod)] : L10n driver for Firefox desktop localization and Test Pilot. Owner for webdashboards and AppStores webapp, peer and technical support for mozilla.org and mobile, product l10n early review in mozilla-central.

=== Mozilla Foundation ===
;[https://www.theochevalier.fr/ Théo Chevalier] : L10n driver for Mozilla Foundation projects, Advocacy & fundraising in particular.

 

== Current projects ==

*[[L10n:Pontoon|Pontoon]]
*[https://wiki.mozilla.org/Fluent Fluent]
*[https://wiki.mozilla.org/Elmo Elmo]

== Contact ==

Send mail to [mailto:L10n-drivers@mozilla.org L10n driver's team] or subscribe to the [http://groups.google.com/group/mozilla.dev.l10n/topics Mozilla l10n forum]. 
[[Category:L10n]]

L10n:Bugogram

2018-04-18T17:40:57Z

Flod: /* build */

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

== shipping ==
; short_desc : [%(loc)s] Firefox release tracker %(language)s
; alias : fx-l10n-%(loc)s
; blocked : fx-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,pmo@mozilla.com
This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibility to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds Mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

== bugzilla ==
; short_desc : Create l10n Bugzilla component for %(language)s (%(loc)s), add value for Locale field
; product : bugzilla.mozilla.org
; component : Administration
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com
We need a Bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custom field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations
Component: %(loc)s / %(language)s
Description: %(language)s Localization (...)

Assignee: nobody
QA Contact: Empty
Triage owner: :flod (francesco.lodolo@gmail.com)

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description?

Once we have the description, this bug will be fixed by Mozilla staff.

== ldap ==
; short_desc : Create LDAP account for %(name)s <%(bugmail)s>
; product : Infrastructure & Operations
; component : Infrastructure: LDAP
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com

Please create an LDAP account for %(name)s. We'll want a password, and be part of the locale_peer and tableau_users groups.

This bug is independent of repository access requests.

== hg_repo ==
; short_desc : l10n-central Mercurial repository for '%(loc)s'
; product : Developer Services
; component : Mercurial: hg.mozilla.org
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
Please create a new hg repository for Firefox localization. The repository should be:

- l10n-central/%(loc)s/

with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s

Please make sure that dxr is updated to pick up the new repository.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== build ==
; short_desc : Add '%(loc)s' to Firefox Nightly build
; product : Firefox Build System
; component : General
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
We need to add '%(loc)s' to browser/locales/all-locales on mozilla-central.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== product-details ==
; short_desc : Add '%(loc)s' to product-details
; product : Release Engineering
; component : Ship It
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com,francesco.lodolo@gmail.com
We need to add '%(loc)s' to the Firefox Nightly l10n builds on mozilla.org:
* Locale needs to be added to the list of supported Nightly locales.
* If missing, add an entry in languages.json with both the English and localized name for this locale.

P.S. To be clear to the localization team, this bug is handled by Mozilla staff.

== Webservices ==
We'll have a separate bug for each web service area, namely
* search
* protocol handlers
* rss readers

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives:
Google, Bing, Amazon, DuckDuckGo, Twitter, Wikipedia, eBay

Adding brand new search engines, that not yet ship in any other language, needs approval from Business Development and requires more time to get authorization and assets from the provider. To avoid blocking the initial set up, this type of requests should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.

The %(language)s team and flod will be driving this bug to completion.

=== protocol ===
; short_desc : [%(loc)s] Firefox protocol handler setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

=== readers ===
; short_desc : [%(loc)s] Firefox News reader setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
News readers are web services allowing users to subscribe to RSS/ATOM feeds online and view them. If Firefox detects a feed, it offers the user the option to subscribe to it, either as a live bookmark or via one of the web services.

The current News Reader in en-US is My Yahoo!.

We want to ship a good set of defaults for %(language)s and will do that in three stages.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. After we decide on a particular news reader, flod will contact the owner and ask for permission. %(name)s, we'll likely need your help to at least get the contact information.

Once we have a specification on what the set of news readers for %(language)s should look like, flod will work on an implementation for that. flod will create and attach patches for the desired changes and request a review. After a successful review, flod team will land them. If you're interested, you can provide those patches too and request a review from flod before landing.

Please don't commit any modifications in browser/chrome/browser-region/region.properties to the hg repository without a patch reviewed by flod, Axel or someone else appointed by them. The data here is sensitive to users and our search partners, thus requiring the extra care here.

The %(language)s team will be driving this bug to completion.

== websetup ==
; short_desc : [%(loc)s] bootstrap %(language)s on GitHub and the web dashboard
; product : Mozilla Localizations
; component : Infrastructure
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com
; blocked : fx-l10n-%(loc)s

flod, Peiying, please set up the webdashboard for %(language)s, and add web pages to this locale's folder on mozilla.org.

Please notify in the actual translation bug when this is done.

== webparts ==
; short_desc : [%(loc)s] Firefox initial web parts for %(language)s
; product : www.mozilla.org
; component : L10N
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages. There's a set of pages that are essential to having a successful Firefox localization and promotion, and those depend on the files listed below.

flod or Peying will follow up here when the initial setup work is done. After that, you'll find the files to localize in GitHub.

The repository you want to work with is located at https://github.com/mozilla-l10n/www.mozilla.org/tree/master/%(loc)s/

The status of web parts for your locale on GitHub can be checked at this URL (updated every 15 minutes)
http://l10n.mozilla-community.org/webdashboard/?locale=%(loc)s

Please start by translating files with higher priority according to the dashboard.

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

== sumo ==
; short_desc : [%(loc)s] Enable %(language)s localization on SUMO
; product : support.mozilla.org
; component : Localization
; cc : %(bugmail)s
; blocked : fx-l10n-%(loc)s
We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

== done ==
That's all folks.

L10n:Mobile/Bugogram

2018-04-05T18:48:25Z

Flod:

== shipping ==
; short_desc : [%(loc)s] Firefox Mobile release tracker %(language)s
; alias : fm-l10n-%(loc)s
; blocked : fm-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,lebedel.delphine@gmail.com
This is a tracker bug for releasing Firefox Mobile %(loc)s.

This bug is not that detailed, but as we get particular work items, they should
block this bug for tracking and discoverability.

== Webservices ==
We'll have a separate bug for each web service area. Currently that's only
* search.

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox Mobile for %(language)s.
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com,lebedel.delphine@gmail.com
; blocked : fm-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Mobile/Productization

We want to ship Firefox Mobile with a good list of search engines for %(language)s.

We're going to work towards this in three phases. First, the localization team and the l10n drivers will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this, the guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Mobile/Productization>.

For en-US, we currently use this set, to which we can fall back in the case of lacking localized alternatives:

> Google, Bing, Amazon, Twitter, Wikipedia

We may also want to go with just a subset of the en-US engines, if that's more appropriate for the local market.

Adding brand new search engines, that don't yet ship in any other language, needs approval from Business Development and requires more time to get authorization and assets from the provider. To avoid blocking the initial set up, this type of requests should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

For search engines that we already ship with on desktop and that you would like to include in mobile as well, the permission is not needed. Consider using a mobile version of the engine if one is available. For Android we'll want a specific 96x96px image, with colored background and rounder corners (6px radius).

Once we have a specification on what the search engines for %(language)s should look like, Delphine and the localization team will work on the implementation. Delphine will create and attach patches for the desired changes and get them reviewed. After a successful review, Delphine will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask Delphine for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by Delphine, flod, Axel or someone else appointed by the l10n drivers. The data here is sensitive to users and our search partners, thus the extra care here.

The %(language)s team and Delphine will be driving this bug to completion.

== done ==
That's all folks.

L10n:Bugogram

2018-04-05T18:48:01Z

Flod:

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

== shipping ==
; short_desc : [%(loc)s] Firefox release tracker %(language)s
; alias : fx-l10n-%(loc)s
; blocked : fx-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,pmo@mozilla.com
This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibility to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds Mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

== bugzilla ==
; short_desc : Create l10n Bugzilla component for %(language)s (%(loc)s), add value for Locale field
; product : bugzilla.mozilla.org
; component : Administration
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com
We need a Bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custom field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations
Component: %(loc)s / %(language)s
Description: %(language)s Localization (...)

Assignee: nobody
QA Contact: Empty
Triage owner: :flod (francesco.lodolo@gmail.com)

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description?

Once we have the description, this bug will be fixed by Mozilla staff.

== ldap ==
; short_desc : Create LDAP account for %(name)s <%(bugmail)s>
; product : Infrastructure & Operations
; component : Infrastructure: LDAP
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com

Please create an LDAP account for %(name)s. We'll want a password, and be part of the locale_peer and tableau_users groups.

This bug is independent of repository access requests.

== hg_repo ==
; short_desc : l10n-central Mercurial repository for '%(loc)s'
; product : Developer Services
; component : Mercurial: hg.mozilla.org
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
Please create a new hg repository for Firefox localization. The repository should be:

- l10n-central/%(loc)s/

with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s

Please make sure that dxr is updated to pick up the new repository.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== build ==
; short_desc : Add '%(loc)s' to Firefox Nightly build
; product : Core
; component : Build Config
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
We need to add '%(loc)s' to browser/locales/all-locales on mozilla-central.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== product-details ==
; short_desc : Add '%(loc)s' to product-details
; product : Release Engineering
; component : Ship It
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com,francesco.lodolo@gmail.com
We need to add '%(loc)s' to the Firefox Nightly l10n builds on mozilla.org:
* Locale needs to be added to the list of supported Nightly locales.
* If missing, add an entry in languages.json with both the English and localized name for this locale.

P.S. To be clear to the localization team, this bug is handled by Mozilla staff.

== Webservices ==
We'll have a separate bug for each web service area, namely
* search
* protocol handlers
* rss readers

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives:
Google, Bing, Amazon, DuckDuckGo, Twitter, Wikipedia, eBay

Adding brand new search engines, that not yet ship in any other language, needs approval from Business Development and requires more time to get authorization and assets from the provider. To avoid blocking the initial set up, this type of requests should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.

The %(language)s team and flod will be driving this bug to completion.

=== protocol ===
; short_desc : [%(loc)s] Firefox protocol handler setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

=== readers ===
; short_desc : [%(loc)s] Firefox News reader setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
News readers are web services allowing users to subscribe to RSS/ATOM feeds online and view them. If Firefox detects a feed, it offers the user the option to subscribe to it, either as a live bookmark or via one of the web services.

The current News Reader in en-US is My Yahoo!.

We want to ship a good set of defaults for %(language)s and will do that in three stages.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. After we decide on a particular news reader, flod will contact the owner and ask for permission. %(name)s, we'll likely need your help to at least get the contact information.

Once we have a specification on what the set of news readers for %(language)s should look like, flod will work on an implementation for that. flod will create and attach patches for the desired changes and request a review. After a successful review, flod team will land them. If you're interested, you can provide those patches too and request a review from flod before landing.

Please don't commit any modifications in browser/chrome/browser-region/region.properties to the hg repository without a patch reviewed by flod, Axel or someone else appointed by them. The data here is sensitive to users and our search partners, thus requiring the extra care here.

The %(language)s team will be driving this bug to completion.

== websetup ==
; short_desc : [%(loc)s] bootstrap %(language)s on GitHub and the web dashboard
; product : Mozilla Localizations
; component : Infrastructure
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com
; blocked : fx-l10n-%(loc)s

flod, Peiying, please set up the webdashboard for %(language)s, and add web pages to this locale's folder on mozilla.org.

Please notify in the actual translation bug when this is done.

== webparts ==
; short_desc : [%(loc)s] Firefox initial web parts for %(language)s
; product : www.mozilla.org
; component : L10N
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages. There's a set of pages that are essential to having a successful Firefox localization and promotion, and those depend on the files listed below.

flod or Peying will follow up here when the initial setup work is done. After that, you'll find the files to localize in GitHub.

The repository you want to work with is located at https://github.com/mozilla-l10n/www.mozilla.org/tree/master/%(loc)s/

The status of web parts for your locale on GitHub can be checked at this URL (updated every 15 minutes)
http://l10n.mozilla-community.org/webdashboard/?locale=%(loc)s

Please start by translating files with higher priority according to the dashboard.

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

== sumo ==
; short_desc : [%(loc)s] Enable %(language)s localization on SUMO
; product : support.mozilla.org
; component : Localization
; cc : %(bugmail)s
; blocked : fx-l10n-%(loc)s
We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

== done ==
That's all folks.

L10n:Bugogram

2018-04-04T15:28:50Z

Flod: /* hg_repo */

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

== shipping ==
; short_desc : [%(loc)s] Firefox release tracker %(language)s
; alias : fx-l10n-%(loc)s
; blocked : fx-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,pmo@mozilla.com
This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibility to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds Mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

== bugzilla ==
; short_desc : Create l10n Bugzilla component for %(language)s (%(loc)s), add value for Locale field
; product : bugzilla.mozilla.org
; component : Administration
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com
We need a Bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custom field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations
Component: %(loc)s / %(language)s
Description: %(language)s Localization (...)

Assignee: nobody
QA Contact: Empty
Triage owner: :flod (francesco.lodolo@gmail.com)

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description?

Once we have the description, this bug will be fixed by Mozilla staff.

== ldap ==
; short_desc : Create LDAP account for %(name)s <%(bugmail)s>
; product : Infrastructure & Operations
; component : Infrastructure: LDAP
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com

Please create an LDAP account for %(name)s. We'll want a password, and be part of the locale_peer and tableau_users groups.

This bug is independent of repository access requests.

== hg_repo ==
; short_desc : l10n-central Mercurial repository for '%(loc)s'
; product : Developer Services
; component : Mercurial: hg.mozilla.org
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
Please create a new hg repository for Firefox localization. The repository should be:

- l10n-central/%(loc)s/

with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s

Please make sure that dxr is updated to pick up the new repository.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== build ==
; short_desc : Add '%(loc)s' to Firefox Nightly build
; product : Core
; component : Build Config
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
We need to add '%(loc)s' to browser/locales/all-locales on mozilla-central.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== product-details ==
; short_desc : Add '%(loc)s' to product-details
; product : Release Engineering
; component : Ship It
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com,francesco.lodolo@gmail.com
We need to add '%(loc)s' to the Firefox Nightly l10n builds on mozilla.org:
* Locale needs to be added to the list of supported Nightly locales.
* If missing, add an entry in languages.json with both the English and localized name for this locale.

P.S. To be clear to the localization team, this bug is handled by Mozilla staff.

== Webservices ==
We'll have a separate bug for each web service area, namely
* search
* protocol handlers
* rss readers

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives:
Google, Yahoo!, Bing, Amazon, DuckDuckGo, Twitter, Wikipedia, eBay

Adding brand new search engines, that not yet ship in any other language, needs approval from Business Development and requires more time to get authorization and assets from the provider. To avoid blocking the initial set up, this type of requests should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.

The %(language)s team and flod will be driving this bug to completion.

=== protocol ===
; short_desc : [%(loc)s] Firefox protocol handler setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

=== readers ===
; short_desc : [%(loc)s] Firefox News reader setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
News readers are web services allowing users to subscribe to RSS/ATOM feeds online and view them. If Firefox detects a feed, it offers the user the option to subscribe to it, either as a live bookmark or via one of the web services.

The current News Reader in en-US is My Yahoo!.

We want to ship a good set of defaults for %(language)s and will do that in three stages.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. After we decide on a particular news reader, flod will contact the owner and ask for permission. %(name)s, we'll likely need your help to at least get the contact information.

Once we have a specification on what the set of news readers for %(language)s should look like, flod will work on an implementation for that. flod will create and attach patches for the desired changes and request a review. After a successful review, flod team will land them. If you're interested, you can provide those patches too and request a review from flod before landing.

Please don't commit any modifications in browser/chrome/browser-region/region.properties to the hg repository without a patch reviewed by flod, Axel or someone else appointed by them. The data here is sensitive to users and our search partners, thus requiring the extra care here.

The %(language)s team will be driving this bug to completion.

== websetup ==
; short_desc : [%(loc)s] bootstrap %(language)s on GitHub and the web dashboard
; product : Mozilla Localizations
; component : Infrastructure
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com
; blocked : fx-l10n-%(loc)s

flod, Peiying, please set up the webdashboard for %(language)s, and add web pages to this locale's folder on mozilla.org.

Please notify in the actual translation bug when this is done.

== webparts ==
; short_desc : [%(loc)s] Firefox initial web parts for %(language)s
; product : www.mozilla.org
; component : L10N
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages. There's a set of pages that are essential to having a successful Firefox localization and promotion, and those depend on the files listed below.

flod or Peying will follow up here when the initial setup work is done. After that, you'll find the files to localize in GitHub.

The repository you want to work with is located at https://github.com/mozilla-l10n/www.mozilla.org/tree/master/%(loc)s/

The status of web parts for your locale on GitHub can be checked at this URL (updated every 15 minutes)
http://l10n.mozilla-community.org/webdashboard/?locale=%(loc)s

Please start by translating files with higher priority according to the dashboard.

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

== sumo ==
; short_desc : [%(loc)s] Enable %(language)s localization on SUMO
; product : support.mozilla.org
; component : Localization
; cc : %(bugmail)s
; blocked : fx-l10n-%(loc)s
We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

== done ==
That's all folks.

L10n:Meetings/2018 Ljubljana

2018-03-06T15:07:16Z

Flod: /* Logistics */

[[Category:L10n workdays|{{SUBPAGENAME}}]]
[[Category:L10n meetings|{{SUBPAGENAME}}]]

__NOTOC__
==Logistics==
;where:
Grand Union Hotel (DO NOT BOOK)

Miklošičeva cesta 1

1000 Ljubljana

Slovenia

;when: 26-29 March 2018
;travel: Plan to arrive on Sunday evening (25th) and to leave as early as Thursday evening (29th).

;arrivals:
{| border="1"
|-
| Name
| Date
| Time
| Airport
| Flight
|-
| Jeff
|
|
|
|
|-
| Zibi
|
|
|
|
|-
| Pike
| 25
| 16:50
| LJU
| Adria 113
|-
| Matjaž
|
|
|
|
|-
| Stas
| Mar 26
| 11:25
| LJU
| LO 5561
|-
| Pei
|
|
|
|
|-
| Flod
| Mar 25
| Early afternoon
| By car
|
|-
| Delphine
|
|
|
|
|-
| Adrian
| Mar 25
| 16:50
| LJU
| LH 6904
|-
| Théo
|
|
|
|
|-
| Ryan
|
|
|
|
|-
|}

;departures:
{| border="1"
|-
| Name
| Date
| Time
| Airport
| Flight
|-
| Jeff
|
|
|
|
|-
| Zibi
|
|
|
|
|-
| Pike
| 30
| 13:25
| LJU
| Adria 112
|-
| Matjaž
|
|
|
|
|-
| Stas
| Mar 30
| 13:40
| LJU
| LO 616
|-
| Pei
|
|
|
|
|-
| Flod
| Mar 30
| Morning
| By Car
|
|-
| Delphine
|
|
|
|
|-
| Adrian
| Mar 30
| 17:50
| LJU
| OS 7034
|-
| Théo
|
|
|
|
|-
| Ryan
|
|
|
|
|-
|}

===Goals of work week===

==Schedule==
====Sunday====
* Arrivals
* Dinner:
====Monday====
{| border="1"
|-
| Start
| Lunch
| End
| Dinner
|-
| 09:00
| 13:00
| 17:00
|
|-
|}
;Morning
*Lunch:TBD
;Afternoon
*Dinner:TBD

====Tuesday====
{| border="1"
|-
| Start
| Lunch
| End
| Dinner
|-
| 09:00
| 13:00
| 17:00
|
|-
|}
;Morning
*Lunch:TBD
;Afternoon
*Dinner:TBD
====Wednesday====
{| border="1"
|-
| Start
| Lunch
| End
| Dinner
|-
| 09:00
| 13:00
| 17:00
|
|-
|}
;Morning
*Lunch:TBD
;Afternoon
*Dinner:TBD
====Thursday====
{| border="1"
|-
| Start
| Lunch
| End
| Dinner
|-
| 09:00
| 13:00
| 17:00
|
|-
|}
;Morning
* Lunch:TBD
;Afternoon
*Dinner:TBD

== Possible Group Activities ==

Fluent

2018-02-21T09:07:28Z

Flod:

Project Fluent is a localization system designed to improve how software is translated. See http://projectfluent.org/ for more information, including the links to the project's repositories and the GitHub wiki.

==Mozilla Projects Using Fluent==

=====fluent-react=====
* https://github.com/mozilla/testpilot (the website)
* https://github.com/mozilla-services/screenshots (the website)
* https://github.com/mozilla/voice-web
* https://github.com/mozilla-lockbox/lockbox-extension (not actively localized)

=====vanilla fluent=====
*https://github.com/mozilla/send

Fluent

2018-02-10T07:34:50Z

Flod: /* Mozilla Projects Using Fluent */

Project Fluent is a localization system designed to improve how software is translated. See http://projectfluent.org/ for more information, including the links to the project's repositories and the GitHub wiki.

==Mozilla Projects Using Fluent==

=====fluent-react=====
* https://github.com/mozilla/testpilot (the website)
* https://github.com/mozilla-services/screenshots (the website)
* https://github.com/mozilla-lockbox/lockbox-extension (not actively localized)
* https://github.com/mozilla/voice-web (not actively localized)

=====vanilla fluent=====
*https://github.com/mozilla/send

L10n:Goals/H1-2018

2018-02-09T16:47:25Z

Flod: /* Flod */

L10n:Goals/H1-2018

2018-02-09T07:26:32Z

Flod: /* Flod */

2017-11-03T06:58:07Z

Flod: /* search */

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

== shipping ==
; short_desc : [%(loc)s] Firefox release tracker %(language)s
; alias : fx-l10n-%(loc)s
; blocked : fx-l10n-tracker
; cc : %(bugmail)s,l10n@mozilla.com,francesco.lodolo@gmail.com,pmo@mozilla.com
This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibility to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds Mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

== bugzilla ==
; short_desc : Create l10n Bugzilla component for %(language)s (%(loc)s), add value for Locale field
; product : bugzilla.mozilla.org
; component : Administration
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com
We need a Bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custom field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations
Component: %(loc)s / %(language)s
Description: %(language)s Localization (...)

Assignee: nobody
QA Contact: Empty

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description?

Once we have the description, this bug will be fixed by Mozilla staff.

== ldap ==
; short_desc : Create LDAP account for %(name)s <%(bugmail)s>
; product : Infrastructure & Operations
; component : Infrastructure: LDAP
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,l10n@mozilla.com

Please create an LDAP account for %(name)s. We'll want a password, and be part of the locale_peer and tableau_users groups.

This bug is independent of repository access requests.

== hg_repo ==
; short_desc : l10n-central Mercurial repository for '%(loc)s'
; product : Developer Services
; component : Mercurial: hg.mozilla.org
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
Please create a new hg repository for Firefox localization. The repository should be:

- l10n-central/%(loc)s/

with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

Please make sure that dxr is updated to pick up the new repository.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== build ==
; short_desc : Add '%(loc)s' to Firefox Nightly build
; product : Core
; component : Build Config
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com
We need to add '%(loc)s' to browser/locales/all-locales on mozilla-central.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

== product-details ==
; short_desc : Add '%(loc)s' to product-details
; product : Release Engineering
; component : Ship It
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com,francesco.lodolo@gmail.com
We need to add '%(loc)s' to the Firefox Nightly l10n builds on mozilla.org:
* Locale needs to be added to the list of supported Nightly locales.
* If missing, add an entry in languages.json with both the English and localized name for this locale.

P.S. To be clear to the localization team, this bug is handled by Mozilla staff.

== Webservices ==
We'll have a separate bug for each web service area, namely
* search
* protocol handlers
* rss readers

=== search ===
; short_desc : [%(loc)s] Search engine setup for Firefox for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives:
Google, Yahoo!, Bing, Amazon, DuckDuckGo, Twitter, Wikipedia, eBay

Adding brand new search engines, i.e. not shipping in any other languages, needs approval from Business Development and requires more time to get approval and assets. Ideally, requests of this type should be split into follow up bugs. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.

The %(language)s team and flod will be driving this bug to completion.

=== protocol ===
; short_desc : [%(loc)s] Firefox protocol handler setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

=== readers ===
; short_desc : [%(loc)s] Firefox News reader setup for %(language)s
; cc : l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
; blocked : fx-l10n-%(loc)s
; keywords : productization
; bug_file_loc : https://wiki.mozilla.org/L10n:Firefox/Productization
News readers are web services allowing users to subscribe to RSS/ATOM feeds online and view them. If Firefox detects a feed, it offers the user the option to subscribe to it, either as a live bookmark or via one of the web services.

The current News Reader in en-US is My Yahoo!.

We want to ship a good set of defaults for %(language)s and will do that in three stages.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. After we decide on a particular news reader, flod will contact the owner and ask for permission. %(name)s, we'll likely need your help to at least get the contact information.

Once we have a specification on what the set of news readers for %(language)s should look like, flod will work on an implementation for that. flod will create and attach patches for the desired changes and request a review. After a successful review, flod team will land them. If you're interested, you can provide those patches too and request a review from flod before landing.

Please don't commit any modifications in browser/chrome/browser-region/region.properties to the hg repository without a patch reviewed by flod, Axel or someone else appointed by them. The data here is sensitive to users and our search partners, thus requiring the extra care here.

The %(language)s team will be driving this bug to completion.

== websetup ==
; short_desc : [%(loc)s] bootstrap %(language)s on GitHub and the web dashboard
; product : Mozilla Localizations
; component : Infrastructure
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com
; blocked : fx-l10n-%(loc)s

flod, Peiying, please set up the webdashboard for %(language)s, and add web pages to this locale's folder on mozilla.org.

Please notify in the actual translation bug when this is done.

== webparts ==
; short_desc : [%(loc)s] Firefox initial web parts for %(language)s
; product : www.mozilla.org
; component : L10N
; blocked : fx-l10n-%(loc)s
; cc : %(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com,pmo@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages. There's a set of pages that are essential to having a successful Firefox localization and promotion, and those depend on the files listed below.

flod or Peying will follow up here when the initial setup work is done. After that, you'll find the files to localize in GitHub.

The repository you want to work with is located at https://github.com/mozilla-l10n/www.mozilla.org/tree/master/%(loc)s/

The status of web parts for your locale on GitHub can be checked at this URL (updated every 15 minutes)
http://l10n.mozilla-community.org/webdashboard/?locale=%(loc)s

Please start by translating files with higher priority according to the dashboard.

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

== sumo ==
; short_desc : [%(loc)s] Enable %(language)s localization on SUMO
; product : support.mozilla.org
; component : Localization
; cc : %(bugmail)s
; blocked : fx-l10n-%(loc)s
We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

== done ==
That's all folks.

L10n:Goals/Q4 2017

2017-10-17T19:44:56Z

Flod: /* Flod */

[[Category:L10n goals]]
==Team Goals==
Please ensure that individual goals (all or part) are contributing to our [https://docs.google.com/document/d/1s_b679LNzXcvNjA6K5pEnhnDhgH8DFCV1aVwyfCUSTc/edit#heading=h.m68mgmculzl8 2017 OKRs for localization]. Citing the OKR that your Q4 goal contributes to in your goal section is preferred.
* Cross-channel - Axel, J, M, F, D
* AWS Migration - Axel, J, F
* UI for FTL in Pontoon - Matjaz, S, Ax, Ad, Z
* Mobile at a glance - Delphine
* Community Workshops - Jeff, P, D, F, T
* Firefox Quantum Marketing - Peiying, F, D
* Predictable l10n Demand - Peiying, F, T
* [16OCT] Pudelo stage 2 - Ryan, M, Ad, Ax
* 2018 OKR planning - Jeff, all
* Fluent in Gecko - Zibi, Ax, S, M, Ad
* Pontoon.next - Adrian, M, Ax, PM group

[https://docs.google.com/spreadsheets/d/14qGL9F_nbP-m5WHPQKWREDMn6DZZqgWKBUVT67n_jxc/edit#gid=0 Planning spreadsheet].

==Roundtable==

=== Axel ===

=== Delphine ===

=== Flod ===
Firefox Desktop
* Support cross-channel repository initiative through:
** [DONE] (from Q2) Initial testing and support.
** [] (from Q2) Creating documentation for new processes.
** [DONE] (from Q2) Adding support for cross-channel repository in Transvision.
** [] (from Q2) Starting discussion with release management about shipping updates on release and ESR channels.
* [] Try to move at least one new locale to Beta.

Other products, tools, support for mozilla.org and mobile
* [] Identify tool to localize documentation repositories.
* Transvision:
** [DONE] Add Focus for Android and iOS, rationalize code around projects.
** [] Add view to check keyboard shortcuts.
* [] (ongoing) Support Test Pilot experiments and system add-ons (review, localization setup, infrastructure).

Back-burner
* [] (from Q2, blocked by new project configurations) Get string tiers implemented in tools (Pontoon).
* [] (ongoing) Identify inactive locales, reach out to them, try to find new contributors, remove them from builds if that fails (long term goal for 2017).
* [] (from Q2) Support DevTools move to an external GitHub repository.

=== Gandalf ===

* [] Enable Fluent in Firefox
* [] Release fluent-rs 0.1.0
* [] Design a plan for Fluent in WebExtensions

=== Jeff ===
'''[] Support landing Fluent in Firefox'''
* This will be completed when the appropriate stakeholders have been gathered, release criteria has been defined, and Fluent is on the Firefox roadmap.
'''[] Finalize 2018 OKR doc'''

'''[] Identify l10n design sprints for H12017.'''

'''[] Create framework for defining l10n community leadership and contribution models with Open Innovation.'''

=== Matjaž ===
* FTL: Land advanced UI for FTL in Pontoon
* Fix Bug 1305281: search across all projects
* Work with Adrian on documenting the 2018 roadmap and technology choices for Pontoon.NEXT
* Create proposal of new Pontoon development process.

=== Stas ===

1. Support Fluent in cross-channel localization.

[ ] Adapt compare-locales to support Fluent Comments, Sections and whitespace.
[ ] Enable merging FTL files across channels.

2. Create fluent-lint for linting FTL files and autofixing them

[ ] Create a set of rules for formatting, whitespace and indentation, called Fluent Standard.
[ ] Create a tool for reporting linting errors in FTL files.
[ ] Add an option to autofix linting errors.

3. Define a roadmap for Pontoon API and complete one milestone.

[ ] Identify upcoming needs for exposing Pontoon data.
[ ] Document the roadmap on the wiki.
[ ] Complete one milestone on the roadmap.

4. Add a solution for localizing DOM fragments to fluent-react. CARRY-OVER from Q3

[Q3] Review the solution currently implemented in fluent-dom.
[Q3] Research current solutions in other i18n libraries for React
[Q3] Research approaches to parsing HTML in translations
[ ] Implement
[ ] Write tests and documentation

=== Adrian ===

* implement new source input for one-off projects
* scope requirements for Pontoon.Next
* design the architecture of Pontoon.Next
* create a road-map for Pontoon.Next
* build prototypes for key features and challenges of Pontoon.Next

=== Theo (optional) ===