Posts Tagged with “Project”

February 23 — The Mozilla Organization

February 25th, 2008

[Note: I was traveling and unexpectedly without Internet access last week, so this post is a few days late.]

Ten years ago Netscape planted a seed by launching an organization to create an open source development process for future generation browsers. At the time no one knew how that seed would grow, what kind of open source project would develop, how we would build the key aspects of open source and free software development — transparency, leadership through respect, peer review, participation — into the Mozilla project.

Today we know. We’ve built a vibrant open-source project. We’ve built phenomenal products in an extraordinarily competitive environment. We’ve built communities of people who know that their participation makes a difference in their Internet experience. We’ve built opportunities for people to participate in improving their digital lives. We’ve built an organization that no one could have predicted, that has defied all manner of difficulties and flourished.

We continue to build these things today.

Here is the beginning of that organization:



MOUNTAIN VIEW, Calif. (February 23, 1998) – Netscape Communications Corporation (NASDAQ:NSCP) today announced the creation of, a dedicated team within Netscape with an associated Web site that will promote, foster and guide open dialog and development of Netscape’s client source code. As a follow-on to Netscape’s recent announcement to make the first developer release of Communicator 5.0 source code available for free, will act as a focal point for developers who are interested in modifying and redistributing Netscape client source.Accessible today by going to, the Web site will provide a central point of contact and community by encouraging developers to download the client source code, post their enhancements, take part in newsgroup discussions, and obtain and share Communicator-related information with Netscape and others in the Internet community. The site is also accessible through Netscape’s developer Web site at”By making our source code available to the Internet community, Netscape can expand its client software leadership by integrating the best enhancements from a broad array of developers,” said Marc Andreessen, executive vice president of products for Netscape. “This Netscape team will be dedicated to assisting developers in the development of the source code, building a community that addresses markets and needs we can’t address on our own and allowing our customers to reap the benefits through access to superior products.”

“The popularity and success of Apache, the Linux operating system, the BSD version of UNIX and many other software applications prove the value and impact of open source development,” said Linus Torvalds, creator of Linux. “By introducing, Netscape has created an environment that will bring the best of the Internet to a common locale, encouraging developers to create quality products for end users.”

“Netscape is the first major company to exploit the power of the open source strategy,” said Eric S. Raymond, open-source developer and advocate. “Making their client software source code free to developers is a bold move that will do great things for their products.”

As previously announced, Netscape plans to make Netscape Communicator 5.0 source code available to developers and the Internet community beginning later this quarter with the first developer release of the product. More information is accessible today by going to or by accessing Netscape’s DevEdge site.

January 22, 1998 — the Beginning of Mozilla

January 22nd, 2008

Anyone remember this?



MOUNTAIN VIEW, Calif. (January 22, 1998) — Netscape Communications Corporation (NASDAQ: NSCP) today announced bold plans to make the source code for the next generation of its highly popular Netscape Communicator client software available for free licensing on the Internet. The company plans to post the source code beginning with the first Netscape Communicator 5.0 developer release, expected by the end of the first quarter of 1998. This aggressive move will enable Netscape to harness the creative power of thousands of programmers on the Internet by incorporating their best enhancements into future versions of Netscape’s software. This strategy is designed to accelerate development and free distribution by Netscape of future high-quality versions of Netscape Communicator to business customers and individuals, further seeding the market for Netscape’s enterprise solutions and Netcenter business.

In addition, the company is making its currently available Netscape Navigator and Communicator Standard Edition 4.0 software products immediately free for all users. With this action, Netscape makes it easier than ever for individuals at home, at school or at work to choose the world’s most popular Internet client software as their preferred interface to the Internet.

“The time is right for us to take the bold action of making our client free – and we are going even further by committing to post the source code for free for Communicator 5.0,” said Jim Barksdale, Netscape’s president and chief executive officer. “By giving away the source code for future versions, we can ignite the creative energies of the entire Net community and fuel unprecedented levels of innovation in the browser market. Our customers can benefit from world-class technology advancements; the development community gains access to a whole new market opportunity; and Netscape’s core businesses benefit from the proliferation of the market-leading client software.”

Netscape plans to make Netscape Communicator 5.0 source code available for modification and redistribution beginning later this quarter with the first developer release of the product. The company will handle free source distribution with a license which allows source code modification and redistribution and provides for free availability of source code versions, building on the heritage of the GNU Public License (GPL), familiar to developers on the Net. Netscape intends to create a special Web site service where all interested parties can download the source code, post their enhancements, take part in newsgroup discussions, and obtain and share Communicator-related information with others in the Internet community. Netscape will also continue to develop new technologies and offer periodic certified, high-quality, supported releases of its Netscape Communicator and Navigator products, incorporating some of the best features created by this dynamic community.

The ubiquity of Netscape’s client software facilitates Netscape’s strategy of linking millions of individuals to businesses. Today’s announcements will help to further proliferate Netscape’s award-winning client software which today has an installed base of more than 68 million, providing a ready market for businesses using Netscape’s Networked Enterprise software solutions and Netscape Netcenter services. Netscape’s research indicates that in the education market where Netscape’s products are free, the Netscape client software commands approximately 90 percent share, indicating that users tend to choose Netscape when the choice is freely available. Making its browser software free also will enable Netscape to continue to drive Internet standards, maximize the number of users on the Internet, and expand the third-party community of companies and products that take advantage of the Netscape software platform.

Netscape has successfully shifted its business over the past year toward enterprise software sales and to revenues from its Web site business, and away from standalone client revenues. In the third quarter of 1997, standalone client revenues represented approximately 18 percent of Netscape’s revenue, with the rest coming from enterprise software, services and the Web site. Preliminary results for the fourth quarter of 1997, which Netscape announced January 5, show standalone client revenues decreased to approximately 13 percent in the fourth quarter. In the fourth quarter of 1996 by comparison, standalone client revenue represented approximately 45 percent of Netscape’s revenue.

In conjunction with its free client, Netscape separately announced today that it is launching a host of enhanced products and services that leverage its free client software to make it easy for enterprise and individual customers to adopt Netscape solutions. The new products and services reinforce Netscape’s strategy of leveraging market penetration of its popular client software and its busy Internet site to seed further sales of Netscape software solutions in the home and business markets. The new products and services include enhanced subscription and support packages, an investment protection program for Netscape Communicator users, new reduced pricing on Netscape’s retail and enterprise client products, new Premium Services on its Netscape Netcenter online service and Netscape SuiteSpot server software upgrades featuring Netscape client software.

In addition, the company separately announced the launch of an aggressive new software distribution program called “Unlimited Distribution” to broadly distribute its market-leading Internet client software for free. Unlimited Distribution enables Original Equipment Manufacturers (OEMs), Internet Service Providers (ISPs), telecommunications companies, Web content providers, publishers and software developers to download and redistribute Netscape Communicator and Netscape Navigator easily with “no strings attached.” In addition, beginning immediately, individual users can download Netscape Communicator or Navigator for free, register for Netscape Netcenter and, beginning tomorrow, enter the Choose Netscape Sweepstakes to win exciting travel-related prizes including a grand prize of two all-inclusive, seven-night tropical resort vacations.

Individuals can download a free copy of Netscape Communicator client software or the Netscape Navigator browser from the Netscape home page at, or by clicking on any of the thousands of “Netscape Now” buttons on the Internet. Netscape Communicator Professional Edition, which adds features for enterprise customers, will be available for US$29.

Netscape Communications Corporation is a premier provider of open software for linking people and information over enterprise networks and the Internet. The company offers a full line of Netscape Navigator clients, servers, development tools and commercial applications to create a complete platform for next-generation, live online applications. Traded on NASDAQ under the symbol “NSCP,” Netscape Communications Corporation is based in Mountain View, California.

Additional information on Netscape Communications Corporation is available on the Internet at, by sending email to or by calling 650/937-2555 (corporate customers) or 650/937-3777 (individuals).

Hybrid Organizations

January 14th, 2008

Mozilla is an unusual organization, perhaps even unique. But we are part of a new type of organization — organizations that are mission — driven but use market mechanisms to achieve their goals. By “mission driven” I mean an organization that exists to provide social and civic value. In Mozilla’s case we have a public benefit mission — building an Internet that is open and participatory, where people have meaningful choices about their Internet experience. By “market mechanism” I mean that we use tools that non-profit organizations traditionally haven’t. We use financial tools — we sustain ourselves by generating revenue from our activities, rather than relying completely on grants and donations. We also use the “market” to drive change. In the Internet industry today we are promoting open source, innovation and participation by building products people want to use. Because so many people use our products, we are able to influence technical and policy decisions.

Both John and I have been using the phrase “hybrid organization” to describe this group of organizations. It’s a useful word, but not necessarily precise. I’ll get back to that in a minute.

One important point is that Mozilla is not alone in being a hybrid organization. We are very rare in the technology space. And even rarer in having our size and scope in the technology world. But we are part of a large world of organizations that are combining a social purpose with new tools for financial sustainability. That means some smart people have already been thinking about how to describe these new organizations and we can learn from them.

So, what does a “hybrid organization” mean? There seems to be some academic history of using “hybrid” to mean different types of organizations working together. That’s not what we mean. Wikipedia has a definition of “hybrid organization” that is closer, describing them as operating

in both the public sector and the private sector, simultaneously fulfilling public duties and developing commercial market activities. As a result the hybrid organization becomes a mixture of both a part of government and a commercial enterprise.

The first sentence fits the world I’m trying to describe. But the reference to a hybrid organization being partly “government” is not what I think of with Mozilla. With a little poking around on the Web I found not only a nice description of hybrid organizations but also a very well thought out framework for distinguishing between different gradations of hybrid organizations. (Have I said recently how much I love the Web?).

Here I’m going to call out a few points. This is partly because I’m finding the framework useful for thinking about the broad range of organizational structures people are trying. And it’s partly because the materials help set Mozilla within a larger set of organizations working to create social value in new ways. The author describes a spectrum of hybrid organizations, ranging from “corporations practicing social responsibility” to non-profits that generate income. One type of hybrid with this spectrum is the “Social Enterprise” which is

“any business venture created for a social purpose — mitigating/reducing a social problem or a market failure — and to generate social value while operating with the financial discipline, innovation and determination of a private sector business.” Source

This definitely describes the Mozilla Corporation. (I’m leaving aside for the moment whether one applies this designation to the Mozilla Foundation itself; or treats the Mozilla Foundation as more of a pure non-profit parent of a Social Enterprise.

The world of Social Enterprises is further divided into social enterprises where the “social programs and business activities are one and the same” (the “embedded social enterprise”) and where they are related but not necessarily the same (the “related social enterprise”). In our case, our social programs — creating, distributing and helping people enjoy open source software products — and our business activities are the same.

This slide captures all of this in one place. It describes Mozilla extremely well. We are a mission-driven organization, a portion of which (Mozilla Corporation and soon MailCo) perform some traditionally commercial activities as an integral part of accomplishing the mission. (I would like to copy the entire slide, but haven’t yet contacted the author to see how much I can reproduce here.)

“Embedded mission-centric social enterprise.” That’s a lot of words and I’ll probably keep using “hybrid” in most settings. But each of these words has a specific meaning, often capturing a concept I’ve been trying to organize somehow. Each helps place Mozilla among other organizations. How are we like /unlike microfinance? How are we like / unlike How are we like / unlike the Fair Trade organizations? And, it helps distinguish us from the makers of other browsers and products, *whether or not those products are built using open source software.* The open source nature of Firefox and Thunderbird is fundamental; other products in the market may match those (though none do today). The public-benefit, mission-driven nature of Mozilla is also fundamental, and this regard we are very close to unique.

Mitch Kapor and Mozilla

January 12th, 2008

Mitch Kapor recently announced the end of his involvement with the Open Source Applications Foundation and the Chandler project. Included in his comments is the brief note that:

OSAF also served as the fiscal sponsor for the Mozilla Foundation between its spinout from AOL/Netscape and when it secured its own tax-exempt non-profit status. In that respect, it played a small but important role in the great Firefox success story.

This is absolutely true but dramatically understates Mitch’s and OSAF’s role in helping Mozilla. Mitch began assisting Mozilla in late 2002. This was long before discussion with AOL about the the Mozilla Foundation began. 2002 was not the best of times for Mozilla. There was no Firefox. Our product was the Mozilla Application Suite. It was a good product, released in mid 2002. It far exceeded what anyone had expected us to produce and I remain proud of it to this day. But it wasn’t a well-adopted product. It wasn’t glamourous; it wasn’t elegant. It wasn’t the product that would spread like wildfire.

Mitch didn’t help Mozilla to join the bandwagon of something exciting. Mitch helped us because he knew that open source applications are important, and he knew that the browser’s place in an open source ecosystem is critical. I suspect we appeared more like an “ugly duckling” than anything exciting. But Mitch has a good eye for recognizing important things and he stepped up to help us.

I was working on Mozilla as a volunteer at the time, and had been doing so for about a year. I had been laid off from Netscape in early September of 2001. (I actually met Mitch face-to-face for the first time the day I was laid off from AOL. The meeting with Mitch was, as far as I can remember, the only thing that I did after I received the lay-off notice and before I left the building. At the time I knew it was interesting to meet Mitch, but I had no idea what that meeting would set in motion.) In late 2002 Mitch and I talked about me working at OSAF. I said I only wanted to work part-time because I wanted to keep volunteering with Mozilla. Mitch not only agreed, OSAF agreed to subsidize something like a day of week of my time for Mozilla.

Mitch and OSAF’s support of Mozilla grew from there. When the chance came to form the Mozilla Foundation Mitch’s assistance was invaluable. There was financial assistance. There was also Mitch’s personal involvement in helping the Mozilla Foundation get started and strengthening my courage to be responsible for the welfare of our initial employees and the fund-raising we expected to need. (Remember, at that time there was no Firefox, no Google, very little interest in the then-obscure piece of software known as the browser, and no obvious sources of funds.) A number of people thought we should take the $2MM pledge from AOL, hire 2 or 3 people to keep the machines running, and try to last as long as possible. Brendan and I knew more was required but it was a lot to take on. Mitch brought a level of sophistication and assistance that made a big difference in our ability to lay the foundations of the organization we know today. His assistance to me personally was enormous.

The Mozilla Foundation would have come into existence in some form without Mitch — an astonishingly dedicated and talented group of people were determined to see this happen. But it would not have started life anywhere near as strong without Mitch. Even with Mitch’s help, my role in building and funding the Mozilla Foundation was almost more than I could manage. Mitch’s involvement made a big difference. Mitch remains a member of the Mozilla Foundation Board of Directors and I continue to value his input enormously.

Project-Wide Activities

April 16th, 2007

A couple of weeks ago, I informally asked Mozilla Corporation employees what types of work they do that are “project-wide” or not related to Firefox. Here’s a summary of the results.

  • IT Support and Build
    • Hosting of tinderboxes for all Mozilla projects, including Thunderbird, XUL, etc. This includes both application and server support.
    • Support, hosting and maintenance of basic infrastructure — IRC, Bugzilla, CVS, etc. for all Mozilla projects.
    • Provision of ftp services for many of the other projects — often a large amount of traffic that would be cost prohibitive to any of the smaller projects.
    • Support of the community giving network, which hosts infrastructure (Bugzilla, localization) for a range of projects, including Seamonkey, Camino, etc. Build, development and production machines as well as network capabilities are hosted, in both the San Jose and Amsterdam locations. For example, in Q1 2007 the build team spent a good deal of time to get community build Macs set up for each of the Seamonkey, Camino, and Sunbird/Lightning teams.
  • Thunderbird: build, release, QA, marketing, PR and a range of other activities.
  • Web Services: supports extensions for Firefox, Thunderbird, Seamonkey, and Sunbird.
  • Talkback support for Thunderbird, Sunbird, Camino and Seamonkey. This includes the creation of reports for new releases as well as server and symbols management work.
  • The Community Giving program has provided support to the calendar and Bugzilla projects as well as the Oregon State Open Source Lab.
  • The Mozilla Developer Center includes content and documentation for a range of technologies; including XUL platform documentation to help XUL developers.
  • General module owner activities relating to code review and patch management.
  • Mozilla Store operational support.

I doubt this is a conclusive list. Even so, it gives an idea of the types of activities beyond Firefox that happen on a daily basis.

Mozilla Foundation and Project Leadership

May 26th, 2006

The Mozilla project is an enormous worldwide community of people who choose to work together to produce and share technology, products and a passion for the web. The Mozilla Foundation is the official home of the Mozilla project. It has certain special abilities and responsibilities with regard to leadership of the Mozilla project and stewardship of the project’s assets.

In some ways the Mozilla Foundation is like the proverbial “tip of the iceberg.” It’s the easiest part to see, it has a size and structure that is easy to understand. But the heart of the Mozilla project is the enormous, highly motivated, loosely structured set of communities that make the project vibrant. Like the tip of an iceberg the Mozilla Foundation is a good marker for the larger reality and a good place to start an understanding of the project. And like an iceberg, one needs to go far beyond the surface of the Mozilla Foundation to understand the breadth and depth of the Mozilla project.

In other words, the Mozilla project is larger than the Mozilla Foundation and its employees. This fact should be reflected in the way the Mozilla Foundation organizes itself. Employment with the Mozilla Foundation is not and must not become the source of all authority within the Mozilla project. Contributors must have a voice within the Mozilla project unrelated to employment.

In the days before the Mozilla Foundation existed a group of people known as “ staff” provided this voice. staff was a virtual organization which governed the Mozilla project in general, and did so increasingly unrelated to any employment relationship. Some of the functions that staff used to fulfill now live in the Foundation — stewardship of the assets, release of products using the Mozilla name, as examples. So the old model of staff cannot continue unchanged in the world of the Foundation.

Nevertheless, we need a mechanism to recognize, organize and legitimate the leadership of key contributors and community members unrelated to employment status. This mechanism should both (a) organize and amplify this contributor voice and (b) give this voice input and participation into the Mozilla Foundation’s activities.

We have proven policies for ensuring authority unrelated to employment in the development of code itself. We need a way to maintain and update these policies that doesn’t put all leadership in the hands of Mozilla Foundation employees. We also need to ensure contributors can provide leadership in Mozilla project activities other than writing code.

Some may ask “why?” “Why doesn’t the Mozilla Foundation simply take on the leadership and governance role through its employees?” there are many answers to this. First, the Mozilla project is an open source project. We build software through distributed authority based on reputation, peer review, proven results and ability to lead others through results rather than title. This system produces great results, allows new contributors to appear from unexpected places and join us, drives technical excellence and prevents group-think from making us complacent. The operating style of the Mozilla Foundation must reflect this DNA.

Secondly, the Mozilla Foundation does not and will not employ all the great contributors to the Mozilla project. There are far too many contributors for this to be the case. And it is an explicit goal to have volunteers and people employed by different organizations contributing to get broader perspectives into the heart of the project. Expertise and dedication will exist outside of the Mozilla Foundation’s employee base. It is critical that these contributors have an understood, identified, accepted way to participate in the Mozilla Foundation’s activities.

Those people who have been involved in the project for along time have a short hand phrase for this — we say that “ staff needs to be revitalized to provide this role.” Framed more generally the question is: We need a way for participants to exercise leadership and moral authority in the governance and activities of the Mozilla project that is unrelated to one’s employment status. We need to articulate the scope of that leadership and authority and create a mechanism by which that voice is involved in Mozilla Foundation activities.

Identity and process

March 16th, 2006

Last December we had a gathering of people who were critical to shipping Firefox 1.5. It was called the Firefox Summit and it was about 100 people. I think 10 or so came from Europe, and Roger Sidje came all the way from Australia. We had volunteers, Mozilla Foundation and Corporation employees, and employees of other organizations who are deeply involved in shipping Firefox. (It was an astonishing event for me. I spent most of the dinners looking around in amazement. )

We had a general session on Mozilla Project Dynamics and a discussion about keeping the identity and culture of the Mozilla project as we grow. We’re growing in user base, user needs, contributors, program needs, scale of infrastructure, industry stature, employees (both employees of Mozilla Foundation and Corporation, and employees of other organizations), and management. How do we keep the core identify of the project in the midst of this change?

Ben Goodger made a comment that stuck with me and has been connecting with some other thoughts lately. Ben noted that our identity is deeply tied up in how we build software. A continuing focus on openness, peer review, merit, leadership through reputation, influence through action in building software is fundamental to our continued health. In one sense this seems obvious, but I have found it very helpful. There’s a lot going on with Mozilla and Firefox these days; it is very helpful to focus on the fundamental thing we have done well for years and years, even before the world knew of it — we build software in an open, distributed manner where people choose to participate because the project is worthwhile and works at least well enough. I think of this often as I think about how to manage all the new things that are on our plate today. I also think about it in relation to a set of questions about management and an open management style — more on that later.

Where I Am

March 2nd, 2006

My experience with the Mozilla project in 2005 was about a few things:

1. Growing our organization into the stature the rapid adoption of Firefox brought us. We started the year with about 15 people, and an unexpectedly large set of users. Organizationally we needed to get more people involved full time to take care of things, to build our physical infrastructure (with special thanks to the Oregon State University Open Source Lab), to take care of our user base, and to start to add more coordination among our contributors. Coordination means management of resources so we added a few managers to the employee base. Management in an open source project like ours is not as well understood or developed as code development in an open source project, and I hope to describe our thinking more clearly here and to generate discussion before long.

2. We adjusted our organization a bit, forming the Mozilla Corporation as an adjunct to the Mozilla Foundation. Personally, this was a lot of work. It needs more work, in particular to work explain, refine and further develop the roles of the Foundation and Corporation to help guide the Mozilla project.

3. We shipped Firefox and Thunderbird 1.5. This was important to get updated technology to our users and to provide a way to help protect users through automatic update, particularly for improvements related to security and privacy. It was also important to show that Firefox 1.0 wasn’t a one-shot wonder; that we understand how to ship software on a regular basis. We also broadened our search relationships, with Yahoo becoming the default in the Japanese, Chinese and Korean languages.

We did a lot of other things, but these are the chunks that occupied me for long periods of time.

In 2006 I see a continued focus on products. This has always been the core of what we do and we will continue to ship great products. For me personally, another large focus is in articulating the overall nature and goals of our organization and the means by which we will seek to achieve them. What is the mission of the Mozilla project? How do we best achieve these? What should the Mozilla Foundation do to help people enjoy free, useful participation in what the Internet offers? How best can the Corporation develop products and technologies to promote this goal? How do we combine management with open source DNA? How can I help bring the open, collaborative and distributed decision-making principles of code development into management and leadership of the Mozilla Corporation?

I don’t think there’s a how-to guide about how to do this 🙂

Technology and Non-Profits

June 1st, 2005

One of my Mozilla-related goals for the last year or so has been to increase the outward focus of the Mozilla project. For years we’ve been so focused on getting a great applications shipped that we’ve been extremely inwardly focused. I’ve been spending a chunk of time lately meeting people who are in and around the Mozilla space, trying to get to know people involved in the consumer side of the Internet and people interested in the non-profit world. (I know a lot of the enterprise folks already, thus the focus on the consumer side.)

I had lunch yesterday with Jim Fruchterman. Jim leads the BeneTech Initiative, a non-profit high-technology organization dedicated to building sustainable technology initiatives that address social problems. I met Jim courtesy of Kevin Lenzo, open source speech technologist from Carnegie Mellon University, who had been exploring uses of open source speech-related technology for providing greater accessibility in software. BeneTech has a range of technology projects in the literacy / accessibility and human rights areas.

Talking with Jim is always great. He’s got great experience with the organizational issues that affect a non-profit. Non profits are subject to both various state laws that govern the operation of a non-profit and various federal laws that govern the tax exempt status. It’s a complex area with only a few technology organizations represented. Any many of these — such as the Apache, Perl and Python Foundations — employ very few if any full time people. So finding someone with a number of years of experience in this area is wonderful.

Jim is also experimenting with different ways of generating funds to sustain these technological projects since traditional models don’t fit. And of course he’s thinking about how to generate funds and remain true to the mission of the project. These topics are very similar to those I think about with regard to the Mozilla project. I’m always drawn in by the process of understanding different perspectives and figuring out new ways to do things and Jim and I get together periodically to trade notes. Yesterday’s conversation was particularly interesting coming so closely after the venture capital focus of last week’s Women’s Technology Cluster awards ceremony. In that case the organizational model is known and the issue is finding the people, technology and market opportunities for successful execution of the model. Jim is trying to do something different, meeting needs of groups of people who aren’t likely to ever generate large return on capital investment. These problems — literacy, accessibility, human rights — need solving, and I hope we find some ways of making our vast technical capabilities available to those who need them so badly and can pay so little. homepage

September 21st, 2004

Bart’s recent blog post asked for comments about the homepage, and so here are mine.

I disagree with the view that “the primary purposes of the homepage should be (1) to generate Firefox downloads and (2) to direct people to the information they are looking for on our site.” The homepage is the main view into the Mozilla project. The Mozilla project is bigger than the Mozilla Foundation and bigger than Firefox downloads. I believe that should reflect this.

End user adoption is obviously a critical factor in the success in the Mozilla project and I totally agree that we need to need to make it easy and desirable for end-users to get Firefox. New end-users are coming to Firefox in record numbers; we should celebrate this success and maintain a strong focus on the end-user experience.

But Firefox is an appealing product because it is an active project with a vibrant community. I am uncomfortable with a home page that doesn’t reflect this.

It may be that the changes Bart has proposed are exactly what I would do with the page if I were designing it and that we agree on the specific look for that makes sense today. I’m not trying to design the page; I’m not the right person for that. But the homepage I would like to see will reflect a broader view of the Mozilla project than Firefox downloads.

Skip past the sidebar