Localization Bugs Resolved Incomplete

Yesterday, Axel and I (and a few others) went through several lingering registration bugs that needed attention from our team.  I think we covered just under 40 outstanding bugs and came up with responses that we should provide over the upcoming days.

This is more of our effort to improve communication with localizers and to eliminate the number of outstanding bugs that have not had activity or are waiting for a response from someone on the l10n-drivers team at Mozilla Corporation.  We decided to resolve a number of bugs as “incomplete” where individuals had not responded to pings for several months (and in some cases, over one year).

I inserted the following note in each bug to the localizers:

“Hello:  Due to the lack of recent activity on this bug, we are going to resolve it as “incomplete”.  If you choose to restart translation activity, then no problem at all.  Please notify the l10n-drivers team using the l10n mailing list (dev-l10n@lists.mozilla.org) and file a new bug in Bugzilla.  That bug should indicate that you are interested in translating the upcoming version of Firefox, which is 3.1 right now.  All the best, SethB”

Here is a list of the lanaguages and bugs I committed as incomplete:

301564 [ig-NG] Igbo: Firefox, Thunderbird
309575 [ky-KG] Kyrgyz: Thunderbird
370204 [gsc] Aranese: Firefox
398393 [ti] Tigrigna: Firefox
407543 [ht] Haitian creole: Firefox
412994 [kk] Kazakh: Firefox

Over the next few days, I will be working on pinging many individuals who have filed registration bugs, but have had recent activity.  Most likely, we will ask these individuals to participate in the upcoming localization of Firefox 3.1.  Obviously, a lot has to be done before any of the localizers need to worry about translating the next major release of the browser.  (for one, we need to get builds and tinderboxen set up…)  But, we intend to start the communication process with the new teams who seem interested in participating in the upcoming release.