Closed Bug 471561 Opened 15 years ago Closed 15 years ago

Change search/start defaults to Yandex in ru builds

Categories

(Firefox :: Search, defect, P2)

3.5 Branch
defect

Tracking

()

VERIFIED FIXED
Firefox 3.1b3

People

(Reporter: kev, Assigned: kev)

References

Details

(Keywords: verified1.9.1, Whiteboard: [bug 480598 covers getting this into b3])

Attachments

(2 files, 1 obsolete file)

Per the new business arrangement between Mozilla & Yandex in Russia, we need to make some changes to the ru build's search defaults. Those changes will include modifying the default Yandex search plugin, putting it first in search plugin order, and making it the default searchengineprovider. We will also need to change the keyword.URL to Yandex, and add an argument to the default start page. (see below)

Google will move from position 1 to position 2. 

This change is for the ru locale only.

The value for keyword.URL should be:

http://yandex.ru/yandsearch?stype=first&clid=46511&text=

The value for the default start page should be:

http://ru.start2.mozilla.com/?clid=46512

The modified Yandex search plugin is attached.

This bug is marked confidential until the agreement has been announced publicly.
Flags: wanted-firefox3.1?
Flags: blocking-firefox3.1?
Flags: blocking-firefox3.1? → blocking-firefox3.1+
(In reply to comment #0)
> This bug is marked confidential until the agreement has been announced
> publicly.
Does this mean it shouldn't be checked in until then as well?  Do we know when this will be announced publicly?

Lastly, Kev, are you going to generate the patch for this, or should someone else?
Margaret, can you weigh in on when we can make the change public? The sooner the better, so it can be included in beta releases. The agreement is executed, but I just want to make sure we don't surprise anyone if it gets checked into nightlies.

I'll generate the patch this aft and add it.
FYI - the code freeze for beta 3 is January 13th, 11:59pm PST, and technically it's supposed to bake on mozilla-central for a bit too.
Assignee: nobody → kev
Harvey or I will post one very short blog indicating that the partnership is on.  That will be done by end of this week.

Once that is up (and I will update this bug when that happens) we can then make the change public in a non-confidential bug and start getting it in any future beta release builds.

Thanks,
/M
Flags: wanted-firefox3.1?
Priority: -- → P2
(In reply to comment #0)
> The value for the default start page should be:
> 
> http://ru.start2.mozilla.com/?clid=46512

I thought our policy was to not change the search settings for people already using Firefox and that any change would just affect new users... If that's still true, shouldn't this be ru.start3.mozilla.com instead?
Not sure how that would really change things, unless we were talking about users who did not update. I have no objection to using ru.start3.mozilla.com, just so everyone's clear that the default changes will affect all users who update to 3.1.
(In reply to comment #6)
> Not sure how that would really change things, unless we were talking about
> users who did not update. I have no objection to using ru.start3.mozilla.com,
> just so everyone's clear that the default changes will affect all users who
> update to 3.1.

So, if a user currently uses the default start page setting (currently Google), we're just going to change it to Yandex without their permission?
Yes.

We're changing the default providers in 3.1. They are not user-set, they're application defaults. We did this when we moved from Yahoo! to Google in Asia with 2.0, and the changes would only apply to 3.1 and beyond.

After a little more thought, we do have to use a different hostname, as we don't want the change to effect existing users of current and earlier versions.
(In reply to comment #7)
> So, if a user currently uses the default start page setting (currently Google),
> we're just going to change it to Yandex without their permission?

Default providers and settings have always been changed this way - if a user has changed their settings, we respect and keep that change. If they have accepted the default, and if we believe the default should change, then the change should go out to existing and new users. This has been the case before for other changes to defaults ("Latest Headlines", f.e.) as well.

We're making this change because the .ru localization community and our community feels like it's the best choice for users. Feel free to dispute that claim, bringing evidence or rationale, here or perhaps in dev-apps-firefox.
I have no qualms with the change... I was just surprised we were changing what some people may already be using, but I understand your reasoning behind it. :)
Group: mozilla-corporation-confidential
My apologies! And when and where interrogation of Russian community what Yandex is the best choice was spent? Can the best choice for Russian community will Google Chrome, Safari or Internet Explorer?
Why weren't the russian localizers and l10n drivers team on this bug?

Should this bug move over to the russian localization component now that it's public?
(In reply to comment #8)
> We're changing the default providers in 3.1. They are not user-set, they're
> application defaults. We did this when we moved from Yahoo! to Google in Asia
> with 2.0, and the changes would only apply to 3.1 and beyond.

Actually, for the 2.0.0.2 CJKT changes we actually went through a lot of trouble to ensure that they applied only to new users (see bug 364297, particularly bug 364297 comment 5).

We could make use of that technique again, but it's far from perfect (we can only ensure the "no-change" transition for a given upgrade due to bug 380429), and if we're OK with avoiding it for this change it makes our lives much easier.
(In reply to comment #11)
> My apologies! And when and where interrogation of Russian community what Yandex
> is the best choice was spent? Can the best choice for Russian community will
> Google Chrome, Safari or Internet Explorer?

AFAIR, it was internal research. But you can see browser statistics on liveinternet.ru for example and make self decisions. Anyway, it's not 180deg turn, just extension of current possibilities.
(In reply to comment #14)
> (In reply to comment #11)
> > ... when and where ...?
> 
> AFAIR, it was internal research. But you can see browser statistics on
> liveinternet.ru for example and make self decisions. Anyway, it's not 180deg
> turn, just extension of current possibilities.

The problem was originally discussed in great detail in bug #348096 back in 2006.

So it appears that negotiations took about two years, and had several iterations, including Yandex releasing its own branded version of Firefox.  Here's what Harvey Anderson, VP and General Counsel of Mozilla Corporation, has to say:
http://lockshot.wordpress.com/2008/10/15/exploring-partnership-with-yandex/
http://lockshot.wordpress.com/2009/01/09/yandex-partnership-for-search-services/
(In reply to comment #15)
> > AFAIR, it was internal research. But you can see browser statistics on
> > liveinternet.ru for example and make self decisions. Anyway, it's not 180deg
> > turn, just extension of current possibilities.
> 
> The problem was originally discussed in great detail in bug #348096 back in
> 2006.
No, I say about browser market research and what features make Yandex unique in Russia.

> 
> So it appears that negotiations took about two years, and had several
> iterations, including Yandex releasing its own branded version of Firefox. 
> Here's what Harvey Anderson, VP and General Counsel of Mozilla Corporation, has
> to say:
> http://lockshot.wordpress.com/2008/10/15/exploring-partnership-with-yandex/
> http://lockshot.wordpress.com/2009/01/09/yandex-partnership-for-search-services/
Thanks for notify about this!
Kev, this bug is assigned to you, are you coming up with a patch?
Per comment #5, is there a preferred way (or any way, for that matter) to specify a locale-specific override for browser.startup.homepage and browser.startup.homepage_reset?
Please disregard the previous comment. Has to be done web-side, and I'll open a separate bug for that. Axel - yes, I'll add a patch.
Should we contact Yandex on bug 428354?
I should let you know something about what you do

Russian Goverment forced employers (and childrens in russian schools too - most worst thing) to use "Russian search system Yandex"

http://www.liveinternet.ru/stat/ru/searches.html - just note that at weekends & russian holidays Yandex lost positions - sometime google win over Yandex at weekends

Look like Mozilla going to help Russian Government to close "iron curtain". Free soft for non-free peoples with non-free search. :(

By the way

Please compare Yandex browsers (wow - IE6-lovers still majority!):

http://www.liveinternet.ru/stat/ru/browsers.html?slice=yandex;lang=en

and Google (IE7&FF3 almost share(!) first place, then Opera 9, and only then IE6)

http://www.liveinternet.ru/stat/ru/browsers.html?slice=Google

Google lovers love new browsers, Yandex lovers love old browsers? FF 3.1 is old browser? 

One free tip - make this "special version" looking like IE 5 and you winner!

And don`t forget to rename shortcut to "ImperNet Explorer" (icon must be blue E)
(In reply to comment #21)
> I should let you know something about what you do
> 
> Russian Goverment forced employers (and childrens in russian schools too - most
> worst thing) to use "Russian search system Yandex"
its FUD. There is no special government direction about that engine must be used for search in Russia. Maybe you approximate local work requires?

> 
> http://www.liveinternet.ru/stat/ru/searches.html - just note that at weekends &
> russian holidays Yandex lost positions - sometime google win over Yandex at
> weekends
Sometimes is not the answer.

> 
> Look like Mozilla going to help Russian Government to close "iron curtain".
> Free soft for non-free peoples with non-free search. :(
> 
> By the way
> 
> Please compare Yandex browsers (wow - IE6-lovers still majority!):
> 
> http://www.liveinternet.ru/stat/ru/browsers.html?slice=yandex;lang=en
> 
> and Google (IE7&FF3 almost share(!) first place, then Opera 9, and only then
> IE6)
> 
> http://www.liveinternet.ru/stat/ru/browsers.html?slice=Google
> 
> Google lovers love new browsers, Yandex lovers love old browsers? FF 3.1 is old
> browser? 
> 
> One free tip - make this "special version" looking like IE 5 and you winner!
> 
> And don`t forget to rename shortcut to "ImperNet Explorer" (icon must be blue
> E)
Feel free to use what you want but don't say it for others. All of your opinions are very strange and irrelevant.
(In reply to comment #21)
> Russian Goverment forced employers (and childrens in russian schools too - most
> worst thing) to use "Russian search system Yandex"

Do you have any evidence (documents or anything else) ?
I hear about it first time.

> Look like Mozilla going to help Russian Government to close "iron curtain".

It looks like a global Conspiracy. :)

You should remember that we discuss a _default_ search engine. Use another search engine if you wish.

You can see that Yandex is most popular for russians in Internet. Yandex don't have 100% ... Your opinion is a proof of that. That is why yandex is not a single search engine in firefox.

> Free soft for non-free peoples with non-free search. :(

Google is a free search ?! :)
>Do you have any evidence (documents or anything else) ?
>I hear about it first time.

Ask any child or teacher. By the way "This bug is marked confidential until the
agreement has been announced publicly" Is it look friendly and open? Why you
think KGB-based Russian Government more open then Mozilla? It was ordinary phone order.

> It looks like a global Conspiracy. :)

Hear it first time too? You know how many journalists killed in Russia every
year? And again you not seen any documented order to kill any of them?

> Google is a free search ?! :)

At least free for use - google not force you to use it with methods similar to
MS Office Open XML propagation - $$ and false. $$ is same "internal research"
written above? Google was set as default search as *best global* search engine.
Why you want russians become local? Maybe Yandex should become global first to
be compared with Google?
(In reply to comment #24)
> Ask any child or teacher. By the way "This bug is marked confidential until the
> agreement has been announced publicly" 

Oh. Please use facts ... not gossip. You can not be verified.

> At least free for use - google not force you to use it with methods similar to
> MS Office Open XML propagation - $$ and false. 

Please stop this flood. This has nothing to do with the bug subject.

Again, we are not discussing technologies of MS or others. We are discussing the default search engine (one of several _available_). And the choice is based on popularity. This is a good motivation.

> Maybe Yandex should become global first to be compared with Google?

Again and again, yandex is more popular than google for russians (You showed us the statistics). This is a global search engine for russians.
Shouldn't this "discussion" be taken to the newsgroups?  This bug is about implementing the change...
Proposed changes.
Attachment #356722 - Attachment is patch: true
this is not flood - just suggestion

Google more popular then Yandex for Linux users in Russia - why Linux build should be affected by this 'patch' too?

look like Chrome have not Linux version yet so should Linux users need to be involved into this mess?

i suggest exclude Linux build from this 'improvement'
Previous patch wasn't done per MDC recommendations. re-submitting.
Attachment #356722 - Attachment is obsolete: true
this is not flood - just suggestion

Google more popular then Yandex for Linux users in Russia - why Linux build
should be affected by this 'patch' too?

look like Chrome have not Linux version yet so should Linux users need to be
involved into this mess?

i suggest exclude Linux build from this 'improvement'
Vyacheslav: First of all, please, do not spam anymore by sending everyone from the CC list emails. This is impolite.

> Google more popular then Yandex for Linux users in Russia

Can you back this claim by any data? Our data shows the opposite.

> why Linux build should be affected by this 'patch' too?

Because our decision is based on the careful consideration of the best option for our users in Russia, not on any selected platform.

> look like Chrome have not Linux version yet so should Linux users need to be
involved into this mess?

Because the decision has nothing to do with Chrome.

Please, before replying next time to this thread once more, read your comment twice and make sure it has no emotional flavor, is valuable for readers and contains all data to back up any of your claims.
FYI. I responded to  Vyacheslav by email explaining him how to avoid such comments in the future and what mistakes he made. Please, do not respond massively to his email to avoid more problems around it. Thanks
my coworker was angry too when i told to him about this 'bug', especially 'blocking-firefox3.1' flag and 'confidencial' status - i guess  this will be common reaction of Open Source Community to Yandex expansion in their world

Well - lets check Linux stats for Russia

Yandex 

http://www.liveinternet.ru/stat/ru/oses.html?=ru@yandex&slice=yandex&id=10&show=rebuild+graph&per_page=10&report=oses.html%3Fslice%3Dyandex

Google

http://www.liveinternet.ru/stat/ru/oses.html?=ru@Google&slice=Google&id=10&show=rebuild+graph&per_page=10&report=oses.html%3Fslice%3DGoogle

Look like 1 against 3 and probably this one 'linuxoid' use Yandex.Market from time to time to check prices for Asus EEE PC :) I hope Yandex.Market present in this patch. Probably almost 100% linux users use Google as default search and 25% of them sometime use Yandex.Market (as i do until Google implement same functionality).

Site search at http://linuxcenter.ru based on Google too at now (i guess they smart guys and they know what they do)

By the way - Windows Vista users prefer Google too in Russia (most Vista based at home laptops and free from admin`s restrictions), maybe better option is to use Yandex at job and Google at home. Maybe Firefox should have Enterprise Edition packed with Yandex plugin (good oportunity for include XForms plugin too).

to my opinion look like Yandex trying to "sell dead bird to blind boy" 
(c) DUMB & DUMBER 
or if you want more serious comparing "sell burning house"

p.s. this comment was readed by me twice and it not contain emotional flower (really)
Vyacheslav: You fail to understand that we are not interested what is browser or OS market share of google vs yandex in Russia beyond oportunnity to promote Firefox among users who don't know about it yet (and more of them seems to be in Yandex market as you mentioned).

> p.s. this comment was readed by me twice and it not contain emotional flower
(really)

Unfortunately it does.

Please, move with your concerns to newgroup, as sdwilsh noted in comment 26 this bug is about implementation of a patch, not discussion on the bowser market share choices. We respect your opinion, but I doubt you will cause anything more than frustration among people on the CC list by your comments.
> Shouldn't this "discussion" be taken to the newsgroups?

Relevant discussion:

http://forum.mozilla-russia.org/viewtopic.php?id=29708
i am banned here - got life-time ban for message about lost dog in flame topic

look like i am born to be victim :(
Whiteboard: [wip patch]
Kev: if you want a reviewer for that patch, please prod gavin.sharp@gmail.com or mconnor@mozilla.com for it.
Depends on: 479240
Whiteboard: [wip patch] → [needs review axel]
Comment on attachment 356726 [details] [diff] [review]
proposed patch for search plugin and region.properties

r=me, putting this patch on the radar of both Stas and Unghost, too. Stas needs to track this in his paper works.

Reading the initial comment, is there an IT bug that describes what to do for the start page?
Attachment #356726 - Flags: review?(unghost)
Attachment #356726 - Flags: review?(stas)
Attachment #356726 - Flags: review?(l10n)
Attachment #356726 - Flags: review+
Whiteboard: [needs review axel] → [needs review stas/unghost]
For the start page, we'll be using the standard URL with default arguments. The hostname for the startpage in 3.1 is being changed to <locale>.start3.mozilla.com (see 479240), and ru.start3.mozilla.com has a CNAME entry for firefox.yandex.ru (active now).
Comment on attachment 356726 [details] [diff] [review]
proposed patch for search plugin and region.properties

Updated https://wiki.mozilla.org/L10n:Firefox_web_services_status:ru to reflect these changes. I usually do this after the patch lands, but let's make an exception here. I'll keep an eye on the landing.
Attachment #356726 - Flags: review?(stas) → review+
Comment on attachment 356726 [details] [diff] [review]
proposed patch for search plugin and region.properties

r=me
Attachment #356726 - Flags: review?(unghost) → review+
Keywords: checkin-needed
Whiteboard: [needs review stas/unghost] → [ready to land]
I don't know if this matters yet, but

you can land this, but

http://ru.start2.mozilla.com/?clid=46512

currently goes to google with the message
The page - www.google.com/?clid=46512 - does not exist.

either the ru.start2.mozilla.com needs a dns record changing so that it goes to yandex or mozilla.com/yandex ? so people running the nightlies have a working startpage?
Andrew: see comment 39 and bug 479240.
Landed on the release branch as well:
https://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ru/rev/722bd4f64c17

This won't make b3 unless we change the signed-off changeset for ru, though, so I guess I'll omit the fixed1.9.1 keyword for now?
Status: NEW → RESOLVED
Closed: 15 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Whiteboard: [ready to land] → [fixed for b4, won't make b3]
Whiteboard: [fixed for b4, won't make b3] → [bug 480598 covers getting this into b3]
(In reply to comment #45)
> This won't make b3 unless we change the signed-off changeset for ru, though, so
> I guess I'll omit the fixed1.9.1 keyword for now?

Axel went ahead and did this in bug 480598.
Keywords: fixed1.9.1
verified FIXED On builds: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; ru; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4 ID:20090423191946
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.