L10n:Localization Process: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Some cleanup)
 
(63 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{DRAFT}
{{L10navbar}}
__NOTOC__
__NOTOC__
=End to End Firefox Localization Process Overview=
Our [[L10n:Home_Page|L10n]] objective is to help you get a community formed in your country and launch as many new languages/locales as we can, our current goal is to get to 100. This wiki page is meant to give you, as a new volunteer, an overview of what’s involved from start to finish of a new build and then ongoing releases. We try to keep it short and sweet, (10 minutes of reading or less ;-).


=Very simple overview=
Mozilla's localization (L10n) objective is to improve the world by culturally adapting Mozilla products by region and locale and offering them to every user in every region throughout the world. By doing so, we create a world where the open web exists beyond linguistic, cultural, and geographical boundaries. We also pride ourselves on making sure that each user will love their experience with Mozilla products, regardless of language, culture, and region. A user has an awesome experience with Mozilla by learning about, discovering, installing, using, and continually updating their Mozilla products to their latest released versions.
The 5 step process to localizing Firefox. Click on the links to get the more detailed view:


1 Volunteer appears and community [[L10n:Localization_Process_Start| STARTs]] to form
As an open source project, we work closely with communities of volunteer contributors who also care about the fate of the open web. Their contributions to our L10n effort make having an open and accessible web possible. Without their help, the web and Mozilla would not be what it is today. Working together, we can open the web to all and protect user rights all over the world.
* realization that Firefox needs a new language
 
* if we form a community we can solve this problem
The nature of the Mozilla L10n program is deeply rooted in collaboration between volunteer localizers and a lean team of Mozilla staff called the L10n drivers. The process that makes this collaboration efficient and strong can be described in four stages: an initial desire to localize Firefox, the actual localization work, pushing localized versions toward official release status, and maintaining Firefox while jumping into more projects.
* get ready to turn our will into action and be reviewed by team
 
2 Preparation for creating your language begins and effectively you've entered the [[L10n:Localization_Process_Middle| MIDDLE]] of the process
<div style="border-radius: 50px; width: 25%; background-color: #4AA02C; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px"><h2>[[L10n:Starting a localization|Starting a L10n effort]]</h2>A L10n community is born.</div>
* Many types of skills are required to build your new version of Firefox
<div style="border-radius: 50px; width: 25%; background-color: #A2BFF4; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px"><h2>[[L10n:Localizing a project|Localizing a project]]</h2>How Mozilla and you localize Firefox.</div>
** Translations skills: a lot of work is in translating typically from English to your language web and client application content, this is considered a P1 in terms of the basic thing you need to complete your work
<div style="border-radius: 50px; width: 25%; background-color: orange; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px"><h2>[[L10n:Becoming an Official Localization|Localized release schedule]]</h2>Putting your localization into the user's hands.</div>
** Technical/Engineering/Testing skills: to view, edit and review code, understand how the build and release process of Mozilla works, and be passionate about details to ensure that your build is working the way you would expect it to, this is considered a P1 in terms of another basic element you need
<div style="border-radius: 50px; width: 92%; background-color: #C0C0C0; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px"><h2>[[L10n:Official Localized Releases|Post-release]]</h2>More ways to contribute after your first release.</div>
** Community development skills: it is always good to have more people in the community who can help you for example, make some product decisions, test your new build, spread the word, and come to build and launch parties ;-). This is considered a P2 in terms of basic skills that are required
<div style="border-radius: 10px; background-color: white; border: 3px solid; display: block; padding:20px; margin-top: 20px;">These four stages make up the L10n program. To learn more about any of these, click on any of the links above. To get the big picture, we suggest you start with the green bubble and move from stage to stage.</div>
**4-marketing and PR skills: once you've built your new version we'll want to help you let the world know that there is a new version available, we are currently working on a "buffet" of items to help you here and will write more on this soon. This is considered a P2 in terms of basic skills required.
 
**5-support: (Mic note to Axel/Choffman: need help here) (P3)
 
3 Localizations gets plugged into our build/release process for automation
Since we actively promote open source values, we always try to improve our efforts and welcome your input. Please tell us what you think by joining the discussion either on the [http://www.mozilla.org/community/developer-forums.html#dev-l10n L10n forum] or the [http://irc.mozilla.org/#l10n IRC #l10n channel].
* automation happens here
 
4 Builds are prepared for final release and testing (what we refer to as Beta)
[[Category:L10n]]
* fix bugs, get ready for many reviews, get plugged in and prepare yourself
* daily builds start happening and this is an iterative process to get a candidate for final release
5 "Releases happens" for your locale - the [[L10n:Localization_Process_End| END]]
* offered automatically to people coming to our site
* celebration/party
* tell other people about your experience

Latest revision as of 14:50, 22 October 2013

Mozilla L10n Main | Join Mozilla | Overview | L10n Drivers | Communities | Meetings | Blog | Resources


Mozilla's localization (L10n) objective is to improve the world by culturally adapting Mozilla products by region and locale and offering them to every user in every region throughout the world. By doing so, we create a world where the open web exists beyond linguistic, cultural, and geographical boundaries. We also pride ourselves on making sure that each user will love their experience with Mozilla products, regardless of language, culture, and region. A user has an awesome experience with Mozilla by learning about, discovering, installing, using, and continually updating their Mozilla products to their latest released versions.

As an open source project, we work closely with communities of volunteer contributors who also care about the fate of the open web. Their contributions to our L10n effort make having an open and accessible web possible. Without their help, the web and Mozilla would not be what it is today. Working together, we can open the web to all and protect user rights all over the world.

The nature of the Mozilla L10n program is deeply rooted in collaboration between volunteer localizers and a lean team of Mozilla staff called the L10n drivers. The process that makes this collaboration efficient and strong can be described in four stages: an initial desire to localize Firefox, the actual localization work, pushing localized versions toward official release status, and maintaining Firefox while jumping into more projects.

Starting a L10n effort

A L10n community is born.

Localizing a project

How Mozilla and you localize Firefox.

Localized release schedule

Putting your localization into the user's hands.

Post-release

More ways to contribute after your first release.
These four stages make up the L10n program. To learn more about any of these, click on any of the links above. To get the big picture, we suggest you start with the green bubble and move from stage to stage.


Since we actively promote open source values, we always try to improve our efforts and welcome your input. Please tell us what you think by joining the discussion either on the L10n forum or the IRC #l10n channel.