Yesterday I with Aman presented at Mozilla Carnival, Pune about the experience of releasing a new locale Maithili on the topic: "Firefox Localization : Locale—Localization—Release : A Case Study : Maithili Bugzilla Journey" [1]. I tried to understand the journey through the process we resolved important bugs for releasing Firefox in this presentation. I added one slide of community review but the requirement of community review is not tracked through bugzilla's locale release tracker bug. I think it is one of the most important aspect and it should be added in Mozilla l10n release process with more importance as it is very useful in making localized build error free to a great extent. I as a coordinator did for Hindi and as a mentor Maithili [2] as well. Though FUEL project [3] we covered lot for menus/sub-menus level review by community, but the dedicated review for Firefox by community helped us lot. I would recommend to incorporate the community
review phase as a dependency in the release tracker bug of a locale. Also I would like to recommend other already released locales also to go for it to make the mozilla localized product much more better.
[1] http://bhashaghar.googlecode.com/files/Firefox_Localization_Case_Study_Maithili_Pune_Carnival.pdf
[2] http://bhashaghar.googlecode.com/files/Review%20Workshop%20of%20Firefox%20Maithili_A-Report.pdf
[3] https://fedorahosted.org/fuel
regards,
--------------
Rajesh Ranjan
Kramashah
Thanks!
Actually I found community review workshop useful in several ways and so I suggested. When writing this mail, I thought like other bugs, we can create a bug something like Localized Build Review and make it a criteria for final release of the localized build of beta. The community can be instructed to push the changes in upstream by mentioning it in comment including the bug no. Apart from this, it will generate awareness among language people that Firefox is going to come in their language. I did it for Maithili and allmajor newspaper/channels came to cover it.
Actually, I can see lot of work is happening here in Mozilla l10n community. We have challenges to streamline all l10n activity of one language under one place or at least some coordination is necessary among different type of localization activities or people involved in localization activity of same language. We have teams’ page [3] and I feel whole localization activity related to one language should have all details on that page.
One point I would like to add here, I think we should incorporate ‘Approved/Locked’ [1] like state for the translation tool Mozilla is going to adopt. I filed a bug for the same for gettext. Firefox is one of the flagship open source product and ensuring good localized build availability is of great importance. Probably you know that we under FUEL Module [2] tried to concentrate on three-four level of menus entries of frequently used applications in which Firefox is one major application of browser category and so lot of entries of Firefox is present in fuel module. It helps us to standardized menus across different applications and due to this we are able to improve GUI entries which a normal user can encounter in general.
[1] http://savannah.gnu.org/bugs/?37236
[2] http://svn.fedorahosted.org/svn/fuel/fuel_pot/fuel_en_US.pot
[3] https://wiki.mozilla.org/L10n:Teams
regards,
--------------
Rajesh Ranjan
Kramashah
________________________________
From: Axel Hecht <l1...@mozilla.com>
To: dev-...@lists.mozilla.org
Cc: community-india <communi...@lists.mozilla.org>; Mozilla Reps - General <reps-g...@lists.mozilla.org>
Sent: Monday, September 17, 2012 5:19 PM
Subject: Re: Firefox Localization : Journey through Bugzilla
Hi Rajesh,
Axel
_______________________________________________
dev-l10n mailing list
dev-...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-l10n