Posts Tagged with “EULA”

Mock-Ups Available for Notices (previously was EULA)

September 17th, 2008

First set of mock-ups

Second post re mock-ups

Firefox without EULAs — Update

September 16th, 2008

We’re still working on this. There’s been a bunch of helpful feedback. We appreciate this. We think we’ve integrated the feedback into something that’s a good solution; different from out last version in both its essence and its presentation and content.

We’ve come to understand that anything EULA-like is disturbing, even if the content is FLOSS based. So we’re eliminating that. We still feel that something about the web services integrated into the browser is needed; these services can be turned off and not interrupt the flow of using the browser. We also want to tell
people about the FLOSS license — as a notice, not as as EULA or use restriction. Again, this won’t block the flow or provide the unwelcoming feeling that one comment to my previous post described so eloquently.

We expect to have the materials that show this plan posted tomorrow morning.

Along with the feedback, there have also been some responses that go beyond anger to nasty, personal attacks.  This is unfortunate. I think we’ve gotten past the vitriol to absorb the underlying issues. It’s possible that we’ve missed something. Sometimes the vitriol masks what would otherwise be a point we might understand and agree with. If that’s the case, we’ll keep working on things. The end result will be better for all of us.

Firefox End User License Agreement

November 8th, 2004

The source code of Mozilla’s browsing and email clients is available under the Mozilla Public License (the “MPL”), an open source license certified by the Open Source Initiative. Until now we’ve used the MPL for our executable releases as well. It hasn’t been a perfect match, as the MPL is aimed at source code. And even if we change the MPL to clearly apply to executables it’s still an odd fit. One might have the right under the MPL to modify the code of the executable, but source code is the natural way to make most modifications.

The MPL is not designed for the average consumer who isn’t interested in the complexity of a license aimed at development methodologies. (That’s assuming the average End User is really interested in any End User License Agreement. Even with all my background in this area I find it tedious to read through End User License Agreements, so I can only imagine that someone who’s not trained in this and only interested in getting something done may not pay much attention to the license.)

Periodically people have suggested that our executables should ship with a EULA rather than the MPL. This is particularly true with Mozilla Firefox, which is aimed at end-users as well as our traditional developer community. So we’ve done this with the 1.0 release. I had hoped to get the EULA included much earlier, but my to-do list is longer than my capacity to execute.

The Firefox EULA is pretty basic. That’s not to say it is as short as I would like — just including the standard clauses takes space. I thought about doing some things with the EULA that aren’t standard in the industry, like talking about distribution rights so that people wouldn’t need to look elsewhere. But it turns out that this adds complexity and I decided to leave this out, at least for now. I’ve written many EULAs in the past — almost every EULA that Netscape every used, in fact. But I haven’t focused on this in recent years, and now I rely on legal counsel to remain up to date and vet the content of the license. In this, as in so many other things, I want to thank Heather Meeker of Greenberg Traurig for her great help and unflagging positive nature in the face of time constraints and great demands.

Many people, especially programmers, ask me why there is so much “shouting” in EULAs. The answer is that consumer protection statutes often require notices to be “conspicuous” so that consumers see them. One way to make things conspicuous is to have them in all capital letters. That leaves the license pretty disturbing to programmers who associate all caps with yelling, but it is hard to change given the legal parameters within which a EULA operates.

We would also like to have translated versions of the Firefox EULA and we’re working on getting this done.

I suspect that the Firefox EULA is not perfect. If I had more time I would have distributed it for review and comment. Firefox 1.0 is only the beginning of great new releases from the Mozilla project, and the license can improve along with other aspects. The Firefox EULA can be found at the Mozilla website.

Skip past the sidebar