Closed Bug 1158054 Opened 9 years ago Closed 9 years ago

[ks] Search engine setup for Firefox for Kashmiri

Categories

(Mozilla Localizations :: ks / Kashmiri, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gueroJeff, Assigned: flod)

References

()

Details

(Keywords: productization)

We want to ship Firefox with a good list of search engines for Kashmiri. 

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. Chandrakant, we'll need your input on this. The guidelines for making recommendations are found on <https://developer.mozilla.org/en-US/docs/Productization_guide>. 

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. Chandrakant, 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 Kashmiri 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. Chandrakant, 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, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.

The Kashmiri team and flod will be driving this bug to completion.
Assignee: nobody → francesco.lodolo
bing
eBay-in
google
yahoo-in
Component: Other → ks / Kashmiri
Depends on: 1170525
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.