EULA for Firefox in all builds

RESOLVED FIXED

Status

()

Firefox
Build Config
RESOLVED FIXED
13 years ago
13 years ago

People

(Reporter: rebron, Assigned: Chase Phillips)

Tracking

Trunk
x86
All
Points:
---
Dependency tree / graph
Bug Flags:
blocking-aviary1.0.3 -

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
Need to include the EULA as part of all release and nightly builds e.g. tar.gz,
Mac builds, and .zip builds.

http://www.mozilla.org/foundation/EULA/
http://www.mozilla.org/foundation/EULA/firefox-en.txt
(Reporter)

Updated

13 years ago
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.0.3?
This isn't necessary/useful.  From a similar issue (stripping of headers on
jarred chrome), this is the legal opinion we got from our IP lawyer:

"If you want to make a license actually bind someone, you need to inform
him of the applicability of the terms of the license prior to "sale" --
which in this case I assume occurs when the user performs the download.
It is not a question of what license is included in the product, but
what license is presented to the recipient at the time of sale.  It
always helps to provide licensing information in a product, just for
clarity.  But including a license in a product is not enough -- hence
all the rigmarole that companies go through to make their licenses
effective -- break the seal licenses, click-to-accept licenses, etc."

If its just for aesthetic or other reasons, fine, but it isn't really useful
from a legal perspective.
not blocking 1.0.3
Flags: blocking-aviary1.0.3? → blocking-aviary1.0.3-

Updated

13 years ago
Flags: blocking-aviary1.1? → blocking-aviary1.1+

Updated

13 years ago
Depends on: 302080

Comment 3

13 years ago
EULAs for Mac Firefox are now in for the 1.5 release (1.8 branch) and on the
trunk.  Bug 302080.

Updated

13 years ago
Depends on: 305686

Comment 4

13 years ago
This is fixed, I believe. 
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Flags: blocking-aviary1.5+
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.