Virtual, global Mozilla l10n sprint — Report

Jeff Beatty

0

I want thank everyone who both accomplished their Spring Release work before the l10n sprint and participated in the l10n sprint. As you know, the Spring Release is one of the two major releases this year and a big opportunity for new users to download and install your localization work. When they do so, we want to make sure they’re installing the most localized version of the browser(s) yet! In order to be sure that your localization is one of those shipping an update in the Spring Release, please sign off on your projects by 30 April.

Here’s what we accomplished before and during the sprint:

Firefox 38 desktop:

  • pre-sprint 48% signed off,
  • post-sprint 53% signed off (rm, tr, fa, ko)

Fennec 38:

  • pre-sprint 64% signed off,
  • post-sprint 66% signed off(pt-PT)

Web parts:

  • eo, kn, bn-IN, sk were able to bring their mozilla.org and other projects up-to-date.

The following locales were done with Firefox/Fennec spring release before the sprint. Congratulations and thank you:

  • af
  • an 
  • ar 
  • az 
  • bg 
  • bn-IN
  • br 
  • cs 
  • cy 
  • dsb 
  • es-CL 
  • es-ES 
  • et 
  • eu 
  • fi 
  • fr 
  • fy-NL 
  • ga-IE 
  • gd 
  • hr 
  • hsb 
  • id 
  • is 
  • it 
  • kk 
  • lv
  • my
  • nl 
  • pt-PT
  • pl
  • ro 
  • ru
  • sk 
  • sl 
  • sq 
  • sr 
  • sv-SE 
  • uk 
  • zh-CN 
  • zh-TW

The following locales made progress on localizing Spring Release products (Firefox/Fennec) during the sprint. Thank you for your involvement:

  • bg
  • br
  • cs
  • de
  • es-MX
  • fa
  • hi-IN
  • kn
  • ko
  • lt
  • nn-NO
  • pl
  • pt-PT
  • rm
  • si
  • ta
  • tr
The Beta cycle is not yet over and we all still have time to ship the most linguistically accessible version of the Firefox browsers yet! If you have not yet signed off on your localizations, please do so by 30 April. We will be reaching out to individual locales between now and then to see how we can help you ship a complete update for Spring Release!

Awesome l10n contributor: Umesh Agarwal

Jeff Beatty

0

Part of a series similar to the Awesome L10n Communities series where individual contributors are spotlighted for their efforts.umesh

Umesh Agarwal

Started with Mozilla project: 2013
Nationality: Indian
Languages: English, Hindi, Bengali
Background: CS graduate specializing in Big Data and Data Mining, working on Oracle apps development.
Role in L10n community:  Translator & review for Hindi projects, coordinating Hindi Marketplace l10n
Projects you’re currently working on:
  • Marketplace
  • Other projects in need
  • Previously worked on Webmaker
How did you get started with the Mozilla project?

I began at Mozilla as a university student. Other members of the Indian community (Shahid Farooqui, Biraj Karmakar, Chandan Kumar) recruited me to be involved in the project. Shahid created an event at the university and gave me the chance to give a presentation on Mozilla design. After that event, Shahid conducted an online sprint for localizing projects in Pootle. Biraj and Shahid trained me on how to localize Firefox and other projects and then got me in touch with Rajesh Ranjan. Through Rajesh, I became familiar with the FUEL project and I became more and more involved. Seeing the software in my language was a very good and motivating experience.

What have been some of the biggest challenges to your localization effort?
It can be very difficult to find documentation for being involved in l10n. It is especially very tough for beginners. Connecting with mentors can help to fix this and make getting involved in Mozilla localization much easier and a lot of fun.

 

What have been some of your biggest successes?

Becoming a reviewer and then a l10n project coordinator for a national language (Hindi) in less than two years.

What’s your philosophy/method on localizing Mozilla projects (how do you stay on top of things)?

Having a clear priority for a project helps localizers to know where to concentrate all of our efforts and provide the best quality translation for the project. Take the Marketplace project, for example. When it became a priority and a need in India for the Firefox OS launches, we were able to focus on it. Before then, we didn’t focus on it. Prioritize your team’s projects within your own team. When another project priority is escalated, adjust. When there’s no escalation, rely on your team’s internal project priorities. Document these priorities on your team’s wiki page.

As a reviewer, I must also be a mentor. When I reject a string, I must follow up with them feedback on why that string was rejected to help them to improve their work and grow.

If you could identify several best practices that have helped you to become a successful Mozilla localizer, what would they be?
  • Follow the Mozilla L10n guidelines as closely as possible.
  • Following the guidelines from your regional l10n mentor.
  • Be in contact with your l10n mentor frequently.
  • Enjoy it! :-D
You’re a Mozilla Rep and a localizer. Do you see these roles as complementary? Could you provide details?

Both have their separate responsibilities, but in some ways they overlap. I’m able to organize localization events for Hindi, which helps the Hindi l10n community. As a Rep, my network goes beyond l10n, so I often help with events that aren’t l10n-specific. Where there’s a need from a specific l10n team to help, I’m able to support them with the Reps program, regardless of if it’s within the Hindi team or in another. I have helped with Bengali l10n events and the Maithili Fennec launch event in Patna.

What unique practices does the Hindi l10n team have for working on l10n projects?

We hold virtual l10n sprints, since the Hindi l10n community is spread throughout India. The Hindi mailing list helps to coordinate all of the work no matter where we are.
We also divide the workload and l10n project ownership. Many localizers want to be involved in Hindi l10n. It’s important to spread out the workload and give others an opportunity to participate and grow. Decentralized leadership also helps to mentor more people and share good ideas and practices.

What are you most looking forward to accomplishing this year in your l10n efforts?

With this month’s virtual l10n sprint, I hope that we can arrive at 80% complete in Pootle for the locale. I’m also really looking forward to reactivating the localization literacy map project in FUEL.

Five things you may not know about me:
  1. I’m helpful, but sometimes it comes off as arrogant because I’m unable to help when there are communication gaps.
  2. I’m the leader of the FSA task force leader in India.
  3. I just recently became a Reps mentor :-)
  4. I like soft Hindi music.
  5. My favorite food is biryani.

Virtual, global l10n sprint for Northern Spring Release

Jeff Beatty

0

Hi localizers!

Thank you for all of your work to make the Northern Spring Release a success. Because the timeframe was so brief for localizing 38 in Aurora, we’re asking that you continue to focus your efforts on making 38 a great release while it’s in Beta. The marketing and publicity that will be used to promote this release will be critical to gaining more users across all locales and platforms. To best serve Mozilla users at this important time, we need to be sure that they receive the best the community can offer in localized products.

That being said, I’m excited to announce that we’re trying something new and different than what we’ve done before. On 8 April, we will be holding a virtual global localization sprint for the Northern Spring Release! We feel that the opportunity for user growth provided by the Northern Spring Release creates an exception to the preferred way of localizing these projects and requires this rare event. I use the term “sprint” specifically because we are hoping to cover a lot of l10n work within a short, 24-hour period of time in Beta (essentially, we’re sprinting to cover a lot of ground, fast). Here’s what will be involved:

Mission:
– Unify the global l10n community virtually for 24 hours in order to complete l10n work associated with the Northern Spring Release (Fx38, fennec38, fx-ios, marketing, fxOS2.2, marketplace).

How it will happen:
–  A few l10n-drivers will clear their schedules throughout the day on 8 April starting at 12AM UTC. Each will work exclusively to support those participating in the sprint by answering questions, helping with testing, performing sign-offs, and even jumping in to translate where you feel it would be helpful.
– We have created the localization channel in vidyo just for this event (https://v.mozilla.com/flex.html?roomdirect.html&key=RJUISaeKVSdq1PwuPElfyZk2CNQ) and will hold most of the discussions there and in #l10n.
– There is no schedule of sessions or topics; this will be simply the largest online gathering of localizers around the globe intent on translating Mozilla projects for the Northern Spring Release.
– We’ll publicize the sprint on social media using the hashtag #mozl10n.
– While the sprint will be going on during those 24 hours, no one is expected to stay for the full 24 hours. We’re simply asking that you plan to spend time with us that day translating together.

Please join us on 8 April for this rare event for the Northern Spring Release! And please forward this email along to all members of your l10n team.

Please also let us know if you have any questions.

Looking forward to seeing you there!

Localize Firefox 38: Northern Spring and ESR!

Axel Hecht

1

Firefox 38 is now string frozen. On March 30th, we’ll migrate 38 to
beta, which gives you a week and a half to get the translation work into
a great state.

This is one of our two big releases this year, and it’s the ESR, so it’s
going to be around for a while.

We ended up with a good 300 strings for 38; they’re split across:

  • Reader View and Reading List
  • Hello (tab sharing for example)
  • Developer Tools

Upcoming schedule for 38 and the northern-spring release:

  • March 30: Migrate from aurora to beta
  • April 6: Marketing material string freeze (including content for
    mozilla.org)
  • April 30: last chance to get changes in on beta
  • May 12: Release Firefox 38, and celebrate

We’ve been talking to Dwayne about opening up 38 on Beta on locamotion,
and giving you all the goodness there. He’ll follow up on that.

Thank you so much for your contributions and your patience.

Localization Hackathons in India and Sri Lanka

Jeff Beatty

0

In February, three of the l10n drivers were able to make an overdue trip to meet with localizers in India and Sri Lanka. It was a really wonderful experience to meet localizers in person that we had interacted with for so long virtually.

We had a particular format for the event and a few specific goals. The format was to spend half of each day in large group discussion and half broken up into each l10n team so that localizers could fix bugs, translate strings, and collaborate in person while we discussed l10n community health status with each l10n team, one-on-one. Unfortunately, this format was slightly confusing the first day, particularly the breakout half of the day. The second day was much more productive. Our goals for the meetup were specific to matters in India localization communities:

  1. Share updates to product release schedules and the Mozilla organization with localizers.
  2. Discuss how localizers see their localized products being used in India and Sri Lanka and brainstorm how to increase the user base for Firefox and Fennec in local languages.
  3. Discuss how Indic and Sri Lankan localization teams prioritize localization work.
  4. Identify outstanding internationalization bugs that specifically affect Indic languages.
  5. Create a strategy to raise the number of Indic languages we ship Firefox into from 12 to 22.

We were able to accomplish each of these goals and enjoy the collaboration with the community to do so. We learned a lot of helpful insights into the challenges faced by Indic l10n teams.

There were three discussions that were particularly engaging: the virtuous participation cycle, the Mozilla l10n landscape, and increasing the user base for Firefox and Fennec in local languages. One of the most interesting outcomes of these discussions was the creation of a local language promotion taskforce in India. This taskforce is responsible for creating campaigns to educate users on how to find Firefox and Fennec in their local languages and to help Mozilla identify successful marketing strategies for increasing the local language user base in India.

In Sri Lanka, we had a great opportunity to meet with both new and veteran localizers for the Sinhala localization team. In addition to a very engaging conversation about how people in Sri Lanka use Firefox in Sinhala, the most interesting and motivational part of the hackathon was the breakout portion. Seeing veteran localizers become very involved in mentoring new localizers and collaboratively creating a Sinhala style guide and glossary was inspirational.

All-in-all, this was a very fulfilling experience for Axel, Arky, and I. I want to thank Ani Peter, Rajesh Ranjan, Galaxy Kadiyala, Danishka Navin and Konstantina for all of their help to make these events possible and successful.

For more information about these events, please see the following links:

  • https://wiki.mozilla.org/L10n:Meetings/IndiaQ12015
  • https://wiki.mozilla.org/L10n:Meetings/Sri_Lanka2015

Here are some of our favorite pics from the events:

2015-02-02 14.57.33 2015-02-03 15.43.12 2015-02-03 17.00.16 2015-02-03 17.28.53 2015-02-05 11.04.33 2015-02-05 13.29.06 2015-02-05 14.02.58 2015-02-06 12.13.25 2015-02-06 17.07.142015-02-08 13.59.36 2015-02-08 14.00.07 2015-02-08 14.22.31

Firefox L10n Report (Aurora 37)

Jeff Beatty

0

Hello localizers!
Thank you all for your great work with Firefox 35 and 36. Here’s an outline of what is currently in Aurora this cycle (37) and what we accomplished together last cycle:

This cycle (Fx37) — 13 Jan. – 24 Feb.

Key dates:
– Beta sign-offs for new locales must be complete by 2 Feb.
– Beta sign offs must be completed before 9 Feb.
– Aurora sign offs must be completed before 23 Feb.
– Firefox 36 releases 24 Feb.

Features:
– Approximately 97 new string changes were made to Aurora desktop, 20 for Aurora mobile exclusively (unshared).
– 37% of the desktop strings changes are in devtools. 46% are strings that need to be removed from your repo. The rest are related to mixed content, search UI, and mirrored tabs. (see https://wiki.mozilla.org/Features/Release_Tracking#Likely_in_Firefox_37 for more info).
– 60% of the mobile string changes are related to syncing your Firefox account. 10% of the mobile string changes are related to password security. The rest include the home page and pref tracking protection (see https://wiki.mozilla.org/Mobile/Roadmap#Firefox_37_.28Aurora.29 ).

Notes:
Please remember that sign offs are a critical piece to the cycle and mean that you approve and can vouch for the work you’re submitting for shipment.

Last cycle — 1 Dec. – 12 Jan.

Noteworthy accomplishments:
62% of all locales shipped Firefox 35 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is an 8% decrease in locale coverage between Firefox 34 and Firefox 35.
76% of all locales shipped Fennec 35 on time. Congratulations to everyone who signed off and shipped this last cycle! This is a 1% decrease in locale coverage between Fennec 34 and Fennec 35!
– The Breton (br) and Esperanto (eo) teams launched their localizations of Fennec with Fennec 35. Please reach out to them with your congratulations!

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.

Firefox L10n Report (cycles 35 & 36)

Jeff Beatty

0

Hello localizers!

Thank you all for your great work with Firefox 34 and 35. Here’s an outline of what is currently in Aurora this cycle (36) and what we accomplished together last cycle:

This cycle (Fx35) — 1 Dec. – 12 Jan.

Key dates:
– Beta sign-offs for new locales must be complete by 22 Dec.
– Beta sign offs must be completed before 29 Dec.
– Aurora sign offs must be completed before 12 Jan.
– Firefox 34 releases 13 Jan.
Features:
– Approximately 192 new string changes were made to Aurora desktop, 39 for Aurora mobile exclusively (unshared).
– 40% of the desktop strings changes are strings or files that need to be removed from your repos. 8% of all changes are related to Loop. 40% of all string changes are in devtools (see https://wiki.mozilla.org/Features/Release_Tracking#Likely_in_Firefox_36 for more info).
– 28% of the mobile string changes are related to Do Not Track. 15% of the mobile string changes are related to Content Security Policy. The rest include home page, Firefox Accounts, and preferences (see https://wiki.mozilla.org/Mobile/Roadmap#Firefox_36_.28Aurora.29 ).

Notes:
Please remember that sign offs are a critical piece to the cycle and mean that you approve and can vouch for the work you’re submitting for shipment.

Last cycle — 13 Oct. – 1 Dec.

Noteworthy accomplishments:
70% of all locales shipped Firefox 34 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is an 10% decrease in locale coverage between Firefox 33 and Firefox 34.
77% of all locales shipped Fennec 34 on time. Congratulations to everyone who signed off and shipped this last cycle! This is a 3% increase in locale coverage between Fennec 33 and Fennec 34!

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.

Firefox L10n Report (cycles 34 & 35)

Jeff Beatty

1

Hello localizers!

Thank you all for your great work with Firefox 33 and 34. Here’s an outline of what is currently in Aurora this cycle (35) and what we accomplished together last cycle:

This cycle (Fx35) — 13 Oct – 24 Nov

Key dates:
– Beta sign-offs for new locales must be complete by 3 Nov.
– Beta sign offs must be completed before 10 Nov.
– Aurora sign offs must be completed before 24 Nov.
– Firefox 34 releases 25 Nov.
Features:
– Approximately 160 new string changes were made to Aurora desktop, 57 for Aurora mobile exclusively (unshared).
– 54% of the desktop strings changes are strings or files that need to be removed from your repos. 25% of all changes are related to Loop. 19% of all string changes are related to session restore and profiles. 13% of all string changes are in devtools (see https://wiki.mozilla.org/Features/Release_Tracking#Likely_in_Firefox_35 for more info).
– 23% of the mobile string changes are related to providing user feedback. The rest include screencasting, and preferences (see https://wiki.mozilla.org/Mobile/Roadmap#Firefox_35_.28Aurora.29 ).
Notes:
Please remember that sign offs are a critical piece to the cycle and mean that you approve and can vouch for the work you’re submitting for shipment.

Last cycle — 1 Sept. – 13 Oct.

Noteworthy accomplishments:
80% of all locales shipped Firefox 33 on desktop updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is an 10% increase in locale coverage between Firefox 32 and Firefox 33! Thank you to everyone involved in making this possible; it’s the highest update percentage we’ve seen in months!
74% of all locales shipped Fennec 33 on time. Congratulations to everyone who signed off and shipped this last cycle! This is an 1% decrease in locale coverage between Fennec 32 and Fennec 33!
– The Azerbaijani (az) team launched their first localization of Firefox desktop! Please contact the team to congratulate them on this massive accomplishment, and feel free to tweet all about!
– The Aragonese (an), Kazakh (kk), and Frisian (fy-NL) teams launched their first localizations of Fennec! Please contact the teams to congratulate them on this massive accomplishment, and feel free to tweet all about!
– Both the BBC and The Economist reported about the incredible efforts of the Mozilla l10n community, and featured interviews from Ibrahima Sarr and myself.

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.

Firefox L10n Report (cycles 33 & 34)

Jeff Beatty

1

Hello localizers!

Thank you all for your great work with Firefox 32 and 33. Here’s an outline of what is currently in Aurora this cycle (34) and what we accomplished together last cycle:

This cycle (Fx34) — 2 September – 14 October

Key dates:
– Beta sign offs must be completed before 29 September.
– Aurora sign offs must be completed before 13 October.
– Firefox 33 releases 14 October.

Features:
– Approximately 574 new string changes were made to Aurora desktop, 136 for Aurora mobile exclusively (unshared).
– 21% of the desktop changes are strings or files that need to be removed from your repos. 13% of all string changes are in devtools. The rest cover changes in Private Browsing, mixed content blocking, Get User Media, Loop video & voice calling (see https://wiki.mozilla.org/Features/Release_Tracking#Likely_in_Firefox_34 ).
– 21% of the mobile string changes are related to device storage dialogues. The rest include developments in tab mirroring, guest browsing, among others (see https://wiki.mozilla.org/Mobile/Roadmap#Firefox_34:_.28Beta.29 ).

Notes:
Please remember that sign offs are a critical piece to the cycle and mean that you approve and can vouch for the work you’re submitting for shipment. I will be following this report with an email to the dev-l10n list regarding some changes to the l10n sign-off schedule, specifically related to versions of Firefox in the Beta channel.

Last cycle — 10 June – 21 July

Noteworthy accomplishments:

70% of all locales shipped Firefox 32 updates on time. Congratulations to everyone who signed off and shipped this last cycle! This is an 2% increase in locale coverage between Firefox 31 and Firefox 32! Together, let’s aim to raise that percentage to 80% for Firefox 33! So far, we’re at 65% signed off!
75% of all locales shipped Fennec 32 on time. Congratulations to everyone who signed off and shipped this last cycle! This is an 11% decrease in locale coverage between Firefox 31 and Firefox 32! Together, let’s aim to raise that percentage to 80% for Firefox 33! So far, we’re at 68% signed off!
– The Armenian, Basque, Fulah, Icelandic, Scottish Gaelic and Welsh teams launched their first localizations of Fennec! These are the first locales to enjoy launching their work, thanks specifically to the new language switching piece in Fennec 32. Please contact the teams to congratulate them on this massive accomplishment, and feel free to tweet all about!
– The Lower Sorbian team has launched their first localization of Firefox desktop! Please contact the team to congratulate them on this massive accomplishment, and feel free to tweet all about!

Awesome l10n contributor: Biraj Karmakar

Jeff Beatty

6

Part of a series similar to the Awesome L10n Communities series where individual contributors are spotlighted for their efforts.

Biraj Karmakar biraj

Nationality: Indian
Languages: Bengali, English, Hindi
Background: Been a Mozillian for four years. Starting at the beginning of his university studies four years ago. Was recruited by Runa to localize Thunderbird. Studying Computer Science Engineering at West Bengal University of Technology in his final year.
Role in L10n community: I have started working with mozilla as a translator. But now I am locale owner. Driving product l10n for Indian Bengali.

Projects you’re currently working on:
Firefox desktop, Firefox OS, Firefox for Android, previously on Thunderbird, Webmaker, and SUMO.

How did you get started with the Mozilla project?

One day, arrbee (Runa) asked me if I was interested in Mozilla Thunderbird translation or not. So, I told her that I was really interested to translate the Thunderbird and I began right away.

What have been some of the biggest challenges to reviving your localization effort?

There were technical barriers to entry for people to get involved because bn-IN was not hosted on Pootle. Training localizers has also been a challenge. Language differences among community were a challenge.

What have been some of your biggest successes?

At last Firefox Aurora 27 came after Firefox 16 and Bengali India page was been re-enabled. L10n sprints have been a very helpful tool to update and maintain Firefox desktop localization. One of these last year, in particular, was very helpful in this area.

How do you help your team find new L10n contributors?

Generally, in every event in my region, I take a session on localization and introduce the participants how to do localization in their languages. Talking to people at all events I attend and encouraging people to get involved. I try to encourage them to get involved in multiple areas of Mozilla, but specifically to start with l10n and I mentor them through the process of getting started with l10n.

What’s your philosophy/method on mentoring new contributors?

First of all, I give them some example about localization, like mobile phone operating system.
Then ask them why it is needed. After hearing their answer I discuss its importance. I give a small presentation on localization. After that, I give a hands-on session how to do localization .
I tell some rules and regulations which have to followed at the time of localization.

If you could identify several best practices that have helped you to become a successful Mozilla localizer, what would they be?

  1. I don’t use the machine translating system. Only use MT for specific purposes, like terminology lookup, instead of sentences. And even then, I use it for inspiration, not for the concrete term. Example : খাতা is wrong for “File” word . We have to use “ফাইল” for “File” word.
  2. I like Pootle’s error checking system which helps me to check silly mistakes.
  3. Also I like Pootle’s string auto suggestion system which helps me to save my time for translating similar strings.
  4. For translation, I always use the Bengali keyboard layout.
  5. Look to knowledgeable people for help.

What are you most looking forward to accomplishing this year?

Firefox OS  and Firefox for Android.

Five things you may not know about me:

  1. I’m a Web Developer (with 2 apps in Firefox OS Marketplace).
  2. I also work on SUMO, Webmaker, and QA.
  3. I’m a good mentor.
  4. I’m a nice person :-)
  5. I have a photography business and enjoy photo editing and graphic design.