When French Mozillians join in Paris Office to translate all over a week-end, they call it locasprint: French contributors are working and have fun together in the same place to improve French user experience of every Mozilla product. Here is a quick report of our recent #4 Locasprint.
Twice per year, Mozillians from around the world are invited to attend All Hands work week. All Hands is an opportunity for both paid and volunteer staff from all functional areas to meet together to solve problems, brainstorm new goals, and find ways to make the Mozilla mission a reality. For the localization functional area, All Hands gives us a chance to collaborate on resolving challenges in the l10n process, discuss community needs, and start new programs within the functional area. Below is an overview of the highlights and l10n-specific sessions that were held in Orlando. More information about many of these sessions will be made available in the coming weeks.
This cycle (Fx45)
- Beta (44) sign offs for *already shipping locales* must be completed before 13 January.
- Aurora (45) sign offs must be completed before 25 January.
- Approximately 186 new strings landed in Firefox Aurora desktop and 64 for Fennec Aurora (unshared).
- devtools is now in its own root directory within l10n repos – https://bugzil.la/1182722
- 40% of the new strings in desktop are in devtools and DOM. 17% are for the Firefox Hello client. Please see https://www.mozilla.org/en-US/firefox/45.0a2/auroranotes/ for more info.
- 19% of the new strings in Fennec are related to content blocking. 41% are for Fennec preferences. 8% are for the home screen. We’ll see a couple of Firefox Account strings land today (see https://bugzilla.mozilla.org/show_bug.cgi?id=1220904 ). Please see https://www.mozilla.org/en-US/firefox/android/45.0a2/auroranotes/ for more information.
Last 2 cycles
- 84% of all locales shipped signed off updates of Firefox 42 on desktop. This is a massive 17% increase in locale coverage between Firefox 41 and Firefox 42!
- 80% of all locales shipped signed off updates of Fennec 42 on Android. This is a 6% increase in locale coverage between Fennec 41 and Fennec 42!
- 66% of all locales shipped signed off updates of Firefox 43 on desktop. This is an 18% decrease in locale coverage between Firefox 42 and Firefox 43.
- 62% of all locales shipped signed off updates of Fennec 43 on Android. This is an 18% decrease in locale coverage between Fennec 42 and Fennec 43.
- We’re also looking forward to seeing the Lao and Romansh localization teams launch their first Mozilla localizations in Firefox for Android soon.
At the beginning of October, Axel and I took a trip to Istanbul to organize a new l10n hackathon. Is there a more iconic place than a city extending over two continents, with such diversity of culture, to host a localization event?
The target for these meetings is to gather key l10n contributors in the region, bring them up to speed on the latest updates regarding Mozilla, and understand their team’s health and perspectives.
At this event, hosted by a local hacking space named Iskele47, we had representatives from five languages: Azerbaijani, Kazakh, Russian, Turkish, and Uzbek.
(Blog post by Théo Chevalier)
Firefox OS is distributed across several countries and quickly expands throughout Africa. For many people, Firefox OS devices will be their first phone. This was an opportunity for Mozilla to provide phones in languages that are too often ignored or not well supported by other companies.
For many people, it will also be the first time they can get a phone that speaks their language. We are excited about it, localizers are excited about it, everyone is excited about it. With the recent addition of new African languages, Firefox OS 2.2 supports up to 97 languages – 40 of which are complete translation-wise!
From our own experience, we learned that building communities of localizers in Africa is extremely hard, and we failed many times. Even running on-ground events cannot guarantee people will be able to work together on the long term. We realized that connectivity is a major issue, though not the only one.
So during the summer we reached out to several people – most of them come from an Open Source background and have contributed already to other projects – explaining to them what we were trying to achieve with Firefox OS in Africa. We provided them communication channels and general support to start localization activities and get them up and running. We’ve been amazed to see communities growing up, especially around three languages: Bambara, Malagasy and Wolof.
Arky, Delphine, Peiying, and I have just returned from spending a spectacular week at an event that is a first for the Mozilla Localization community: a gathering for Right-to-Left (RTL) localization communities! This was a very unique event, not only because it was the first hackathon dedicated to RTL issues, but it was also one of the few hackathons we’ve arranged outside of any of the RTL localization communities’ home countries. The Sinhala localization team hosted the event and were very welcome LTR participants within an otherwise RTL event.
A unique event
Never before have we been able to organize an event specifically for RTL. Being gathered together in Sri Lanka created a very unique opportunity to hear about RTL issues from a variety of perspectives. Additionally, being that half of the Persian l10n community is based in Iran, none of us had previously had the chance to meet and spend time with them. We were very fortunate to bring our Iranian Mozillian friends to this event and learn of their efforts to localize Firefox into their native language. Finally, we were pleased to organize the first meeting of the complete Urdu l10n community. I use the term “complete” because the Urdu l10n community is spread across India and Pakistan. They had made attempts to gather together in the past, but had been unsuccessful. Meeting in Sri Lanka gave us this opportunity and the full team was happy to be together for the first time.
RTL l10n communities at Mozilla
Firefox desktop is the only Mozilla product that has RTL support explicitly developed into it. Over the years, RTL support has been a desired feature in Mozilla’s mobile products, but our expertise and sustainable plans for it have not been able to culminate in fully supported RTL Fennec or Firefox OS products. Firefox OS has inched closer and closer to this reality and many within the Arabic and Urdu communities have dedicated time to testing RTL bugs and improving the support within that platform. We organized this hackathon for two reasons: 1) to include these locales in the list of teams we aimed to meet with in person during 2015; 2) to bring RTL localizers/users together in a room to triage bugs, learn how to test RTL issues, and establish a taskforce to be more involved in RTL across multiple Mozilla projects.
RTL hackathon activities
The agenda for this hackathon can be found in the Mozilla wiki. Within the wiki, you’ll find the agenda, as well as all of the etherpad notes that were taken during the event. These notes not only covered the morning discussions, but also provide an overview of the Arabic, Urdu, Persian, and Sinhala l10n community status as of October 2015. The agenda covered many of the same topics that (if you’ve been following along throughout the year) can also be found on the agendas of other hackathons. The key difference between this hackathon and others was how the free time in the afternoon was spent. Nearly all of the l10n teams participating in the hackathon were up-to-date on their product l10n projects for the 42 release. During their free time, they localized web parts content, initiated new l10n projects (e.g., the Persian team started localizing Firefox OS 2.5), and formed an RTL taskforce.
It has become obvious to the various RTL communities that the creation of an RTL task force is needed in order to drive the RTL effort onwards.Participants (mostly developers) from Arabic, Persian and Urdu teams have agreed that the RTL task force needs to be first and foremost a global task force – and that they can then address the possible RTL differences from one language to another as they come.
We have started to form a couple goals for this task force:
- Planning and working on creating a seamless RTL experience across Mozilla products
- Identify and study possible differences in RTL across languages
- Fixing bugs in Fennec: RTL tracker bug for RTL Fennec for Android — https://bugzilla.mozilla.org/show_bug.cgi?id=702845
- Finding and filing bugs in Fennec
- Fixing bugs in Firefox OS current master- Meta bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1179459
- Finding and filing bugs in FirefoxOS (under FirefoxOS > Gaia:component)
In order to get everyone on the same page and start working actual dev work, we have agreed that an RTL hackathon should take place soon, in order to have presentations on best coding practices and then do some hands-on bug fixing. This will also be the opportunity to define and prioritize the RTL task force’s goals.
With the creation of this task force, our next action items are to create tools to support this community (irc channel, wiki pages, mailing list, etc). Please stay tuned for progress on this great initiative!
Our host country & community
The Sinhala localization team in Sri Lanka was an amazing host community. They helped to select our accommodations, introduced us to delicious Sri Lankan food, and even took us site seeing and shopping. They introduced us to their culture, their home, and even brought us out to witness a large, 4-hour long Buddhist parade through Colombo which included Asiatic elephants! Peiying even got to pet one 😉 We had a great time and look forward to the Sri Lanka community inviting us back.
In a previous blog post on my personal blog, I described the unique sentiment that carried through the LATAM hackathon we held in Lima, Peru in June 2015. I won’t rewrite that here, but I think that Delphine, Guillermo Movia, and Juan Becerra would agree when I say that the event seemed to represent the bringing together of old friends to serve those users who spoke their native languages; whether all of these Mozillians were friends before this event or not, they all left with a depth of friendship that usually requires years to forge. It was truly special to be a part of and see how localization could bring together people from over 2 different continents.
This blog post is actually quite late, but doesn’t make it less important. As with other l10n hackathons, the agenda followed the same format: group discussion in the morning, free time in the afternoon. The discussions were phenomenal! Thanks to Marcus Saad for being our notetaker, we have all of the discussion notes (in an etherpad) linked to the hackathon’s wiki page.
This time around, I want to highlight what I felt were some of the most noteworthy accomplishments by the l10n group in both discussion time and free time:
– L10n tool workflows were successfully understood by all present. This led to some with more technical skills becoming interested in hacking on Pootle and helping to resolve outstanding bugs within that system.
– Sustainable l10n team organization was explored in a variety of different ways. We discussed what a successful team org could look like for small (1-2 people), medium (5-6 people), and large l10n communities. We also discussed that there are always ways to make room for new localizers within a team’s organization through project, module, and rights assignment.
– Concerns about l10n workshops and interactions between localizers and Mozilla Reps were discussed, with ideas of how to improve and strengthen those relationships.
– All locales presently shipping official l10n projects were able to sign off on products and focus time on web parts l10n.
– Mozilla Nativo v1.2 was born! Their purposes and goals were refined, having committed to change their strategy away from focusing on recruitment of l10n teams for all indigenous Latin American languages and toward focusing on sustaining and supporting 5 existing teams through the process of shipping their first localizations.
– Some ideas about creating l10n workshops in Brazil were discussed, with timelines for how to introduce these ideas to the Brazil l10n team as a whole.
– The Maya Kaqchikel team was tasked with identifying a launch version goal for their localization of Firefox for Android.
– The Zapotec l10n team was able to have repos and automated builds set up for their l10n of Firefox OS.
– The Paraguayan Guaraní and Bolivian Guaraní l10n teams were able to meet and compare both similarities and differences between their languages and their efforts. The Paraguayan l10n team came away with a strong strategy for approaching their l10n work with sustainability in mind (creating l10n resources first, as well as empowering more community members with reviewer and translator rights).
These lists certainly do not contain the full list of what was completed or accomplished by meeting together, but the time was certainly well spent. Our Peruvian hosts were incredible. Absolutely incredible. We sincerely thank the Reps in Peru for their support and involvement. This event couldn’t have happened without you.
Here are some photos taken at the event. Credit goes out to Juan Eladio Sanchez for his fantastic photo skills 🙂
Thank you all for your great work with Firefox 41 and 42. Here’s an outline of what is currently in Aurora this cycle (43) and what we accomplished together last cycle. Note that in light of what we learned with the report’s information last time, we’re attempting to improve how we identify new strings each release. If you see something that seems off, please call it out:
This cycle (Fx43) — 22 September – 2 November
– Beta (42) sign offs for *already shipping locales* must be completed before 21 October.
– Aurora (43) sign offs must be completed before 2 November.
– Approximately 165 new string changes landed in Firefox Aurora desktop and 49 for Fennec Aurora exclusively (unshared).
– 35% of the new strings in desktop are in devtools and DOM. 21% are for the Firefox Hello client. 12% have to do with preference menu settings. Please see https://www-dev.allizom.org/en-US/firefox/43.0a2/auroranotes/ for more info.
– 27% of the new strings in Fennec are related to Firefox Accounts. 16% are for the Fennec first run screens. 14% are about bookmarks. Additionally, this bug may be breaking string freeze soon – https://bugzilla.mozilla.org/show_bug.cgi?id=1207108 .Please see https://www-dev.allizom.org/en-US/firefox/android/43.0a2/auroranotes/ for more information.
Last cycle — 11 August – 21 September
– 63% of all locales shipped signed off updates of Firefox 41 on desktop. Congratulations to everyone who signed off and shipped this last cycle! Sadly, this is a 12% decrease in locale coverage between Firefox 40 and Firefox 41.
– 74% of all locales shipped signed off updates of Fennec 41 on Android. Congratulations to everyone who signed off and shipped this last cycle! Sadly, this is a 4% decrease in locale coverage between Fennec 40 and Fennec 41.
– Please congratulate the Croatian team on launching their first localization of Firefox for Android with version 41!
– We’re also looking forward to seeing the Purépecha, Kaqchikel, and Lao localization teams launch their first Mozilla localizations in Firefox for Android soon.
Thank you to everyone for all of your dedication and hard work this last sprint. As always, if you note anything missing in these reports, please let me know.
Bucharest, Romania was the excellent host of the 5th Mozilla Balkans Community Meet-up. The 2-day workshop took place at the end of May in a similar form as previous Balkans events that were kick-started back in 2010.
The aim of these gatherings is to enable Mozilla communities in the Balkans to share and learn from each other’s experience working on the Mozilla Project, improve collaboration in the future, and work on specific tasks.
Having attended all but one Mozilla Balkans meeting, I feel confident in congratulating Ioana Chiorean for a brilliant job she did working on her specific task – organizing the whole thing. Everything from transportation, accommodation and venue to the drinks out in the open during the Eurovision Song Contest was flawless. Mersi, Ioana!
Invited were lead contributors from 8 Balkans communities: Albanian, Bulgarian, Croatian, Greek, Macedonian, Romanian, Serbian, and Slovenian. Members of Mozilla staff from 4 different functional areas were also present: Participation Team, Quality Assurance, Support, and Localization.
One of the 5 goals of the Mozilla Balkans community reads Ensure that Firefox and Thunderbird are localized into every Balkan language. While the Thunderbird part may sound slightly outdated as the goal, it clearly shows how important Localization is in this part of the World. So Pike, Flod and I basically went to Bucharest to see how we’re fulfilling this goal.
We talked to each L10n team attending the meet-up separately to hear their feedback on our tools and translation workflows. One of the questions raised was why do we have so many tools. Well, this problem is now solved. 🙂 We also provided some ideas on how to plan upcoming work regarding product roadmaps and schedules and recruit new community members.
I found discussions with localizers, both formal and informal, very valuable for the feedback on work I’m personally engaged with. I hope other participants agree with me that such events not only answer questions, but also make us more motivated.
Here’s to the next Balkans Meet-up!
Thank you all for your great work with Firefox 40 and 41. Here’s an outline of what is currently in Aurora this cycle (42) and what we accomplished together last cycle:
This cycle (Fx42) — 11 August – 21 September
– Beta (41) sign-offs for new locales must be completed by 2 September.
– Beta (41) sign offs for already shipping locales must be completed before 9 September.
– Aurora (42) sign offs must be completed before 21 September.
– Approximately 394 new string changes landed in Firefox Aurora desktop and 87 for Fennec Aurora exclusively (unshared).
– 100% of the Firefox desktop string changes are showing in the dashboard as new strings/files that need translation, however, many of these strings are part of devtools refactoring (i.e., they were moved from one location to another, in several cases existing strings got new IDs). For those of you working directly with HG, this will be helpful to understand these changes: https://hg.mozilla.org/mozilla-central/rev/3301c85aa671 . For those of you working on Pootle, the system’s translation memory should automatically provide you with translation matches as suggestions from when you translated these strings previously.
- ~30% of the new strings in devtools.
- ~27% are in dom.
- ~16% are related to privacy settings, tracking protection, and private browsing.
- ~7% are related to password management.
- ~6% are related to Firefox Hello (loop) and Firefox Accounts.
- Finally, about 4% are related to WebRTC.
Please see https://www.mozilla.org/en-US/firefox/42.0a2/auroranotes/ for more info.
– 68% of the Fennec strings changes are new strings/files that need translation.
- 15% of those new strings are related to performing remote operations in the browser.
- ~17% of them are related to login prompts and credential management.
- ~40% of them are related to private browsing, tracing protection, and privacy settings.
- Finally, 13% of them are related to mixed content and tabbed browsing.
Please see https://www.mozilla.org/en-US/firefox/android/42.0a2/auroranotes/ for more information.
Last cycle — 29 June – 10 August
– 75% of all locales shipped Firefox 40 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is a 7% increase in locale coverage between Firefox 39 and Firefox 40! Congratulations!
– 78% of all locales shipped Fennec 40 on time. Congratulations to everyone who signed off and shipped this last cycle! This is a 1% increase in locale coverage between Fennec 39 and Fennec 40. Congratulations!
– We had the single largest number of locales ever to sign off on the launch of a Mozilla product today with Firefox for iOS. iOS users will be able to access Firefox in up to 36 languages in the first release! This is a major accomplishment for the Mozilla localization communities! Please take a moment to celebrate a job extremely well done.
– We’re looking forward to congratulating the Croatian team next cycle for launching their first localization of Firefox for Android. We’re also looking forward to seeing the Purépecha and Kaqchikel localization teams launch their first Mozilla localizations in Firefox for Android soon.
Thank you to everyone for all of your dedication and hard work this last sprint. As always, if you note anything missing in these reports, please let me know.