Personal tools

L10n:Bugogram

From MozillaWiki

Jump to: navigation, search

These are the bugs to file for new Firefox localizations. The headings below represent bug types that are to be filed for new Firefox localizations. The information contained under each identifies the short descriptions, aliases, blockers (i.e., dependencies), and participating parties for each bug type. The coded variables listed in each bug type are Python variables used to annotate locales, languages, and people. They are meant to serve as informational templates to use whenever a bug corresponding to that bug type is filed and can be copied and pasted into the bug itself at the time of filing it.

Contents

shipping

short_desc 
[%(loc)s] Firefox release tracker %(language)s
alias 
fx-l10n-%(loc)s
blocked 
fx-l10n-tracker
cc 
 %(bugmail)s,l10n@mozilla.com,pascalc@gmail,francesco.lodolo@gmail.com

This is a tracker bug for releasing Firefox %(loc)s.

Your team's dashboard should be up on http://l10n.mozilla.org/teams/%(loc)s. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibilty to your work.

The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug.

We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds mozilla generates, and puts on ftp.

If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.

bugzilla

short_desc 
Create l10n bugzilla component for %(language)s (%(loc)s), add value for Locale field
product 
bugzilla.mozilla.org
component 
Administration
blocked 
fx-l10n-%(loc)s
cc 
 %(bugmail)s,l10n@mozilla.com

We need a bugzilla component for the '%(loc)s' Localization, and a new value for the Locale custon field.

Please add a new value for the custom field 'Locale': %(loc)s / %(language)s

The details for the component should be:

Product: Mozilla Localizations Component: %(loc)s / %(language)s Description: %(language)s Localization (...)

Assignee: nobody QA Contact: Empty

%(name)s, could you provide a utf-8 encoded translation of '%(language)s Localization' to include in the component description? In preparation of a new scheme, could you also fill out the descriptions for Firefox on https://localize.mozilla.org/%(loc)s/bugzilla_components/, please? You'll be able to either log in with your ldap credentials once you have them (along with your hg access), or create an account there. Either way, I'll need to grant you permissions on the server, so poke me with your account details for that.

Once we have the description, this bug will be fixed by Mozilla staff.

hg_repo

short_desc 
l10n aurora/beta/release mercurial repository for '%(loc)s'
product 
Release Engineering
component 
Repos and Hooks
blocked 
fx-l10n-%(loc)s
cc 
l10n@mozilla.com

Please create a new releases/l10n/mozilla-aurora, -beta, and -release hg repositories for a new Firefox localization. The repositories should be releases/l10n/mozilla-aurora/%(loc)s/ etc, with the common scm_l10n permissions and hooks, both python:mozhghooks.pushlog and python:mozhghooks.single_head_per_branch.hook.

Please make sure that mxr is updated to pick up the new repos.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

build

short_desc 
Add '%(loc)s' to the Firefox build
product 
Firefox
component 
Build Config
blocked 
fx-l10n-%(loc)s
cc 
l10n@mozilla.com

We need to add '%(loc)s' to browser/locales/all-locales on mozilla-aurora.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

releng

short_desc 
Add '%(loc)s' to the Firefox build
product 
Release Engineering
component 
General Automation
blocked 
fx-l10n-%(loc)s
cc 
l10n@mozilla.com

We need to add '%(loc)s' to the Firefox Aurora l10n builds.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

product-details

short_desc 
Add '%(loc)s' to product-details
product 
Websites
component 
Other
blocked 
fx-l10n-%(loc)s
cc 
l10n@mozilla.com,pascalc@gmail

We need to add '%(loc)s' to the Firefox Aurora l10n builds on our website. Please check the dependent bugs of bug fx-l10n-%(loc)s on the native name of the language, and when we're having the actual builds on ftp.

PS: to be clear to the localization team, this bug is handled by Mozilla staff.

Webservices

We'll have a separate bug for each web service area, namely

  • search
  • protocol handlers
  • rss readers

search

short_desc 
[%(loc)s] Search engine setup for Firefox for %(language)s
cc 
l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
blocked 
fx-l10n-%(loc)s
keywords 
productization
bug_file_loc 
https://wiki.mozilla.org/L10n:Firefox/Productization

We want to ship Firefox with a good list of search engines for %(language)s.

We'll do this in three phases: First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good set of search providers. %(name)s, we'll need your input on this. The guidelines for making recommendations are found on <https://wiki.mozilla.org/L10n:Firefox/Productization>.

We currently use this set for en-US, to which we can fall back in the case of lacking localized alternatives: Google, Yahoo!, Bing, Amazon, eBay, Twitter, Wikipedia

After we decided on a particular search engine, flod will contact the owner and ask for permission and for specifics, like proper search flags. %(name)s, we'll likely need your help to at least get the owner's contact information.

Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.

The %(language)s team and flod will be driving this bug to completion.

protocol

short_desc 
[%(loc)s] Firefox protocol handler setup for %(language)s
cc 
l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
blocked 
fx-l10n-%(loc)s
keywords 
productization
bug_file_loc 
https://wiki.mozilla.org/L10n:Firefox/Productization

Protocol handlers allow links like mailto:nobody@mozilla.org to be handled by a webmail application.

In order to do that, the site needs to support a special API described on https://developer.mozilla.org/en-US/docs/Web-based_protocol_handlers.

For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto:, 30boxes for webcal: and Mibbit for irc: urls. For %(language)s, we'd like to do that, too.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with a good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. Following that, the evangelism team reaches out to try to get the vendor to support protocol handlers. http://people.mozilla.org/~ctalbert/ has test cases for mailto:.

Once that happens, flod will take over the actual implementation, which will need to change the gecko.handlerService.* entries in browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by flod or somebody else appointed by flod/Stas on a patch for that change upfront.

The %(language)s team and flod will be driving this bug to completion.

readers

short_desc 
[%(loc)s] Firefox News reader setup for %(language)s
cc 
l10n@mozilla.com,%(bugmail)s,francesco.lodolo@gmail.com
blocked 
fx-l10n-%(loc)s
keywords 
productization
bug_file_loc 
https://wiki.mozilla.org/L10n:Firefox/Productization

News readers are web services allowing users to subscribe to RSS/ATOM feeds online and view them. If Firefox detects a feed, it offers the user the option to subscribe to it, either as a live bookmark or via one of the web services.

The current News Reader in en-US is My Yahoo!.

We want to ship a good set of defaults for %(language)s and will do that in three stages.

First, the localization team and flod (Francesco Lodolo) will look at the market for the language and come up with good candidates. %(name)s, we'll need your input on this. The guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Firefox/Productization>. After we decide on a particular news reader, flod will contact the owner and ask for permission. %(name)s, we'll likely need your help to at least get the contact information.

Once we have a specification on what the set of news readers for %(language)s should look like, flod will work on an implementation for that. flod will create and attach patches for the desired changes and request a review. After a successful review, flod team will land them. If you're interested, you can provide those patches too and request a review from flod before landing.

Please don't commit any modifications in browser/chrome/browser-region/region.properties to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod/Stas. The data here is sensitive to users and our search partners, thus requiring the extra care here.

The %(language)s team will be driving this bug to completion.

websetup

short_desc 
[%(loc)s] bootstrap %(language)s on svn and the web dashboard
product 
Mozilla Localizations
component 
Infrastructure
cc 
pascalc@gmail,%(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com

flod, Pascal, please set up the webdashboard for %(language)s, and add web pages to this locale's folder on mozilla.org.

In https://svn.mozilla.org/projects/mozilla.com/trunk/locales set up

download_button.lang
firefox/new.lang
firefox/channel.lang
firefox/whatsnew.lang
firefox/installer-help.lang
firefoxtesting.lang
main.lang
mobile.lang
mozorg/plugincheck.lang
mozorg/home.lang
mozorg/products.lang
newsletter.lang
tabzilla/tabzilla.lang
upgradedialog.lang

In https://svn.mozilla.org/projects/l10n-misc/trunk/firefoxhealthreport/locale/%(loc)s/ set up

fhr.lang
date.lang

Also add %(loc)s to the staging site, http://www-dev.allizom.org/%(loc)s/firefox/.

Please notify in the actual translation bug when this is done.

webparts

short_desc 
[%(loc)s] Firefox initial web parts for %(language)s
product 
www.mozilla.org
component 
L10N
blocked 
fx-l10n-%(loc)s
cc 
pascalc@gmail,%(bugmail)s,francesco.lodolo@gmail.com,l10n@mozilla.com

To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages. There's a set of pages that are essential to having a successful Firefox localization and promotion, and those depend on the files listed below.

flod or Pascal will follow up here when the initial setup work is done. After that, you'll find the files to localize in SVN.

The repositories you want to work with are located at https://svn.mozilla.org/projects/mozilla.com/trunk/locales/%(loc)s/ and https://svn.mozilla.org/projects/l10n-misc/trunk/firefoxhealthreport/locale/%(loc)s/ . Files that need to be translated are, namely:

in https://svn.mozilla.org/projects/mozilla.com/trunk/locales/%(loc)s/

download_button.lang
firefox/new.lang
firefox/channel.lang
firefox/whatsnew.lang
firefox/installer-help.lang
firefoxtesting.lang
main.lang
mobile.lang
mozorg/plugincheck.lang
mozorg/home.lang
mozorg/products.lang
newsletter.lang
tabzilla/tabzilla.lang
upgradedialog.lang

in https://svn.mozilla.org/projects/l10n-misc/trunk/firefoxhealthreport/locale/%(loc)s/

fhr.lang

All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.

The %(language)s team will be driving this bug to completion.

sumo

short_desc 
[%(loc)s] Enable %(language)s localization on SUMO
product 
support.mozilla.org
component 
Localization
cc 
 %(bugmail)s
blocked 
fx-l10n-%(loc)s

We need to enable the localization of SUMO in %(language)s [%(loc)s].

%(name)s, this is one of the better places to get the community to help out directly. If it makes more sense to redirect to another language, though, we can also do that.

And, %(name)s, we'd need "%(language)s" in %(language)s again to set this up, please add that here, utf-8 encoded. Thanks.

Once we have a decision what to do, and possibly the description, this bug will be fixed by Mozilla staff.

done

That's all folks.