L10n:Localization Process: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Some cleanup)
 
(57 intermediate revisions by 6 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, so what you'll find here is an overview and then links to more detail. This way if you're at the start you can jump to details about starting, same for the middle and end. (This page is about a 5 minute read, but the details are much longer).
I am always looking for feedback to make this page better, so if you have something to say good or bad please post to the forum or file a bug [Question: what's best route for feedback?] .


=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.  
* This usually happens when there is a realization that Firefox is missing another language and there is a conclusion that if we form a community we can solve this problem, so we all get ready to turn our will into action.
 
2 Preparation for creating your language begins and this means you've entered the [[L10n:Localization_Process_Middle| MIDDLE]] of the process
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.
* By now you've searched if you're creating something new or joining an existing team and you've read a lot of the documents to give you an idea of what's involved technically to build the Mozilla product in the language of your choice. This stage is the heavy lifting of creating your build, and we're here to help you as much as possible.
 
3 Localizations gets plugged into our build/release process for automation
<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>
* This is a nice time in the sense that you don't need to do much if any work to maintain your build. Once it gets plugged in all new minor releases are automatically updated. Your job is to make sure we don't break anything in your release ;-)
<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>
4 Builds are prepared for final major release and testing (what we refer to as Beta)
<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>
* During a major release e.g., Firefox 3 (and not release 2.0.0.4) we will ask you to fix bugs, get ready for many reviews, get plugged in and prepare yourself for the work required to ensure your code makes it into the tree for that major release
<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>
* You can expect daily builds start happening as this is an iterative process to get a candidate for final release
<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>
5 "Releases happens" for your locale - the [[L10n:Localization_Process_End| END]]
 
* When this happens, your build will be offered to people coming to the main Mozilla site as one of the drop down language choices
 
* We like to celebrate success at Mozilla so we typically try to organize world wide parties to mark a major release. For Firefox 2 the team in Paris organized a huge party where people had lots of fun
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].
* We would also like you to tell other people about your experience so that we can grow our Localizer and Developer community so we can do this all over again :-)
 
[[Category:L10n]]

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.