L10n:Firefox in 2016/For Localizers
While L10n:Firefox in 2016 has been written with a focus on developers, let's rephrase this for Localizers.
We'll be talking about Firefox Desktop and Firefox for Android here. Other applications and websites are not affected.
This plan is based on various conversations that we had with you on our Hackathons in 2015, as well as conversations with the Firefox/Technical Architecture Group and a session in mozlando with stakeholders from Firefox, Build, Release.
The What
The idea is to create one repository (per localization) for you to work on, and to use that to localize all of Aurora (aka Developer Edition), Beta, Release, and ESR.
We will do that by keeping the strings that are only used in Beta and beyond around in the mozilla-aurora main Firefox repository.
We will also have these strings in mozilla-central, so we can use the same repository to localize Nightly as well.
and we will get
- With a single location for all Firefox strings, fixing strings will become much easier. And they'll be in end-users hands much quicker.
- We'll also be in a situation where breaks of string-freeze will become less impactful.
Axel's also hoping that we can expose strings on Nightly soon after they get done. We might given them a week to stabilize, but then we can offer strings for the upcoming aurora cycle. That would be great for a few reasons:
- You can work when you have time. No waiting for 6 weeks until we give you the next batch.
- You don't need to delay work in case new volunteers show up. There's going to be something new to localize the next day.