L10n:Becoming an Official Localization: Difference between revisions

L10n:Becoming an Official Localization (view source)

Revision as of 03:46, 9 July 2007

39 bytes removed , 9 July 2007

no edit summary

Mic

1,035

edits

@@ Line 11: / Line 11: @@
 * language-specific major upgrade to the next versions
-There are a bunch of technical measures that help us achieve these goals, namely
+There are technical measures that help us achieve these goals;
 ; Use the mozilla cvs server : To create builds Mozilla needs access to your source, this happens through our [http://lxr.mozilla.org/l10n cvs repository]. [[L10n:Localization Process Middle#Landing_in_CVS|Details...]]
-; Localize some web content : This isn't all of the mozilla.com website. We currently only offer the localization of the [[L10n:Web parts|Web parts]]. If your interested in translating the mozilla.com website, we're interested, too, but haven't figured out a good set of pages yet.
+; Localize some web content : This isn't all of the mozilla.com website. We currently only offer the localization of the [[L10n:Web parts|Web parts]]. If your interested in translating the mozilla.com website, we're interested, too, but we haven't figured out the right set of pages yet.
 ; Fix bugs in your localization : There will be a bugzilla component for your localization, in wich Mozilla and community members can file bugs on your localization. We'll be working together to fix those, land them, test them and ship them with the next (minor) release.
-; Organize further QA : There will be further test requirements, which the localization team and its community need to lift with help from the Mozilla L10n and QA teams.
+; Organize further QA : There will be further test requirements, which the localization team and its community are responsible for with help from the Mozilla L10n and QA teams.
 ; Follow the development : Localizers need to follow the announcements in .l10n, so that they know when to work on minor and major versions.
@@ Line 23: / Line 23: @@
 To become an official localization, you will need to have a source for your localization and, if possible, some reviews of your work by native speakers. If you have some of the [[L10n:Building Blocks|Building Blocks]] filled, that's a plus, too. You should have a registration bug filed now, and that bug should list
-; what do you want to release : Please mention your language, the language code, and the product/products you're localizing.
+; what you want to release : Please mention your language, the language code, and the product/products you're localizing.
 ; who you are : We'll need your name, and the name of your peers. A link to your [[L10n:Teams|Teams]] page would be good, too.
 File a registration bug using this [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&version=unspecified&component=Registration%20%26%20Management&rep_platform=All&op_sys=All&priority=--&bug_severity=normal&target_milestone=---&bug_status=UNCONFIRMED&assigned_to=registration%40localization.bugs&qa_contact=registration%40localization.bugs&cc=&bug_file_loc=http%3A%2F%2F&short_desc=&comment=&commentprivacy=0&keywords=&dependson=&blocked=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug bug link], which sets the right component. If multiple teams try to submit a localization, this will be resolved within a single registration bug, so before filing a new registration bug, make sure that there isn't one already. We strongly prefer that everyone cooperates to make a better and stronger team.
-Consider this your official signing up moment for being responsible for this effort and think of it as a mid-term commitment to continue with the effort of your localization. Mozilla is a community project and as such, we understand that your schedule has more on it than just Mozilla. Localizing Mozilla is an ongoing effort nevertheless, and if a localization community runs short on manpower, we need your help in getting new volunteers on board.
+Consider this your official signing up moment for being responsible for this effort, it is a mid-term commitment to continue with the effort of your localization. Mozilla is a community project and as such, we understand that your schedule has more on it than just Mozilla. Localizing Mozilla is an ongoing effort nevertheless, and if a localization community runs short on manpower, we need your help in getting new volunteers on board.
 You should attach your localization source to this bug for review. Zips usually fail to work due to their file size as a single attachment, but tarballs do. You can create one by using
@@ Line 35: / Line 35: @@
 == Reviews ==
-Mozilla will take a look at the reviews by native speakers that you point to in the bug. In addition to that, we'll do an user-experience and a technical review. The technical review is done by seasoned Mozilla staff to ensure that there is a promising effort to create a full source localization of the product in question by evaluating the technical correctness and localization coverage. The user-experience review will make a call whether a particular language or dialect is better served with a language pack instead of a full product localization. We may prioritize requests to match them with the resources inside the QA and release team at Mozilla. Part of the user experience review is also some linguistic assessment of the language or dialect in question.
+Mozilla will take a look at the reviews by native speakers that you point to in the bug. In addition to that, we'll do a user-experience and a technical review. The technical review is done to ensure that there is a promising effort to create a full source localization of the product in question by evaluating the technical correctness and localization coverage. The user-experience review will make a call whether a particular language or dialect is better served with a language pack instead of a full product localization. We may prioritize requests to match them with the resources inside the QA and release team at Mozilla. Part of the user experience review is also some linguistic assessment of the language or dialect in question.
 These reviews are done to ensure that the quality of the localization work meets the high standards people have come to expect when they download a Mozilla product from the official [http://www.mozilla.com/en-US/firefox/all.html Mozilla site]. A successful review gives the OK for moving from a language pack to a fully localized product.
@@ Line 42: / Line 42: @@
 = Landing in CVS =
-Mozilla uses CVS to organize the source code changes. You would want to dig a little into version control systems, with a focus on CVS and branches.
+Mozilla uses CVS to organize the source code changes. For this stage, you would want to dig a little into version control systems, with a focus on CVS and branches.
 == CVS write access ==
@@ Line 60: / Line 60: @@
 === Productization ===
-We'll jointly work on  your language-specific search engines, RSS readers, feeds and [http://wiki.mozilla.org/Firefox3/Product_Requirements_Document#Content_handling| content handlers]. This way users have not only a browser that works in their language but also have features localized specifically for their language like Search and RSS readers.
+We'll jointly work on  your language-specific search engines, RSS readers, feeds and [http://wiki.mozilla.org/Firefox3/Product_Requirements_Document#Content_handling| content handlers]. This way users not only have a browser that works in their language but features localized specifically for their language like Search and RSS readers.
 We'll file a separate bug to track this step, in which you propose what local options you'd like to include and we collaboratively review it and once it's approved, you check in the changes.
@@ Line 77: / Line 77: @@
 * This is the step when your localization gets on the branch
 * We create a bug for build automation
-* once this step is complete your localization will then be building on branch
+* Once this step is complete your localization will then be building on branch
-* evaluations are then done by you to ensure all is done the way it's supposed to be. You should incorporate your community if you can for testing here as we all want the user experience to be the best and the crux of this stage is making sure all the translations are completed and "right".
+* Evaluations are then done by you to ensure all is done the way it's supposed to be. You should incorporate your community if you can for testing here as we all want the user experience to be the best and the crux of this stage is making sure all the translations are completed and "right".
 == Ship Beta ==
 * This is our QA stage, it is heavily dependent on a community review
-* Effectively we're asking and you're asking to get as much community feedback as you have access to to review these builds. We want to make sure users will be very happy with the quality of the language translation and the choices we've made to reflect functionality like search, RSS, etc in their language.
+* Effectively we're asking and you're asking to get as much community feedback as you have access to, to review these builds. We want to make sure users will be very happy with the quality of the language translation and the choices we've made to reflect functionality like search, RSS, etc in their language.
 * There are no automatic links to your localization on http://getfirefox.com yet, however it is listed as a Beta on http://www.mozilla.com/en-US/firefox/all.html.
@@ Line 88: / Line 88: @@
 = Official Release =
-You now have an official release of your localized Mozilla product. [[L10n:Localization_Process_End|Official Build]]s come with more possibilities and tasks, which deserve a separate page.
+You now have an official release of your localized Mozilla product. [[L10n:Localization_Process_End|Official Build]]s come with more possibilities and tasks, which deserves a separate page.