1,071
edits
Firefox3/Distro Requirements: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 65: | Line 65: | ||
* DIST-007: Support for command line tools for rebranding on Windows (predominantly) (P1) | * DIST-007: Support for command line tools for rebranding on Windows (predominantly) (P1) | ||
* DIST-008: Digital signature on builds (P1?) | * DIST-008: Digital signature on builds (P1?) | ||
= Customization Checklist = | |||
{| class="fullwidth-table" | |||
!Feature !! Low-Touch !! High-Touch | |||
|- | |||
|<i>Bookmarks/RSS</i> | |||
|- | |||
|Add bookmarks, live bookmarks, bookmarklet, folder to bookmark toolbar and bookmarks folder || P1|| P1 | |||
|- | |||
|Remove a default bookmarks, live bookmarks, bookmarklet, folder to bookmark toolbar and bookmarks folder || P3 || P3 | |||
|- | |||
Determining exactly where bookmarks appear || P1 || P1 | |||
|- | |||
Add RSS feed handler, set default feed handler || P2 || P2 | |||
|- | |||
Extras | |||
|- | |||
Add theme & set default theme || P3 || P3 | |||
|- | |||
Add addon/extension/sidebar/toolbar(s) || P1 || P1 | |||
|- | |||
Support for custom EULA display on first run || P3 || P1 | |||
|- | |||
Search | |||
|- | |||
Add: search engine(s) || P1 || P1 | |||
|- | |||
Reorder search engines (all appearing in build) || P2 || P1 | |||
|- | |||
Add parameters to existing search engine || P2 || P1 | |||
|- | |||
Change existing parameter to search engine || P3 || P1 | |||
|- | |||
Set default search engine || P1 || P1 | |||
|- | |||
URL’s | |||
|- | |||
Set default home page(s) || P1 || P1 | |||
|- | |||
Set default first run page || P1 || P1 | |||
|- | |||
Set default keyword.URL || P3 || P1 | |||
|- | |||
Determining tab order || P3 || P1 | |||
|- | |||
Administration | |||
|- | |||
Set default AUS channel name || P1 || P1 | |||
|- | |||
Support for app.distributor & app.distributor.channel properties || P3 || P1 | |||
|- | |||
Firefox 3 New Features | |||
|- | |||
{Need to include here any new Fx 3 features that might be customized by a partner} | |||
|- | |||
Add/register web service as content handler | |||
|- | |||
Add microformats detectors? | |||
|- | |||
Add microformats handler | |||
|- | |||
Add search engine shortcut key | |||
|} | |||
= Additional Customizations = | |||
These are customizations that have been requested or performed in the past but will not be supported: removing popup blocking, adding domain/site to XPI white list, adding help menu item. | |||
Requests for: compatibility checking prior to install, detecting existing installations | |||
The CCK Wizard includes support for the following: | |||
* Set default proxy configuration | |||
* Change title bar text | |||
* Change animated logo, web page and tooltip used for the animated logo | |||
= Distribution Mechanism Identified = | |||
* Distribute online via HTTP/FTP download | |||
* Distribute via CD/DVD | |||
* Distribute via USB, hard disk or other storage medium | |||
* Pre-install on PC (e.g. OEM) | |||
* Pre-install on a USB drive | |||
* Stream/download interactively and launch (through installation program) | |||
= End of Life Policy = | |||
We need a policy that determines what happens when a partner decides that they no longer want to distribute Firefox or have ceased offering services to their Firefox users. (e.g. partner decides to shutdown and remove the default home page for Firefox users). Can we deliver them an update or re-patriate them to vanilla Firefox? | |||
= Partner Clash = | |||
We need a policy that determines what happens when an existing partner installation is layered with another partner installation. | |||
= Upgrades from Firefox 1.5 = | |||
It is expected that users of Firefox 1.5 (vanilla or partner distributions) would first upgrade to a Firefox 2.0-based released prior to upgrading to a Firefox 3.0-based release. | |||
Note: Users who opt to download Firefox 3 and force install over an existing Firefox 1.5-based installation will have unpredictable outcomes. | |||
Upgrades from Firefox 2.0 | |||
Additional sidegrade, upgrade and downgrade cases are outlined in the Upgrade Document. | |||
= Questions = | |||
* Do we need customization of the Firefox installer? (e.g. EULA, more screens, customized text, language support?) | |||
** Support for a stub installer (allows optional components to be download and installed) | |||
** Support for the stub downloader (as used by DivX) | |||
* Trackability | |||
** After user has downloaded Firefox, should we track the following user actions on some central mozilla.com site? | |||
** Successful installation of setup installer | |||
** Cancellation of setup installation | |||
** First-time startup/activation of Firefox (once per machine) | |||
** First-time startup by a Firefox user (once per OS user) | |||
** First-time startup by a Firefox user profile (once per Firefox profile) | |||
** First-time search by a Firefox user (once per Firefox profile) | |||
** Should we register a GUID for each user? (So that we don’t have to rely on the AUS ping) | |||
* Digital signing of builds - should we sign low-touch builds? Shall we use 2 different certificates for signing? | |||
* Should we include a separate process for detecting existing installations and warning users prior to installation? | |||
* Need to outline a process for dealing with malicious rebranders | |||
* Need to policy to deal with home page resetting | |||
** Is a partner entitled to change the users’ home page (a new default) without prompting the user? | |||
** Is partner allowed to do a server-side redirect? | |||
** Is partner allowed to migrate to a new page after prompting | |||
** When a partner disappears, is Mozilla allowed to prevent users from getting 404’s? How does Mozilla determine this? | |||