1,035
edits
L10n:Becoming an Official Localization: Difference between revisions
L10n:Becoming an Official Localization (view source)
Revision as of 17:30, 18 June 2007
, 18 June 2007→Mozilla Localization Build Categories
| Line 6: | Line 6: | ||
Generally speaking at this stage Mozilla Corporation categorizes this stage as either of: | Generally speaking at this stage Mozilla Corporation categorizes this stage as either of: | ||
*"name" language packs with no source (not in CVS); users are able to get your build through AMO [insert link here to sample], so they'd download either en-US or other related versions and then apply a language pack listed in the [https://addons.mozilla.org/en-US/firefox/browse/type:1/cat:37 | *"name" language packs with no source (not in CVS); users are able to get your build through AMO [insert link here to sample], so they'd download either en-US or other related versions and then apply a language pack listed in the [https://addons.mozilla.org/en-US/firefox/browse/type:1/cat:37 AMO directory] to enable the language you've translated | ||
*"pre-Beta" which means your build would be put in the tree, but not considered "official" in terms of the high level of QA and Build support made available; user has the same experience for this build as for the one above | *"pre-Beta" which means your build would be put in the tree, but not considered "official" in terms of the high level of QA and Build support made available; user has the same experience for this build as for the one above | ||
*"Beta" in shipped-locales; users access to your build from the main Mozilla [http://www.mozilla.com/en-US/firefox/all.html | *"Beta" in shipped-locales; users access to your build from the main Mozilla [http://www.mozilla.com/en-US/firefox/all.html page] except the build is listed as "Beta-language" versus just the name of the language. | ||
Over the next few paragraphs we will better define the process that moves towards official build status. | Over the next few paragraphs we will better define the process that moves towards official build status. | ||
| Line 26: | Line 26: | ||
==Source== | ==Source== | ||
In this stage you are finalizing your language pack and | In this stage you are finalizing your language pack and should expect to have it hosted on [https://addons.mozilla.org/en-US/firefox/browse/type:1/cat:37 AMO]. The critical elements of this stage are to ensure your build has been reviewed by the community (particularly those interested in your language) and is being used on AMO and updated regularly by you. It's important to collect input from any and all sources about your language pack as this is the first time that people will be using it on a day-to-day basis and giving you feedback about the quality of your work. | ||
Something to think about all throughout your work is expanding the people around you who can help you with the language you're working on. This is a good thing and will be useful for you for testing, celebratory events (i.e, launch parties), and possibly web pages or other areas you might need or want help with. We want to help with this and are working on programs to do so. (You can read more about this on Seth's blog about our [http://blog.mozilla.com/seth/2007/06/04/support-update-3/ global program]). | |||
To move forward from this stage you would request a review to make your build "official". | |||
==Review stage== | |||
This stage is your formal request for a review. This means that you are willing to commit over the longer term to sustain your build and in particular to be relied upon by the community and Mozilla to keep up to date with major releases. (Mozilla will do the work for the minor releases). You'll also expect to move from having language pack xpi to a robust build that you might host. We can help you with hosting costs if you need, we have been working on a [http://blog.mozilla.com/seth/2007/06/04/support-update-3/ global program], [mailto:l10n-drivers@mozilla.org email] for this type of support. | |||
* Review the source (checking for completeness and obvious areas) and effectively [http://www.mozilla.org/projects/l10n/mlp_howto.html#mlp_qa QA] your work; further information is available on [http://developer.mozilla.org/en/docs/Create_a_new_localization Mozilla Development Center] | * Review the source (checking for completeness and obvious areas) and effectively [http://www.mozilla.org/projects/l10n/mlp_howto.html#mlp_qa QA] your work; further information is available on [http://developer.mozilla.org/en/docs/Create_a_new_localization Mozilla Development Center] | ||
* if you haven't already done so, file a [http://www.mozilla.org/projects/l10n/registration.html registration bug]. We want this to happen as early in process as possible, because this gives us the notification that you are ready to connect more permanently to us and to your users. Consider it your official signing up moment for being responsible for this effort, think of this as a mid-term commitment to continue with the effort of localization. We consider this a "must" do in order to move forward. This is also the best way to effectively let people across all geographies and user groups (e.g.,Mozilla, Localizer community and users) know what's happening | |||
* You will need to open an l10n account [http://developer.mozilla.org/en/docs/Create_a_new_localization#File_CVS_account_bug| request] (on CVS). This enables Mozilla to create builds for minor updates without involving you. This means the user experience is consistent across the world (or across all of our builds). | * You will need to open an l10n account [http://developer.mozilla.org/en/docs/Create_a_new_localization#File_CVS_account_bug| request] (on CVS). This enables Mozilla to create builds for minor updates without involving you. This means the user experience is consistent across the world (or across all of our builds). | ||
* Create a bugzilla component (so language is created in bugzilla for tracking purposes) | * Create a bugzilla component (so language is created in bugzilla for tracking purposes) | ||
==Incubator Stage== | ==Incubator Stage== | ||