L10n:Localization Process: Difference between revisions
No edit summary |
|||
| Line 12: | Line 12: | ||
* get ready to turn our will into action and be reviewed by team | * 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 | 2 Preparation for creating your language begins and effectively you've entered the [[L10n:Localization_Process_Middle| MIDDLE]] of the process | ||
* review skills required (help | * Many types of skills are required to build your new version of Firefox | ||
** 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 | |||
** 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 | |||
** 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 | |||
**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 | 3 Localizations gets plugged into our build/release process for automation | ||
* automation happens here | * automation happens here | ||
Revision as of 13:36, 2 May 2007
{DRAFT}
End to End Firefox Localization Process Overview
Our 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
The 5 step process to localizing Firefox. Click on the links to get the more detailed view:
1 Volunteer appears and community STARTs to form
- realization that Firefox needs a new language
- if we form a community we can solve this problem
- 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 MIDDLE of the process
- Many types of skills are required to build your new version of Firefox
- 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
- 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
- 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
- 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
- automation happens here
4 Builds are prepared for final release and testing (what we refer to as Beta)
- 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 END
- offered automatically to people coming to our site
- celebration/party
- tell other people about your experience