MozillaWiki

L10n:Official Localized Releases: Difference between revisions
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Official Localization =
__NOTOC__{{L10navbar}}<p><br>
A localized official release means that:
# Mozilla creates minor updates from CVS together with the en-US minor releases. [[L10n:Localization Process End#Minor Updates|Details...]]
# Major upgrades, i.e., the shift from Firefox 2 to Firefox 3, is done through contributions of the localization teams. [[L10n:Localization Process End#Major Upgrades|Details...]]
# The local team strengthens and enlarges the community. [[L10n:Localization Process End#Community Building|Details...]]


Following is more detail...
=Maintaining the effort=
Once a L10n team has succesfully launched their first localized build they have a whole world of additional opportunities available to them! By this point they should have:
*a growing L10n community,
*a steady and constant L10n effort in Aurora for each new version release,
*at least one new localized version in the [https://developer.mozilla.org/en/Localization_sign-off_reviews sign-off review process],
*a calendar marking release channel migration dates to stay on top of their Aurora repos,
*a prominant voice in the [http://groups.google.com/group/mozilla.dev.l10n mozilla.dev.l10n], [http://groups.google.com/group/mozilla.dev.l10n.web mozilla.dev.l10n.web], and [http://groups.google.com/group/mozilla.dev.l10n.new-locales mozilla.dev.l10n.new-locales] newsgroups,
*a plan to frequently check their dashboards for new strings to localize,
*a party to celebrate everthing they've accomplished!


== Minor Updates ==
Sometimes schedule changes may arise for a given version release. In such a case, L10n teams must remain up-to-date on the discussions in the newsgroups, as though are the primary platforms for communication from the L10n drivers. We try to communicate well in advance of changing deadlines through those channels.
Mozilla Corporation resources handle minor updates, etc and collaborates with you to complete a release. Minor updates are generated from a stable branch, this means, changes to that branch require approval and are tightly controlled on testing. This helps us to make sure that there are no regressions in minor updates. The corresponding tree rules are mentioned on the [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n l10n branch tinderbox] and announced in the .l10n newsgroup. All changes are documented in bugs, filed by the localizer in their Bugzilla component.


More specifically,
=More opportunities to contribute=
* Patches are approved after technical review by [[User:AxelHecht| Axel]]
Once a L10n team builds up the enough resources to participate in more projects, there are <i>plenty</i> of additional project that they can get involved in!
* Branding changes (e.g., search, RSS, content handlers) are approved by [[User:MicBerman| Mic]]
* Changes to in-product web pages are managed by [http://chevrel.org/fr/ Pascal]


== Major Upgrades ==
Some ideas:
Major updates are done by you. Our next major update is [http://wiki.mozilla.org/Firefox3 Firefox 3]
*Localize other Mozilla products (Firefox Mobile, Thunderbird, SeaMonkey, Boot2Gecko, etc.)
* There are some [http://developer.mozilla.org/en/docs/Create_a_new_localization#Following_your_localization tools] that are likely useful for you in this stage.  
*Localize articles on the [https://support.mozilla.com/en-US/kb/localize-firefox-help Firefox Support site].<br>
* On the occasions when you don't meet the ship deadlines, we try to do everything we can to support you to meet the release dates. We do this by communicating well in advance of deadlines and being clear about module owners and the like. In the case where a deadline is going to be missed, we've considered these as our suggested options:
*Help localize [https://localize.mozilla.org Mozilla Web Sites, Services, and Marketing Campaigns].<br>
* next release as acceptable
*Localize wiki pages related to localization on the [https://developer.mozilla.org/Special:Tags?tag=Localization&language=en&deki_buttons%5Btag_search%5D%5Bsearch%5D=search Mozilla Developer Network wiki](MDN).  
* special cases we may create a delay on being official build status
*Contribute to an [https://developer.mozilla.org/Special:Tags?tag=Localization&language=en&deki_buttons%5Btag_search%5D%5Bsearch%5D=search L10n topic] on the [https://developer.mozilla.org/Project:en/Getting_started MDN wiki].


Mozilla supports the [[Firefox:2.0_QA_Activities:L10n_Test_Plan|quality assurance]] testing of your build
=Community building=
* We're improving our automated testing capabilities and our procedures for human testing, to better support you for Firefox 3
Each L10n team should aspire to have all the [[L10n:Building Blocks|Building Blocks]] for supporting their localization. A prominent contributor named Nukeador has written a [http://www.nukeador.com/29/11/2011/organizing-a-mozilla-community/ good resource for learning about community building]. It contains many ideas for recruiting and structuring a Mozilla community.
* For major upgrades (Firefox 3), we've created a 2-week string freeze before the code freeze of the last Beta to ensure you have sufficient time to implement new changes
* And, we've created new testing tools to provide nightly builds for which you can test your work against and have more dynamic results


== Community Building ==
Mozilla is also working to develop more ways to support your community building efforts. If you feel your team is in need of this type of support please [mailto:l10n-drivers@mozilla.org email] us. We are also working to determine how to assess the health of a L10n team and how we could better support them to develop their team or their skills.
Your team should aspire to a "full-skills team". Meaning all the [[L10n:Building_blocks| building blocks]] for supporting your localization. Mozilla is working to develop more ways to support you to develop your building blocks. Check out [http://blog.mozilla.com/seth/2007/06/04/support-update-3/ Seth's blog] to hear more about our ideas. We've recently invested more [http://jtbatson.blogspot.com/2007/06/welcome-rishi.html resources] to better support your community development efforts. If you feel your team is need of this type of support please [mailto:l10n-drivers@mozilla.org email] us. We are also working to determine how to assess the "health" of a localization team and how we could better support them to develop their team or their skills.


Back to the [[L10n:Localization Process|Localization Process]]
Back to the [[L10n:Localization Process|Localization Process]].
 
[[Category:L10n]]

Latest revision as of 14:59, 19 September 2012


Maintaining the effort

Once a L10n team has succesfully launched their first localized build they have a whole world of additional opportunities available to them! By this point they should have:

  • a growing L10n community,
  • a steady and constant L10n effort in Aurora for each new version release,
  • at least one new localized version in the sign-off review process,
  • a calendar marking release channel migration dates to stay on top of their Aurora repos,
  • a prominant voice in the mozilla.dev.l10n, mozilla.dev.l10n.web, and mozilla.dev.l10n.new-locales newsgroups,
  • a plan to frequently check their dashboards for new strings to localize,
  • a party to celebrate everthing they've accomplished!

Sometimes schedule changes may arise for a given version release. In such a case, L10n teams must remain up-to-date on the discussions in the newsgroups, as though are the primary platforms for communication from the L10n drivers. We try to communicate well in advance of changing deadlines through those channels.

More opportunities to contribute

Once a L10n team builds up the enough resources to participate in more projects, there are plenty of additional project that they can get involved in!

Some ideas:

Community building

Each L10n team should aspire to have all the Building Blocks for supporting their localization. A prominent contributor named Nukeador has written a good resource for learning about community building. It contains many ideas for recruiting and structuring a Mozilla community.

Mozilla is also working to develop more ways to support your community building efforts. If you feel your team is in need of this type of support please email us. We are also working to determine how to assess the health of a L10n team and how we could better support them to develop their team or their skills.

Back to the Localization Process.

Retrieved from "https://wiki.mozilla.org/index.php?title=L10n:Official_Localized_Releases&oldid=471852"