Firefox Rebranding:Worksheet: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(drop obsolete process and point to the current version of policy.)
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Repackaging Worksheet Template =
#REDIRECT [[Partnering/Repacks/Policy and Process]]
 
The Firefox Branding Worksheet & set of questions should be answered to facilitate creation of [https://intranet.mozilla.org/Firefox:Distribution custom-branded Firefox distributions] using the Firefox 2.x product.
 
== System Requirements ==
 
* What overall settings will be used for this release?
** Standard Firefox Settings
** Google Settings
** Yahoo Settings
 
* What platform are required (Win32, Mac, Linux, Vista)?
* In what markets/countries will this be distributed? What locale/locales will this branding need?
** (See http://www.mozilla.com/en-US/firefox/all.html for what's currently available for Fx 2.0 and http://www.mozilla.com/firefox/all.html for what's available for Fx 1.5)
 
== Bookmarks ==
 
* Are there any new bookmarks?
** Bookmark Folder: <Name> <Where?>
** Bookmark 1: <Name>, <URL>, <Where?>
** Bookmark 2: <Name>, <URL>, <Where?>
**Provide the name, the URL and where on the bookmarks system these will appear.
**<Where?> options include: Directly on the Bookmark Toolbar, In a folder on the Bookmark Toolbar, directly on the Bookmark Menu, in a folder on the Bookmark menu. For direct items, should they appear before or after existing bookmarks?
 
== Search Plugin ==
 
* Are one or more new search engines required?
* Which search engine will be default?
* Does this search engine already appear in the locale?
** It's possible for a single locale to override the entire search URL
** It's not possible to add additional parameters to an existing search plugin
* Are any new search engine arguments required? (e.g. rls codes)
 
* If a new search engine plugin is authored:
** What URL and search parameters should be used for the search?
** If appropriate, confirm with partner that a tracking code is included in the search URL parameters and processed correctly.
** '''FILES REQUIRED: 16x16 image for the search engine icon'''
 
== URL Customization ==
 
=== Home page ===
 
Custom Firefox home pages must be similar to existing Firefox Home Page but may be co-branded, see [http://zh-tw.google.mozilla.com/firefox?hl=zh-tw Google Sample]. Individual users may choose to alter the home page after installation.
 
* Home Page URL:
* Any additional Home Page URL parameters? (e.g. rls codes)
 
=== First-run page ===
 
When Firefox launches for the first time, two tabs are shown. The first tab is selected and displays the First Run Page and a second tab displays the Home Page. It is similar to the following:
* Tab 1 (First Run Page):
**https://en-us.www.mozilla.com/en-US/firefox/2.0/firstrun/
**https://de.www.stage.mozilla.com/de/firefox/2.0/firstrun/
**https://en-us.www.stage.mozilla.com/en-US/firefox/2.0/firstrun/
**http://tools.google.com/firefox/fftb
 
* Tab 2 (Home Page):
**http://www.google.com/firefox
**http://www.google.com/firefox?hl=de
 
A custom first-run page is not required. If the partner decides not to provide and host a custom first run page, then the default "Welcome to Firefox" one will be used.
 
* First Run URL:
** Are searches from the home page instrumented with tracking codes? (Confirm that it is a different value than the search plugin tracking code.)
 
=== Updated Page ===
 
This page is managed by Firefox and is used to alert the user that their browser has been updated for security and stability releases. It is not customizable.
 
=== Keyword URL / URL Bar ===
 
The with keyword.enabled set to true (default for Firefox), keyword searches can be performed from the URL bar. These searches typically use either "I'm feeling lucky" searches or a Google Keyword Search. These searches can be customized for other providers. They are not revenue bearing.
 
== Popup Blocking ==
 
* Not offered. Currently we do not permit changes to the default domain whitelists for allowing pop-ups.
 
== Additional Extensions or themes? ==
 
* The repackaging tool has been updated to support additional extensions such as a sidebar, toolbar or other partner extension. These can now be included. Please specify the extensions you wish to include, as well as URLs for the version(s) you intend to include.
 
== For Distro Extension ==
 
Note: The values of these settings are provided by the Mozilla Corporation
 
* What should it be called? Typically, <Partner> Settings
* What should the description be? Configuration settings for the <Partner> distribution of Firefox
* ''HELPFUL FILE: 32x32 image for extension manager''. Ensure that the image has a transparent background for optimal display. If this is not provided, then the default "extension puzzle piece" icon will be displayed.
 
== AUS, Updates & Upgrades ==
 
Note: The values of these settings are provided by the Mozilla Corporation
 
Firefox update (AUS2) has been configured so that when a request comes that starts with a channel named "release-cck-*" it will fallback and use the bits for channel name "release". In normal cases partner updates will use this mechanism.
 
* What is the partner ID for updates?
** app.partner.<partnerID> = <partnerID>
 
For partners that are "subdistros" of Google, the extension building process ensures that proper values are copied from the Google extension (manual subclassing). No special failover is required, e.g. when a Firefox with Real Networks Settings (release-cck-google-realnetworks) browser needs updating, it simply falls back to "release" and get the update. The Real Networks DEX encapsulates all the customization and changes required.
 
= Distro ID =
 
Note: The values of these settings are provided by the Mozilla Corporation
 
* The distribution ID (app.distributor) should be "<partner>".
* The distribution channel ID (app.distributor.channel) should be "<channel partner>" (It should be blank or the preference is not there at all if Mozilla is distributing).
 
= Marketing & Promotion =
* What is the promotion strategy for this build? Where does the partner expect to host this distribution?

Latest revision as of 21:36, 31 March 2015