MozillaWiki

L10n:Official Localized Releases: Difference between revisions

No edit summary
 
(15 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Official Build==
__NOTOC__{{L10navbar}}<p><br>
An [[L10n:Home_Page| L10n]] official build means that:


1- Mozilla Corporation resources handle minor updates, etc and collaborates with  you to complete a release. More specifically,
=Maintaining the effort=
* An approval for change requests is led by [[User:AxelHecht| Axel]]
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:
* Code/string/catch ups are also approved by Axel
*a growing L10n community,
* Branding changes (e.g., search, RSS, content handlers) are approved by [[User:MicBerman| Mic]]
*a steady and constant L10n effort in Aurora for each new version release,
* Changes to in product web pages are approved by [http://chevrel.org/fr/ Pascal]
*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!


2- 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.
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.


3- Major updates are done by you. Our next major update is [http://wiki.mozilla.org/Firefox3 Firefox 3]
=More opportunities to contribute=
* Here are some [http://developer.mozilla.org/en/docs/Create_a_new_localization#Following_your_localization tools] that are likely going to be useful for you in this stage.
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!
* There are occasions when localizers don't meet the ship deadlines, we try to do everything we can to support you to meet the release dates. Mozilla (we) does 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:
* next release as acceptable
* special cases we may create a delay on being official build status


4-Mozilla supports the [[Firefox:2.0_QA_Activities:L10n_Test_Plan quality assurance]] testing of your build
Some ideas:
* We've instituted a new testing platform and [[L10n:Testing| protocols]] to better support this for Firefox 3
*Localize other Mozilla products (Firefox Mobile, Thunderbird, SeaMonkey, Boot2Gecko, etc.)
* We've also created a 2-week code freeze before Beta 2 to ensure you have sufficient time to implement new changes
*Localize articles on the [https://support.mozilla.com/en-US/kb/localize-firefox-help Firefox Support site].<br>
* And, we've created new tools [Axel help here] to provide nightly builds for which you can test your work against and have more dynamic results
*Help localize [https://localize.mozilla.org Mozilla Web Sites, Services, and Marketing Campaigns].<br>
*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).
*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].


Back to [[L10n:Home_Page]]
=Community building=
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.
 
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.
 
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"