The Mozilla Foundation produces and distributes open source software, notably Firefox and Thunderbird. Since 2005, the Foundation has had a for-profit subsidiary, the Mozilla Corporation, which deals with the development and marketing of Mozilla technologies and products. The Mozilla Corporation shares the aims of the Mozilla Foundation, and reinvests all of its profits towards the mission goals of the Mozilla Foundation.
The Mozilla Corporation was established “to support the Mozilla Foundation’s mission to ensure choice and innovation on the Internet by leveraging the economic value of Firefox which has resulted from its growing marketshare. By forming a commercial subsidiary, the revenue-generating activities of the new entity can provide funds to support development, testing, and productization of the various Mozilla open source technologies.” Basically, though its conception was not profit-motivated, Firefox turned out to be such a good and widely-used product that its use could be monetized. It just made sense to make use of that revenue stream to help support the organization.
Mozilla is a respected and well-known organization. Its model is nontraditional and generative. Its software is open source and free to use, and others are free to distribute and modify them. All the content of its site is copyrighted under a Creative Commons license. Interestingly, most effective restrictions on what one can do with Mozilla’s software stem from Mozilla’s trademark policy. Mozilla is happy to let you do what you want with its software, but there are limitations to how you can talk about and brand what you’ve done.
Mozilla’s trademark policy adheres to the names of its products as well as the symbols used to represent them. The goal of the policy is to make sure uses of their marks are “non-confusing and non-disparaging.” The whole policy is an interesting read, but here are a few examples of some of the rules.
- “Mozilla encourages the use of its trademarks in marketing, fundraising and other publicity-related materials. That includes advertising stating that a person or organization is shipping or selling Mozilla products. Of course, any use of a Mozilla trademark is subject to the overarching requirement that its use be non-confusing. Thus, you can’t say you’re raising money for Mozilla when you’re actually raising it for a Localization Project, say that you’re selling or reviewing the Mozilla Firefox Internet browser when you’re actually reviewing a Community Edition of the Firefox browser, or use the Mozilla logos on the cover of your book or on your product packaging.”
- “Those taking full advantage of the open-source nature of Mozilla’s products and making significant functional changes may not redistribute the fruits of their labor under any Mozilla trademark. For example, it would be inappropriate for them to say “based on Mozilla Firefox”. Instead, in the interest of complete accuracy, they should describe their executables as “based on Mozilla technology”, or “incorporating Mozilla source code.” They should also change the name of the executable so as to reduce the chance that a user of the modified software will be misled into believing it to be a native Mozilla product.”
- “If you want to include all or part of a Mozilla trademark in a domain name, you have to receive written permission from Mozilla. People naturally associate domain names with organizations whose names sound similar. Almost any use of a Mozilla trademark in a domain name is likely to confuse consumers, thus running afoul of the overarching requirement that any use of a Mozilla trademark be non-confusing.”
- “You may make t-shirts, desktop wallpaper, or baseball caps with Mozilla logos on them, though only for yourself and your friends (meaning people from whom you don’t receive anything of value in return). You can’t put the Mozilla logo on anything that you produce commercially — at least not without receiving Mozilla’s permission.”
Mozilla’s use of trademark is somewhat progressive. One characteristic of Mozilla’s trademark policy is that it spends nearly as much time clarifying what uses of its mark are permitted, or ways exceptions can be made to some of the limits Mozilla has, as saying what people cannot do with the marks. From this it can be gleaned that Mozilla did not want its trademark policy to have a chilling effect on the use of its software. People tend to assume the worst when nothing is said about a certain kind of use, so Mozilla makes it very clear what can be done.
The history of Mozilla’s relationship to the RSS feed symbol is interesting. According to the “feed icon guidelines,” the feed icon started as a Mozilla trademark, used in Firefox, but Mozilla has independently given up its trademark on the symbol, putting it out for general use in relation to feeds. Mozilla offers some suggestions for use, but notes that these guidelines “are not legally binding.” Microsoft also uses this symbol in Internet explorer. This development has lead to standardization in this area between web browers.
As these examples show, Mozilla is not interested in preventing the use of their marks as such. Mozilla simply wants to make sure that users have a clear idea of what exactly is associated with Mozilla itself and what is not. Mozilla cannot control the quality of the work of others, so it does not want to risk being associated with shoddy workmanship. Even physically shoddy workmanship, in the case of the Mozilla products reproduced above.
Since Mozilla distributes its products for free, maintaining a reputation for quality is of particular importance. User backlash against a Mozilla software could be quick and conclusive. As this case shows, trademark has a specific and useful role in helping prevent user confusion and helping providers build a reputation for quality. A measured use of trademark benefits users by making it more likely that they will be able to predict the quality of what they use, and benefits providers by allowing them to benefit from the goodwill from the effort they put into creating a quality product – all without hindering competition or innovation.
In the case of Mozilla, it seems that their good faith to not limit innovation through trademark (i.e. relinquishing the rights to the RSS feed symbol) is a crucial component of why they have been so progressive. I wonder if there is any systematic way (such as an industry-wide corporate policy or actual legislation) we could get companies to take this progressive stance if you remove the “good faith” of a foundation/corporation from the equation…
Incidentally, Mozilla’s had significant trademark trouble with the Debian Linux distribution. Debian sticks to a hard-and-fast rule of not including any proprietary materials at all (so no proprietary drivers, no copyrighted artwork, etc.). Mozilla holds copyright to their logo, and refuses to release it under CC or another copyleft license. Because Debian rejects all copyright, they wound up drawing their own alternate artwork and substituting that in for the version of Firefox they shipped with their operating system.
Initially, they kept the Firefox name (with permission from Mozilla). But a couple years after they changed the artwork, Mozilla sent lawyers after them and informed them that their use of the trademarked name was unacceptable. The Debian project chose to resolve the dispute by simply rebranding the browser. Debian these days ships with the “Iceweasel” browser installed by default, which is identical to Firefox except for the artwork and the default inclusion of some proprietary plugins.
I find it ironic that Mozilla’s defense of its trademark here has actually substantially defeated the purpose of trademarks, identification of a product’s source. If Iceweasel is nearly identical to Firefox, it really does come from Mozilla and its name should reflect that. A Debian user who didn’t follow the legal battle would likely (and justifiably) assume that a browser named Iceweasel had very little to do with Firefox. The lack of the Mozilla trademark would therefore be misleading, which is the opposite of the standard model of infringement.
Defining the “source” (in the trademark sense) of an open source software project seems more difficult. When software is proprietary, the mark owner is the single source of distribution for the software: we don’t see these sorts of trademark issues with Internet Explorer because only Microsoft can distribute IE. Open source projects break that coincidence, and the typical result seems to be an awkward tension between free software ideology and aggressive defense of IP rights.