Skip to content
This repository has been archived by the owner on Jun 12, 2021. It is now read-only.

Commit

Permalink
Merge branch 'release/2016-08-31'
Browse files Browse the repository at this point in the history
  • Loading branch information
Pike committed Aug 31, 2016
2 parents 8b4145c + dc3b09d commit 28f7edd
Show file tree
Hide file tree
Showing 3 changed files with 18 additions and 18 deletions.
6 changes: 3 additions & 3 deletions apps/bugsy/templates/bugsy/new-fennec-locales.json
Expand Up @@ -8,7 +8,7 @@ file, You can obtain one at http://mozilla.org/MPL/2.0/.
"comment": "This is a tracker bug for releasing Firefox Mobile {{ loc }}.\n\nThis bug is not that detailed, but as we get particular work items, they should\nblock this bug for tracking and discoverability.",
"product": "Mozilla Localizations",
"title": "shipping",
"cc": "{{ bugmail }},l10n@mozilla.com,stas@moz,pascalc@gmail,francesco.lodolo@gmail.com",
"cc": "{{ bugmail }},l10n@mozilla.com,francesco.lodolo@gmail.com,lebedel.delphine@gmail.com",
"rep_platform": "All",
"short_desc": "[{{ loc }}] Firefox Mobile release tracker {{ language }}",
"component": "{{ component }}",
Expand All @@ -17,10 +17,10 @@ file, You can obtain one at http://mozilla.org/MPL/2.0/.
"blocked": "fm-l10n-tracker"
},
{
"comment": "We want to ship Firefox Mobile with a good list of search engines for {{ language }}. \n\nWe're going to work towards this in three phases. First, the localization team and the l10n drivers will look at the market for the language and come up with a good set of search providers. {{ name }}, we'll need your input on this, the guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Mobile/Productization>. \n\nFor en-US, we currently use this set, to which we can fall back in the case of lacking localized alternatives:\n\n> Google, Yahoo, Bing, Amazon, Twitter, Wikipedia\n\nWe may also want to go with just a subset of the en-US engines, if that's more appropriate for the local market.\n\nOnce we decide to use a particular search engine (and we test it on a mobile device), l10n drivers will contact the owner and ask for permission, and for specifics like proper search flags. {{ name }}, we'll likely need your help to at least get the contact information.\n\nFor search engines that we already ship with on desktop and that you would like to include in mobile as well, the permission is not needed. Consider using a mobile version of the engine if one is available. For Android we'll want a specific 96x96px image, with colored background and rounder corners (6px radius).\n\nOnce we have a specification on what the search engines for {{ language }} should look like, flod (Francesco Lodolo) and the localization team will work on the implementation. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. {{ name }}, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing. \n\nPlease don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Axel or someone else appointed by the l10n drivers. The data here is sensitive to users and our search partners, thus the extra care here.\n\nThe {{ language }} team and flod will be driving this bug to completion.",
"comment": "We want to ship Firefox Mobile with a good list of search engines for {{ language }}. \n\nWe're going to work towards this in three phases. First, the localization team and the l10n drivers will look at the market for the language and come up with a good set of search providers. {{ name }}, we'll need your input on this, the guidelines for making recommendations are on <https://wiki.mozilla.org/L10n:Mobile/Productization>. \n\nFor en-US, we currently use this set, to which we can fall back in the case of lacking localized alternatives:\n\n> Google, Yahoo, Bing, Amazon, Twitter, Wikipedia\n\nWe may also want to go with just a subset of the en-US engines, if that's more appropriate for the local market.\n\nOnce we decide to use a particular search engine (and we test it on a mobile device), l10n drivers will contact the owner and ask for permission, and for specifics like proper search flags. {{ name }}, we'll likely need your help to at least get the contact information.\n\nFor search engines that we already ship with on desktop and that you would like to include in mobile as well, the permission is not needed. Consider using a mobile version of the engine if one is available. For Android we'll want a specific 96x96px image, with colored background and rounder corners (6px radius).\n\nOnce we have a specification on what the search engines for {{ language }} should look like, Delphine and the localization team will work on the implementation. Delphine will create and attach patches for the desired changes and get them reviewed. After a successful review, Delphine will land them. {{ name }}, if you're interested, you could create the patches, too. You'd ask Delphine for review on those before landing. \n\nPlease don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by Delphine, flod, Axel or someone else appointed by the l10n drivers. The data here is sensitive to users and our search partners, thus the extra care here.\n\nThe {{ language }} team and Delphine will be driving this bug to completion.",
"product": "Mozilla Localizations",
"title": "search",
"cc": "l10n@mozilla.com,{{ bugmail }},francesco.lodolo@gmail.com",
"cc": "l10n@mozilla.com,{{ bugmail }},francesco.lodolo@gmail.com,lebedel.delphine@gmail.com",
"rep_platform": "All",
"short_desc": "[{{ loc }}] Search engine setup for Firefox Mobile for {{ language }}.",
"component": "{{ component }}",
Expand Down

0 comments on commit 28f7edd

Please sign in to comment.