Wrangler Doodles, green.

Building a Better World through Technology

co-founder Mozilla

( from the LizardWrangling Archive )

Category: Mozilla

  • Big Blog, Little Blog?

    Not long after my post about trademark and localization policy I received a message noting that the post might make sense to Mozilla insiders, but was opaque to others. The suggestion was made that I include history and perspective in such posts so that people don’t end up thinking “what is she talking about?”

    I have to agree that the email author was right — the last message was intended for the Mozilla community, and the localization community in general. I thought about trying to add the background that would make sense for those not already involved, but decided just to get the post out there. I suspect this will be an ongoing tension. A post that provides the history and background of an issue takes a lot longer to write than one with a much more narrow focus. It also makes for a different sort of blog, generally more formal than the norm.

    Overall, I agree it’s good to do this. Or at least, someone should do it for the Mozilla project. And I’m as good a someone as anyone. So I’ll try.

  • Localization Teams and Trademarks

    I know there is angst and unhappiness about potential new localization plans and trademark limits. I knew this somewhat before, but I really know it now. That’s because Tristan, Peter, Axel, Gerv and others have made it a point to bring these concerns to the Mozilla Foundation and make sure we understand how important a topic this is. They’ve also made it clear that we haven’t done a good enough job at working with the localization teams. So we’re going to do a few things.

    First, we’ve made the localization issues a regular topic of discussion with the Mozilla Europe folks. This way the topic won’t get dropped, and we’ll make sure that the Mozilla Foundation does a better job of both listening and communication. It also gives those in Europe an easier, effective way to raise your concerns — talk to the Mozilla Europe folks and they’ll make sure we get the message. We’ll do the same thing with Mozilla Japan. We’ll continue the regular IRC discussions with the localization groups with Mozilla Foundation participation. We’ll try to do a better job of explaining what’s going on and the constraints within which the Mozilla Foundation operates. That’s what I’ll try to do in the rest of this message.

    The Mozilla Foundation believes it is important to make sure that product names such as Firefox are protected as trademarks. If this is not done, then the names can be used by projects and companies that are doing quite different things. For example, we would be very unhappy to see a new browser plugin named Firefox appear that is unrelated to the Mozilla project. We don’t want to see browsers with different technology underpinnings called Firefox. A browser that doesn’t have XUL for example, isn’t Firefox and we don’t want one to appear called Firefox. This would cause immense confusion.

    So having “Firefox” be a trademark is important. This isn’t something I say lightly because having a trademark means that the owner is required to do certain things to keep a trademark viable. A trademark is used to identify the “source of origin” of the item bearing the trademark and to indicate quality. If the trademark is used in ways that don’t reflect the source of origin and quality level, then the trademark is weakened. If weakened enough, a trademark can be lost entirely. This is what happened to former trademarks such as “elevator” which started out as a trademark and become a general purpose noun through lack of enforcement.

    I’m personally not a fan of much of trademark law, as it requires the trademark owner to do things that seem unfriendly to partners and associates. Nevertheless the Mozilla Foundation is going to comply with the requirements of trademark law to protect Firefox, Thunderbird, and other product names. We will do so in as flexible a manner as we can.

    I recognize the effort, commitment and personal investment the localization teams have made to the Mozilla project. I also recognize that the localization teams take a great deal of pride in the releases that result and it is undoubtedly distasteful to think that the Mozilla Foundation many timezones away may somehow suddenly be involved.

    We are currently working with trademark lawyers to determine the core set of trademark requirements, and to identify those things that trademark lawyers like but which aren’t actually absolutely necessary. We want to give the localization teams flexibility. So we’re working to take the legal requirements necessary for trademark protection and figure out implementation policies consistent with our enormous desire to recognize both the importance and the commitment of the localization teams. It’s actually been harder to get a clear picture of this from the trademark experts than I would have thought, and it’s taken more time than I would like as well.

    We’ve spent a lot of time trying to sort this out and talking with folks from Mozilla Europe and the Mozilla Localization Project. We believe we’re getting close to circulating a draft policy. I imagine no one will think it’s perfect (well, maybe someone will, but I’m not counting on that) but hopefully it will be a good, workable balance.

    We hope to have something posted for comment within the next week or so.

  • Welcome Mozilla Japan

    I am thrilled that Mozilla Japan has been launched. Mozilla Japan reflects the vibrancy of the Mozilla-gumi volunteer community that has been active since the early days of the Mozilla project. Several of the Mozilla-Gumi folks are involved with Mozilla Japan so we have a bridge between the project to date and the work of Mozilla Japan. Mozilla Japan also has some new and active participants. Nobua Kita, CEO of Ten Art-ni Corporation is active in open source matters in Japan in general, and has provided invaluable leadership in the formation and vitality of the new organization.

    Mozilla Japan is the second International Affiliate of the Mozilla Foundation; the first was Mozilla-Europe. International Affiliates are independent legal organizations, preferably with nonprofit status. They are not subsidiaries of the Mozilla Foundation. Each Affiliate is run by an independent Board of Directors. The Mozilla Foundation needs to agree on the directors and the scope of activities before we allow the Mozilla name to be used; once this is done we look to the Affiliate to provide leadership for the Mozilla project in their geographical areas.

    Mozilla Europe and Mozilla Japan came into being because Tristan and Peter in Europe and the Steering Committee in Japan (Nobuo Kita, Katsuhiko Momoi, Satoko TakitaYamaguchi and Motohiro Egota) were determined to see something happen. Actually Tristan and Peter came to us early in the life of the Foundation with their plans. It was a frantic time and figuring out how to make an Affiliate program was not at the top of my list. It became the top of my list because Peter and Tristan made it so, because their determination to give the Mozilla project a real voice in Europe was unstoppable.

    The Mozilla project is successful because of the enormous energy people bring, the ways to contribute people dream up and the drive and leadership they provide. Welcome Mozilla-Japan!

  • Odd One Out

    One of the first open source gatherings I attended was a group of 30 or so hosted by Tim O’Reilly in a San Jose Museum sometime in 1999. I had only recently joined mozilla.org full time, was unknown to most people in the group, am not from a technical background, and am a woman to boot. It was hard not to feel out of place.

    Before long there was talk of encouraging an open source culture that values contributions other than code. This was reassuring. It’s one thing to spend my time knowing that I’ll never be deep in the mainstream activity of programming; it’s another to make that effort assuming I would be a complete outsider forever.

    At last year’s OSCON Eric Raymond announced that the Open Source Initiative and ZDNet were launching the Open Source Awards, intended to “to reward and encourage excellence in open-source software.” The Gold (“Grand Master”) and Bronze (“Merit”) awards are for those who write code. ilver (“Special”) Awards ” . . .offer a way to experiment, and will be expected to occasionally lead to the development of new “regular” categories to go with the Merit and Grand Master awards.”

    This year Eric announced the first winners of the Grand Master and Special Awards. Larry Wall was the winner of the Grand Master award — who could argue with that? To my surprise, I was the winner of the “experimental” Silver Award. So surprised that when people began to congratulate me “on the award” I could only think that Firefox or Thunderbird had won another award and I had somehow missed it. When he gave me the award Eric told me it is for authoring the Mozilla Public License and subsequent leadership of the Mozilla project. Only the latter appears on the OSI website. But it’s impossible to talk about leadership in the Mozilla project without talking about Brendan Eich, and so the combination Eric described has to be the correct rationale.

    The chance of me becoming a primo hacker is just about nil. Well, maybe less than that. The Mozilla Public License shows up in the Mozilla code, but nothing else I write ever will. It’s definitely rewarding to learn that my eclectic, code-free contributions are seen as valuable by people other than mozilla.org staff. It’s also another data point that suggests that the elusive “community management” concepts I mentioned in my last post are becoming generally recognized as an important element of the open source world. Maybe this experimental award will become a regular part of recognizing contributors to the open source community.

  • “Community Building” surfaces at OSCON

    “Community” in the open source world is one of those words that seems obvious at first, but is actually pretty elusive. For those folks who saw r0ml’s talk at OSCON, community doesn’t mean what you think it does. “Building” and “managing” communities are even more elusive concepts. What is it? Who does it? Does it have value? If so, who does it benefit? Is it simply overhead?

    I’ve been thinking about community building and management for a while now, and have had periodic and unstructured talks with folks such as Danese Cooper at Sun, Louis Suarez-Potts of OpenOffice, Brian Behlendorf and Ted Leung of Apache, David Axmark of MySQL, Chao Lam of OSAF, and of course mozilla.org staff. Lots of talk, but nothing organized. And to date, there hasn’t been a good way for discussing issues of interest to all of us. We’ve talked about organizing something related to community building, but never gotten to it.

    Then this year at OSCON, something surprising happened. Two separate activities related to understanding “community” occurred. First, Zak Grant of MySQL came to talk to me as part of a survey MySQL is conducting about community-building. I’m always glad when I see the MySQL folks get involved in something I care about. To date, they’ve been organized, gracious, diligent and effective in the areas where I see them in action. It was late when Zak and I found a chance to talk so I can’t recall the specific questions, but I do recall an interest in both learning and communicating what other projects have tried, what works and what doesn’t.

    Then on Thursday evening there was a Birds of a Feather session on “Managing Community.” It was quite astonishing to see this on the agenda. I was late so didn’t hear exactly how it came to be, but I know that Karim Lakhami, a graduate student at MIT’s Sloan school, was instrumental in getting this set up. Karim’s listing of academic studies relating to open source is a great resource. I think some combination of Chris DeBono, Michael Tiemann and Stefano Mazzocchi may also have been involved in organizing this. There were probably about 25 people for the 2 hour BOF, and we covered a lot of ground.

    We started out comparing projects which are driven by individual developers doing what is of interest to them with projects like the Mozilla project where there is an overall roadmap and some degree of project-wide planning and prioritization which affects (or at least informs) what developers work on. The choice of the Mozilla project was not mine; I believe it was Michael Tiemann who suggested it. As a sidenote, I would say that the response to the Mozilla project was very different this year. In the past, we’ve been accepted as important, but not the focus of much real excitement as OSCON. This year was different. Mozilla Firefox and Mozilla Thunderbird are changing the way people think about the Mozilla project, and that change was palpable. Perhaps some of the change may be that we are no longer in the shadow of a corporate sponsor. Stefano may this case clearly when he noted that now he sees some reason to think about fixing the bugs that bother him rather than wait for someone else to do it.

    There was a discussion about corporate involvement, and the difference between companies paying employees who work on open source projects as individual contributors (think IBM and Apache) and companies who have corporate teams chartered to work on open source project through the management structure (think Sun and IBM with the Mozilla project). This in turn lead to an eloquent description from Stefano of the Apache view of collaborative development, and how the need for working together trumps hot-shot hackers. The more people I meet at Apache the more I am struck by the degree of focus on work-style, community building and management. Someone, I believe Sam Ruby noted that sometimes an active community does not develop until the original developer steps back, citing Gump and Cocoon as examples.

    We also talked about how important a name can be for a project. Sam Ruby noted this, the Jabber folks agreed, and I had to grimace and note how the Mozilla project learned the same thing through our iterative renaming process that finally resulted in Firefox.

    One topic we didn’t discuss much is a sort of historical record. I would love to hear people describe the early phases of their projects, who the first people were to get involved, what the early community looked like, how it grow, what made it grow and so on. Maybe next time.

  • Why pay for staff?

    Many thanks to those who took the time to comment on our anniversary message. It’s extremely gratifying to hear first hand from people who appreciate the Mozilla project. Looking back at the message, one thing that pops out at me is the single line about our development team. This really is a key element of our success, so I thought I’d add some detail.

    The Mozilla project has been managed by a virtual organization known as “mozilla.org staff” since the founding of the project. There’s much that could be said about mozilla.org staff, but I’ll leave that for another time. Over the years mozilla.org staff have given a good deal of though about how best to create an independent Mozilla Foundation. One big question was whether the Foundation should have employees, and if so, how many? The Apache Software Foundation doesn’t, or at least didn’t for many years. The GNOME Foundation and Python Software Foundations don’t; the Open Source Applications Foundation does. And if the Mozilla Foundation ought to have employees, how many should we start with?

    We thought about a minimal model, with only 1 or 2 employees. This would certainly have been easier financially. We eventually started out with 11 employees. Mozilla Foundation personnel are divided among: (i) those focused on the project wide resources (technical leadership, infrastructure, tools, website management, builds, releases, QA); (ii) those focused on the codebase itself — Firefox, Thunderbird, Gecko, the DOM, JavaScript; and (iii) a few, like me, focused on all the other things the project and the Mozilla Foundation need to be successful — relationships with commercial contributors and other structured entities like Mozilla Europe, legal structure, trademarks, finances, etc.

    It’s a small group for the scope of the project, but it’s a big group for a non-profit, open source project to support. While the minimal solution was attractive for its low-stress nature, we decided that the project was unlikely to reach its potential without a core group of 10 or so. Here’s why.

    • The World Wide Web is not finished. It’s changing all the time. New content types develop, new technologies develop, and new possibilities emerge. The browser is the means by which all this content is made available to the general population. If the browser doesn’t continue to develop, then the consumer’s ability to enjoy these enhancement stagnates.
    • Browsers and email clients aren’t done yet either. Building a great application of the scope and complexity of an email client or a web browser takes a chunk of focused time. In addition, there’s a whole range of innovative ideas that interact with browsers and email clients. For example, RSS readers can be nicely integrated with both browsers and email, and we’re working on both of these. The underlying components on which the actual end user applications are built require constant development. It’s a lot of work.
    • Speed matters. Decisions about how citizens and consumer experience the web should not be based on what’s good for the business plans for a few giant companies. And yet IE market share is generally reported at above 90%. Mozilla’s success matters in helping to keep the web an open place where the public good matters. The need for action is now.
    • The size and scope of the project. Just keeping track of what’s going on in the Mozilla project takes time. There are about 70 people actively checking into the CVS repository each month, and of course many more active participants who don’t have CVS access. So far this year we’ve released: thirteen milestone releases (four for Firefox, five for Thunderbird, four for the Mozilla Application Suite); five milestone release candidates and four alpha releases for the Mozilla Application Suite. Making the right things happen is a big job even with a set of full-time employees. Verifying the state of the tree on our three official platforms cannot be set aside for very long without making it very hard to figure out what caused a problem to develop. The international community of active participants is large enough that coordinating across the group needs pretty constant attention. And recently the press requests directed to the Mozilla Foundation have been significant. These are thrilling developments for an open source community. Responding to all these needs without a set of people available full-time (or more than full-time) would be beyond daunting.
    • Working with commercial entities. The Mozilla project has always had a high level of involvement with commercial entities and with Mozilla development teams at commercial entities. Trying to coordinate a set of full time paid contributors in these entities through an all volunteer group would be very difficult. For example, last month the Mozilla Foundation, Apple, Macromedia, Opera, Sun and Adobe announced our joint plans for improving the plug-in experience for non – IE browsers. The Mozilla Foundation volunteered to do the initial implementation as the API was being developed. This allowed the group to look at the proposed API in practice, test it out and see whether the API was on the right track very quickly. The Mozilla Foundation was able to do this because we had the right person available full time and we knew we could commit his energies to this project and other participants could rely on this work happening quickly.
    • A wealth of talented people. The launching of the Mozilla Foundation was a unique time, when a core group of key project leaders was available to join the Mozilla Foundation. If we were going to make the decision to have employees, the time to do so was at the founding and not some months later after the key individuals had dispersed.
    • Looking at this setting we decided that the project would not reach its potential without a core group of people working full-time on Mozilla Foundation activities. When I say “we” I mean primarily Brendan Eich, the technical lead of the project and I, with a great deal of help and support from Mitch Kapor. (Mitch is the founder of the Open Source Applications Foundation and now a member of the Mozilla Foundation Board of Directors as well.) Ultimately we decided that the Mozilla project’s role in helping promote an open Internet and provide open source desktop alternatives is important enough that we should aim high. The results of the last year demonstrate what can be accomplished. Running the Foundation is hard work, but I’m thrilled that we have the opportunity to do so.

  • Time flies when you’re having fun

    It’s already been a year since the Mozilla Foundation was created, and it’s been quite a year. The Mozilla Foundation has prospered, our products are receiving rave reviews, consumer and enterprise interest in Mozilla products is at an all time high, the awareness of the importance of choice in browser software is growing and our community remains vigorous and energetic.

    The Mozilla project has long been an open source technology leader. With our new Firefox and Thunderbird products, we are now focusing on bringing a better Internet experience to millions of new users.

    There have been many highlights for the Mozilla Foundation this year:

    • We’ve built a potent development team to lead continued innovation. Our small team is built entirely of veterans with many years of experience in the Mozilla project.
    • We turned our attention to the end user for the first time, after years of being solely a technology project. The result: Firefox (for browsing) and Thunderbird (for email). 1.0 launches for both products are now just a few months away. To help end users we’ve started offering CDs (we ship more than 5000 CDs for every new release!), telephone support and Mozilla wares (our new tshirts are proving to be a big hit). With help from David Shea and others, we’ve also given our web site a make-over.
    • Our friends in Europe have created Mozilla Europe, a non-profit organization that’s working to promote Mozilla throughout the continent. Similar efforts are now underway in other parts of the world.
    • We continue to innovate. Just a few weeks ago, the Mozilla Foundation spearheaded an announcement with Macromedia, Apple, Opera, Sun Microsystems and Adobe to deliver a richer plugin experience. Mozilla engineers are active participants in the WHAT Working Group, a collaborative effort with Opera and Apple engineers to bring innovation to web forms and other parts of the web.
    • US CERT, a division of the US Department of Homeland Security, recently recommended that Internet Explorer users switch to a different browser to avoid recent dangerous security exploits affecting IE. Secunia, a leading third party security firm, also recommends using another browser.

    The results?

    • 5.5 million downloads of Mozilla products in the last 30 days, including over 3 million downloads of Mozilla Firefox. That’s close to 200,000 downloads a day for the last 30 days.
    • More than 300 million page views on our web site for the year. This month alone, an estimated 10 million visitors have come to mozilla.org – and we’re just halfway into the month.
    • Amazing buzz for Firefox, with more than 20,000 web sites linking to the Firefox product page!

    Most importantly, the tide is finally beginning to turn: after years of increasing monopolization of the web browser market, Mozilla-based browsers (browsers based on the Gecko rendering engine, that is) are now gaining modest but noticeable market share. Both Web Side Story and OneStat.com, leading web analytics firms, confirm this trend.

    All of this terrific news wouldn’t have been possible without help from lots of individuals and organizations. The Mozilla Foundation is a small organization (just a dozen people), but we have lots of friends and contributors:

    • Financial assistance from AOL, IBM, Sun Microsystems and Mitch Kapor allowed us to launch the Foundation.
    • IBM, Sun Microsystems, Red Hat and others employ dozens of engineers who dedicate their full time energy to the Mozilla Foundation.
    • MozillaZine has become a lively hub for Mozilla news, community feedback and end user support.
    • MozDev is home to hundreds of extensions and other projects that keep Mozilla on the leading edge.
    • Close to 4000 individuals have donated almost $10,000 per month to the Mozilla Foundation.
    • The Visual Identity Team has done an amazing job on the Firefox and Thunderbird logos and default themes – and they’re not done yet!
    • A consortium of universities, lead by Oregon State University, is providing server infrastructure helping meet bandwith requirements for our significant (and growing) downloads.
    • MozSource, the company that operates the Mozilla Store, ships thousands of CDs and Mozilla merchandise every month, processes a good chunk of the donations coming to the Mozilla Foundation, and is now sponsoring SilverOrange to improve the Mozilla web site. SilverOrange is also doing a lot of this work on a volunteer basis.
    • Most importantly: the thousands of hackers and testers who participate in producing great software.

    What’s next? Firefox and Thunderbird 1.0 — just around the corner. But don’t wait. Download the preview releases today and help spread the word. And if you prefer to go with a proven, mature Internet suite that’s been around for years, make sure to download Mozilla 1.7.

    Help us take back the web!

    – The Mozilla Team