• How do we scale the Mozilla localization community?

    June 5th, 2009 by seth bindernagel with 3 comments »

    Between the release of Firefox 3 and the upcoming release of Firefox 3.5, Mozilla will add twenty-six new localizations to the Firefox’s list of localized versions.  It’s likely that we will ship Firefox in seventy-four locales, not including the en-US version.  What does it take to scale our community and increase our locale count by over fifty-four percent?

    It turns out that many who learn about our growth often ask if we can articulate any of the magic behind this scale.  It’s not really magical, and it’s pretty straight forward.  In fact, I’ve been meaning to write something on my blog about our process to describe the many things that make this possible.  Coincidentally, Greg Bell, who helps run the website Open Logic, learned of our growth and asked me if I’d answer this very question in a post for his site.  This seemed like the best opportunity since Greg provided a deadline that would force me finally to write it.  He and his staff titled the article Go Local, Be Global: Scaling the Mozilla Localization Community and they wrote a very nice introduction about Mozilla.  I hope you find time to read it.

    Of course, it’s quite easy to write a piece like this when we have a remarkable community of contributors.  Special thanks has to go out to the l10n community and l10n-drivers team who have been building for years the foundation that has made this scale possible.  Most of all, Axel Hecht and Pascal Chevrel have been the two Mozilla employees most responsible for our global growth.  Hats of to them.

    Finally, many thanks to Greg for offering me the opportunity to write.  He caught me at the height of our Firefox 3.5 release work, so it took me a few more weeks than expected to write it. Luckily, he let me slip my deadline twice until I finally got this together.

  • Responding to Walt’s rhetorical criticism

    May 29th, 2009 by seth bindernagel with 7 comments »

    If you advance to the two minute thirty-five second point of this interview of Mitchell Baker and John Lilly, you’ll hear Walt Mossberg remark about the quality of Mozilla’s localizations by saying,

    “I have a deep distrust of somebody who I don’t know to be actually responsible for the quality of the end product.”

    We’ve heard that before, haven’t we?  To entertain the point, I’ll answer a question, “Just how do we know that our translated product is high quality?” by linking to several posts (with very brief summaries) as a response to Mossberg’s rhetorical criticism. 

    • Testing the latest localized version of Firefox 3.5 — In this post, I ask our localizers to test a release, with specific steps that each locale can follow.
    • Moving a locale out of beta — This is a basic software release principle.  No, our localizers don’t get a free pass into “official status”.  We give each locale a proper amount of time to bake so the beta users can provide feedback to our localizers.  After feedback is “triaged”, bugs are fixed, and signs of user adoption become obvious, we move a locale out of beta.
    • Localization-QA survey results — At the end of 2008, we conducted a survey to gauge our teams’ testing efforts.  The posted results point us to where localizers might need our assistance.  From this, we have begun an experiment to provide a third-party QA service to help test a sample of our localized versions.
    • Adding contextual information to a localized build –  Some of our localizers even create, share, and use customized tools to help perfect translations

    Perhaps it’s hard to express without sounding naive or idealistic, but maybe there is an important theme that didn’t make Mossberg’s conversation that should be articulated:

    We take localization very seriously.  This is not just a hobby for our community, and many have the battle scars to prove it.  Just ask someone who has stayed up all night to perfect a translation before a code freeze and you’ll understand what I am getting at.  Each of our localizers is keenly aware that greater than fifty percent of our end-users are NOT using an en-US version.  When a localizer is responsible for a translation, the quality of their work impacts a massive amount of end users.  We could ask our German localizer Kadir, whose localized version of Firefox is being used by an estimated twenty-five million people.  Or, Romi, our Indonesian localizer, who’s translated version has climbed to sixty-three percent market share.  That level of impact keeps our localizers sharp and tremendously dedicated.

    Other highlights from the transcript:

    “Walt: 71 of the foreign-language versions of Firefox are written by volunteers. Why should I use a product like that? Lilly says Mozilla has a system for verifying the quality of these other versions and vets them prior to release. Beyond that, users will alert the company to any problems.”

    “Walt: Why wouldn’t it just be better for the consumer to go with the company that’s hired experts to do its translations? Baker: How much software do you really think is great? Walt: Not very much. Lilly: But it’s all written by experts. Walt nods, point taken.”

    NB:  John Lilly mentions that we’ll have seventy-one localizations for Firefox 3.5.  We’re growing everyday!  We are actually going to ship seventy-three localizations for Firefox 3.5′s release candidate, with an outside chance of seventy-five for final release.

  • Koala

    May 26th, 2009 by seth bindernagel with Comments Off

    Many of you may remember our localization intern, Adrian Kalla, from last year.  A dedicated community member before his internship, Adrian returned to school to continue his contribution to Mozilla.  Recently, he approached us with a request to support a project that would help complete his course of studies.  After expanding the idea with Axel, he had a project idea to pursue and the l10n-drivers jumped at supporting such an interesting experiment that Adrian calls “Koala”.

    He will be blogging about his project on a regular basis, but he asked me to post the following initially to describe the idea:

    During my internship at Mozilla last year, I developed a Silme-based “compare-locales” version. It is a command-line only tool, that requires from the user to have experience in working with a console. Well – we all know that a text-interface is not necessarily a user’s first-choice, so Axel came up with a great idea to develop a user-friendly graphical front-end for it.

    Being back at my University, one part of my major is to work on a project, which may be done in cooperation with external companies. This project is officially scheduled for the term directly after the internship – that is, the chance to move Axel’s idea from the ‘ideabox’ to the ‘real’ world.  I see it as a great opportunity to continue my work on Mozilla L10n tools and my major at the same time.   Everything went quickly: Axel defined the project and its details, which was then accepted by my professor as an official university project. Together with my fellow computer science students, namely Adam Kowalewski and Florian Schloegl, we created a project team. And…

    What exactly are we working on?

    Calling the project just a “graphical interface for compare-locales” would underestimate the objectives we have set for it. It will be an extension for the Komodo Edit & Komodo IDE developer-editor/IDE applications, which are based on Mozilla technologies, that will help with the daily work of holding Mozilla localizations up-to-date. Starting with pulling Mercurial repositories, comparing the changes, showing that changes to the user directly in the work files, …, ending with helping during the translation process (e.g. translation-suggestions, syntax highlighting) and committing the changes back to a repository – everything in just one tool.

    We named the extension “Koala”, which stands for “Komodo Advanced Localization Addon”.

    More information will be available soon on http://koala.mozdev.org .

    To accomplish the project, we have a September, 15 (2009 of course ;) ) deadline. But you will hear of us sooner. Stay tuned.

  • Testing the latest localized version for Firefox 3.5

    May 22nd, 2009 by seth bindernagel with 10 comments »

    I posted this to the Mozilla L10n newsgroup, but for maximum coverage, I’ve reposted it on my blog.  Special thanks to Marcia, Axel, and Chofmann the various resources I reference below.

    ——————————————–

    To all of our great community localizers and testers…

    Over the past few weeks, many of our Mozilla community members have done testing and landed fixes for Firefox 3.5 as we close in on our release.  We are now in the last hours before we ship our release candidate that we can comfortably call Firefox 3.5. If you have time this weekend, it is a great opportunity to do some last minute testing for your localization.

    Where to download the latest localized nightly version of the Firefox 3.5

    http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1-l10n/

    Please hammer on these builds mercilessly to make sure that things work well.  If you notice things that worked in Firefox 3.5 beta 4, but do not work in this release, we would like to know about it right away.

    What to Test

    You can run a set of localization test cases by going to Litmus, Mozilla’s testing suite.  This URL will take you to the “l10n run”.

    https://litmus.mozilla.org/run_tests.cgi?test_run_id=36

    If you don’t have a Litmus account, you should be able to create one quickly.  Please email us if you need any help.

    How to report feedback

    Please try filing a bug for your locale with Bugzilla.  The basic set of instructions are below.  If you are not comfortable filing a bug, you can report it to your locale leader who should be listed in the specific locale on this main Teams page:

    https://wiki.mozilla.org/L10n:Teams

    Things to remember when filing a bug in https://bugzilla.mozilla.org/:

    1. Always include the Build ID that you tested on.  If you type about: in the URL bar, this will give you the Build ID.
    2. Always include clear “Steps to Reproduce” the bug.
    3. Always check to see if your bug has already been filed.  This link will help: http://tinyurl.com/2465be
    4. Use the regression keyword if it indeed a regression from a previous release.  And, please tell us in the main comment of the bug if it is a regression from a previous release.
    5. If you happen to crash, please include the Breakpad ID in the bug.  You can get this by typing about:crashes in the URL bar.

    If you don’t wish to file a bug, report issues through http://feedback.mozilla.org or through the mozilla.feedback.firefox.prerelease newsgroup (I just linked to the Google Group).  However, we prefer bugs as feedback since those are easier to track.

    Finally, keep in mind that no comments or questions are off limits.   Please send along any remarks or questions that you think are appropriate at you test.   It’s all appreciated.

    Thanks to all of you for helping test Firefox and making it the browser of choice for millions and millions of people all over the world!

  • Four more locales added for Firefox 3.5 RC1

    May 20th, 2009 by seth bindernagel with Comments Off

    We’ve added four more locales for Firefox 3.5. These include Oriya, Romansh, Spanish (Chile), and Tamil (Sri Lanka).

    Many thanks to Manoj (or), Sarves (ta-LK), Gion-Anrdi (rm), and Emilio (es-CL) for putting in some great effort in the last hours to complete their translations. Although a set of productization bugs still exists for these languages and Staś is working with these folks to resolve them, we’ll still ship the four new locales with Firefox 3.5 RC1.  Malayalam will also join us for this release after translating 148 strings in the final push. ml has been with us in the past but slipped last time.  Welcome back, Ani and Joyce.

    If you’ve been counting, we *should* get up to 75 localizations for the final release of Firefox 3.5, shipping simultaneously across three platforms.  Yesterday, I was skeptical we would not even come close to the number from beta 4.  But, here is what happened…

    Over the evening time in California, we lost a bit of sleep as we checked throughout the night on the status of teams and responded to emails.  After midnight, we noticed that Alexandru (the maintainer of Narro) had seen a couple of localizations with translated strings that hadn’t been pushed back to us.  He sent us one changeset and we waited a bit longer.  At 4:30 AM, Staś got up and landed ta-LK in its repository since the team had not had the chance.  Then, by the 5 AM code freeze, Alexandru committed the Vietnamese team’s final changes.  Axel continued managing that opt-in thread I mentioned in my post yesterday.  He and Staś also helped sort out some Mercurial landings that got a bit twisted around.  By 11 AM in Mountain View, Axel was reporting on code freeze to the Firefox product team.  We learned when builds would start (Sunday May 24), buying us a bit more time to finish our l10n, allowing a few more locales to make it in the process.  We’re not finished yet, but we are very close…

    This morning the l10n-drivers were chatting about how every time we go through a release, we are blown away by the responsiveness, dedication, and professionalism of this group of volunteers.  Hats off to the localizers one more time.