L10n:Adopting a Localization

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

Thank you for your interest in helping Mozilla renew its support of the [Locale Name, code] localization team.

Within the Mozilla ecosystem, there are projects localized into few languages where the original contributor isn't actively contributing. Having new volunteers pick up those localizations is one advantage on how Open Source software development works, and Mozilla in particular.

The details of the Mozilla Localization process are documented here. Please review this site and feel free to ask questions.

First and foremost, Mozilla hands out privileges based on work done. This is true for both getting write access to Mozilla repositories as well as ownership over modules. That means that even in the absence of an active owner, new volunteers need to submit their contributions, get reviews and landing help. If that goes well, the new localizer can request write access to their localization's repository. If that goes well, we can discuss the responsibility of module ownership for the locale. The best way to get going is to start with a bug for a chunk of contribution, attaching it for review. This link helps, pick the right component and describe what you want to get in. Feel free to ask on the #l10n irc channel on irc.mozilla.org, too.

The technical details on how to work on a localization doesn't really change, so you can refer to the documents referred to on L10n. There's some details to pay attention to, though. For one, even if you obviously not agree with their decision to not contribute to that Mozilla project at this point in time, the earlier contributors are still around somewhere, so treat them and their work with respect.

There's one aspect of Open Source that limits your choice in working on the localizations, though, and that's license headers. Most localization teams don't modify those, but if they have, you cannot undo those original modifications from them. Most locales do not have this issue, but you should check before you start. As a side note, not all l10n-tools work well with licenses and if you run into that problem, please address it with the tool author of your choice.

One last quick tip. This is a helpful tool to check how words have been translated in the past in your locale. Click on your locale code and enter a string to see how it has been translated in Firefox by the previous owner. That gives you some context and a quick starting point to find all translations of a particular word in your locale.

Most importantly, there are many people, documents, and tools available for you to take up the leadership, work, and growth of your localization and its community. Please ask any questions along the way so we can grow your locale to a sustainable state together.