Mozilla Admits Firefox EULA Is Flawed
darthcamaro writes "Mozilla has now come around and is taking seriously the concerns of Ubuntu and others about the Firefox EULA, which we discussed vigorously the other day. In fact Mozilla told InternetNews.com that the EULA itself is flawed and will be replaced with something else. Quoting Mozilla Chairperson Mitchell Baker from the article: 'There is a need for something, something to explain the license[.] I'm not sure I would call it a EULA because that has a meaning to many people of adding restrictions to software and we won't be doing that. We'll be having a license agreement much as Red Hat has a license agreement that says the software is available under the GPL and don't use our trademarks et cetera. So we'll have a license agreement but we won't think of it as a EULA.'"
Do I have to accept it in order to proceed? If I do, it's a EULA no matter what you call it.
You're going to have a License Agreement presented to the End User.. Maybe call it LAEU?
It's walking like a duck and quacking like a duck.
"So we'll have a license agreement but we won't think of it as a EULA"
hmm yeah we need some sort of agreement.. an agreement with the user.. that lets them know the terms of our license.. you know for our trademarks and stuff... but not a EULA.
I wonder if there's an acronym for this user agreement to our license thingy...
I came to the datacenter drunk with a fake ID, don't you want to be just like me?
Nobody has to agree to the GPL to use a GPL'ed piece of software -- only to gain additional rights like redistribution. All Mozilla really needs to do is to look at the Trolltech / Qt situation, and then look around and see real alternatives to their product (Opera / WebKit / etc), and they'll wake up and smell the coffee. There isn't enough justification for the EULA hassle just to "explain the license", and that will be worked around by developers and distributions.
Looks like they missed the point.
--
Hey code monkey... learn electronics! Powerful microcontroller kits for the digital generation.
Must... justify... high priced... lawyers...
I am becoming gerund, destroyer of verbs.
"So we'll have a license agreement but we won't think of it as a EULA.'"
They still don't get it. Anything you have to agree to with an "I agree" button, no matter what they call it, is a EULA.
This is a sig. This is only a sig. Had this been an actual sig you would have been informed where to tune for more sigs.
Not only do the GPL bits not belong in the EULA, but the trademark bits don't belong in the EULA either. We're not talking about what end users do, because Mozilla has never stopped end users from doing whatever they want. Mozilla is concerned with distributors repacking Mozilla products with changes they don't like, and misrepresenting their trademark.
They have their license information online. They make it clear to developers how the project can and can not be repackaged while maintaining official branding.
How does any of that relate to the end user?
The answer is to completely remove the nag screen from the end user.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
Lots of software has splash screens, and most people don't have an aneurysm over them. You pop up the brand, mention the trademarks, and in the meantime the software is doing it's thing.
Nice software has an option to turn off the splash screen. But you will probably see it the first time.
Clicking through an "agreement" to not violate their trademark/copyright is dumb. I mean, I've never agreed not to murder anyone...
hmm, mod this redundant or informative as you will, but i feel like it should be pointed out:
EULA: End User License Agreement.
firefox will be replacing this with a license agreement. for whom? the end-user ;)
but i'll forgive them, they're cute. all innocuous and stuff :)
Help -> About?
I'm sure we had the exact same discussion when they tried to get Debian to include a clickthrough licence for Firefox...
Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
That's not the point. They want to protect their trade marks.
They have no problem with the code being distributed within the terms of GPL.
The problem[1] is with using the logos and naming outside of their License Agreement.
I'm not clear on the details[2] other than the distinction between the code and the trade marks. Iceweasel is OK, for example, because it follows GPL and doesn't even bother with the trade marked material.
[1] According to Mozilla
[2] I suppose I could RTFA