Lizard Wrangling: Mitchell on Mozilla & More

Mozilla

Participation Plus

June 18th, 2009

So far we’ve used the word “participate” as in: “Mozilla promotes choice, innovation and participation on the Internet.” That’s good, but it’s not enough. Many of us participate in closed systems where the rules are set for us and we don’t see them, certainly can’t change them, and aren’t permitted to “participate” in building the rules. This is true of very popular web services. For example, I “participate” in Flickr and Facebook, but within the system and rules that those organizations set up to meet their own goals. That’s fine; there’s no reason for those sites to change.

Mozilla is trying to build a layer of the Internet that’s different, where “participation” extends to the very core of what we build. I’m still struggling to find a crisp way to describe this. If you’ve got thoughts about how to do this — in any language — I would love to hear them.

Windows 7 Without IE

June 12th, 2009

Yesterday Microsoft announced that it is planning to ship Windows 7 without IE in Europe, and to offer IE separately.

It’s impossible to evaluate what this means until Microsoft describes — completely and with specificity — all the incentives and disincentives applicable to Windows OEMs. Without this it’s impossible to tell if Microsoft is giving something with one hand and taking it away with the other. For example, if Windows marketing dollars are tied to IE or browser-based programs, then the ties to Windows are still distorting the browser market. One could think of many other examples.

As a result it’s also impossible to tell whether this does anything more than change the technical installation process of the OEMs. It will certainly make life more difficult for people upgrading to Windows 7.

mitchell

EC Principles: Synthesis

June 11th, 2009

UPDATE: In an odd coincidence, this post appeared just about the time Microsoft announced plans about shipping Windows 7 without Internet Explorer. This post is a synthesis of the public discussions within the Mozilla community over the past weeks. It is not intended — and certainly won’t serve — as a response to Microsoft announcements or plans.


Of the various principles I proposed, the ones that get the strongest positive response are those that protect the choices people have already made or are trying to make. These are outlined in principles 1: Respecting Previous Choice and 2: Windows Must Not Provide a Technical Advantage to IE.

Another set of principles generate a positive response, but feels much more low-key. This includes principles 5, Microsoft must educate people about other browsers and principle 6, Educating people about other browsers.

Principle 7, IE must support web standards, was controversial as a judicial / regulatory requirement. Many want IE to do this but are even very uncomfortable with a regulatory agency determining technical standards in a wildly changing setting such as today’s internet.

The more direct, product based Principle 3, Windows must enable people to choose other browsers, generated some very positive feedback and also some concerns. The positive response comes from the idea that one can’t address the problem without addressing the product. The concerns seem based in (a) complexity of user experience concerns; (b) concern over unintended consequences. The same is true of remedies that have direct effects on the OEM distribution channel. There’s a recognition the OEMs are third parties with their own goals, and an understanding of how hard it is to effectively change such relationships.

There are also people who argue that no one should be able to tell Microsoft anything about its products. People in this group may reject antitrust laws in general, or may reject their application to this kind of technology, or may not know of their existence. Probably all three play a part. Of those people who accept that antitrust law exists and might be applicable, there is a group that wonders if Firefox itself is solving the problem as its market share grows. In contrast, for many people Firefox is mitigating some of the effects of the tying of IE with Windows but does not change the distorted competitive setting that the tying creates.

From this I can say the following about potential remedies, assuming the EC confirms its preliminary conclusion that Microsoft’s tying of IE with Windows violates EC law.

The most basic aspect of a remedy should be to stop Microsoft from subverting the choice to use a browser other than IE. I gave some examples of this in my earlier posts. This will be increasingly important as use of alternative browsers spreads from the early adopters who are more comfortable with their computers to those for whom making any choice that isn’t the default is a bit scary. Forcing those people to figure out and then choose an alternative browser over and over because Windows has somehow pulled them back into IE is a structural problem. Fixing this is an easy and obvious way to protect consumers.

A further remedy that has been publicly discussed is requiring Windows to enable people to choose other browsers, whether through a ballot or not allowing IE to be the automatic default. In other words, helping more people know they have a choice. The lack of knowledge of this choice and the effect it can make is of course a key problem with today’s competitive structure, and is closely related to the integration of IE into Windows. Enabling more people to understand the choices available to them can have some very beneficial results. It is also complex and this aspect of a remedy must be very carefully crafted. The chances for creating a difficult user experience or unintended consequences are real, and so there is a level of concern about the details of what a remedy would look like among even those who support the principle. This mirrors both the challenge and the opportunity of working to provide greater user choice. The reality of the challenges reflects the great importance of the goal.

Mozilla and Firefox have demonstrated that the piece of software known as the “browser” is critically important to each individual’s online experience and to the overall health of the Internet. Building a setting in which consumers and citizens understand they have a choice, realize they can demand better by changing browsers, and aren’t penalized for doing so is a fundamental step in building an internet that retains vibrancy, innovation and choice.

Commit Access Policy Revised

June 9th, 2009

Mozilla’s policy on obtaining commit access to our main mercurial and CVS repositories has been updated. The discussion leading to this can be found in mozilla.governance (via a newsgroup reader or via Google Groups). The revised policy has been posted and is official as of today. A log of the changes can be found in the appropriate Bugzilla bug, for those who follow Bugzilla.

More On 7 Years of Mozilla Releases

June 7th, 2009

Two artifacts from the Mozilla 1.0 release have got my mind spinning. They are the Mozilla press release for Mozilla 1.0, thoughtfully reprinted in part in an article by Glyn Moody at ComputerWorld, and the T-shirt Tristan posted.

First I noticed how consistent how core message has been. Here’s a couple of excerpts:

Mozilla.org is excited about releasing the Mozilla 1.0 code and development tools to the open source community, and providing developers with the resources they need to freely create and view the presentation of their content and data on the Web,” said Mitchell Baker, Chief Lizard Wrangler at mozilla.org. “As the browser has become the main interface between users and the Web over the past several years, the goal of the Mozilla project is to innovate and enable the creation of standards-compliant technology to keep content on the Web open.”

and

Mozilla 1.0 will be available in the following languages (with more to follow): Asturian, Chinese, Dutch, Estonian, Galician, German,Georgian, Greek, Hungarian, Italian, Japanese, Malay, Polish, Slovak, Sorbian and Ukrainian.

The message from 7 years ago was focused at developers and not so much on consumers, but it’s the same message. Open content and data, standards, Mozilla as a platform enabling many people to innovate, the importance of the browser to the general state of the Web, and the importance of a multi-language Web — these are key themes today as then.

Second, I’m struck by how we have expanded our reach by reaching out to consumers as well as developers. In the early days, the idea was that Mozilla would build technology, and others (such as Netscape) would build products. In fact, in the the very early days some people felt that Mozilla would release only source code, that even releasing an executable version was beyond the scope of the project. Clearly we’ve come a long way.

Tristan’s shirt shows the developer focus. How does one announce the release of a product? By closing a bug, of course. How does one represent this on a t-shirt? By printing the URL of the bug-tracking system. Today we complement the developer focus with a consumer focus as well. That’s a big change.

Finally, I must have worked on that press release in the cold and funky downstairs computer zone in my house — 2002 was during the period in which I was a volunteer at Mozilla after being “laid off” by Netscape / AOL in the fall of 2001. Next week I’ll move to a new Mozilla office. It’s a long way from 2002.

Skip past the sidebar