MozillaWiki - User contributions [en]

SecurityEngineering/Certificate Transparency

2025-06-25T17:00:47Z

MikeKaply: Add info about the prefix being unnecessary.

[https://certificate.transparency.dev/ Certificate Transparency] (CT) is a system that works to ensure that TLS web server certificates are verifiably publicly disclosed before they can be used, which allows for certificate misissuance to be detected.

== Certificate Transparency Support in Firefox ==
The security engineering team is actively working to implement Certificate Transparency in Firefox. As of version 133, it is enforced in Nightly by default, meaning that every TLS web server certificate in the public web PKI must be accompanied by sufficient certificate transparency information for Nightly to connect without showing an error page. As of version 134, it is enforced in Beta by default. As of version 135, it is enabled by default in Release on desktop platforms.

Certificate transparency is controlled by the preference ''security.pki.certificate_transparency.mode''. A value of '''0''' disables CT entirely. '''1''' enables CT, but does not enforce it, allowing Firefox to collect telemetry on the implementation and the ecosystem. Setting this preference to '''2''' causes Firefox to enforce CT for certificates issued by roots in [[CA|Mozilla's Root CA Program]].

=== Enterprise Policies ===
The preference ''security.pki.certificate_transparency.disable_for_hosts'' can be used to disable enforcing CT for specific hosts. To do so, specify any number of entries separated by commas. Each entry of the form '''example.com''' will disable CT for '''example.com''' and all subdomains of that domain. Entries of the form '''.example.com''' will disable CT for '''example.com''' only. This is intended to be similar to the Chrome enterprise policy [https://chromeenterprise.google/policies/#CertificateTransparencyEnforcementDisabledForUrls CertificateTransparencyEnforcementDisabledForUrls].

The preference ''security.pki.certificate_transparency.disable_for_spki_hashes'' can be used to disable enforcing CT for certificate chains where one of the certificates in the chain has a matching subject public key info. To do so, specify any number of entries separated by commas. Each entry must be the base64-encoded sha-256 hash of a certificate's DER-encoded subject public key info. This is intended to be similar to the Chrome enterprise policy [https://chromeenterprise.google/policies/#CertificateTransparencyEnforcementDisabledForCas CertificateTransparencyEnforcementDisabledForCas], but the ''sha256/'' prefix is not included.

Both of these preferences can be set via [https://mozilla.github.io/policy-templates/#preferences policy].

=== Known CT Logs ===
The list of known CT logs is [https://hg.mozilla.org/mozilla-central/file/tip/security/ct/CTKnownLogs.h#l44 compiled into] Firefox. This list is derived from [https://www.gstatic.com/ct/log_list/v3/log_list.json Chromium's list] and is automatically updated each week in prerelease versions of Firefox.

Each log in the source list is in one of a number of states. Firefox disregards logs that are '''Pending''' or '''Rejected'''. Firefox considers logs that are '''Qualified''', '''Usable''', or '''ReadOnly''' to be '''Admissible'''. Firefox makes notes of logs that are '''Retired''', along with the retirement time.

This information has a 10 week expiration time. That is, if 10 weeks have passed since the information has been updated (typically by updating Firefox itself), the implementation will no longer enforce certificate transparency.

=== CT Policy ===
Certificate transparency information can be delivered either as signed certificate timestamps (SCTs) embedded in the certificate itself or as SCTs stapled alongside the certificate (via the TLS handshake or in an OCSP response). For a connection to succeed, sufficient certificate transparency information must be provided using either of these methods.

For embedded SCTs, "sufficient" means at least N SCTs from distinct logs that were '''Admissible''' or '''Retired''' at the time of verification, where N is 2 for certificates with a lifetime of 180 days or less, and 3 otherwise. At least 1 of those SCTs must be from a log that was Admissible at the time of verification. Among those SCTs, at least 2 must be from distinct log operators.

For SCTs delivered via the TLS handshake or an OCSP response, "sufficient" means at least 2 SCTs from distinct log operators that were '''Admissible''' at the time of verification.

=== CT Log Policy ===
TK

Mach

2023-06-21T17:35:35Z

MikeKaply: Correct link

'''Mach''' is a command-line tool used for building and testing Firefox and other Mozilla projects. For documentation, see '''https://firefox-source-docs.mozilla.org/mach/index.html'''

Distribution INI File

2022-02-03T19:40:50Z

MikeKaply: Removing search stuff that doesn't work anymore.

# Partner Distribution Configuration File
# Author: Dan Mills <thunder@mozilla.com>

# id: short string unique to this distribution
# about: a short descriptive (ui-visible) string for this
# distribution
# version: version of the extra distribution pieces (not the version
# of Firefox)
# bookmarks.initialized.pref: (optional) name of a boolean pref used to determine if bookmarks should be created on startup. This option should not be used except to upgrade from previous customized distributions that did not use the distribution.ini method

[Global]
id=testpartner
version=1.0
about=Afiliado de Prueba
about.en-US=Test Partner
bookmarks.initialized.pref=cck.testpartner.initialized

# This section contains the global js prefs. You do should not list
# the localized preferences here (see below)

# Boolean preferences should be 'true' or 'false', w/o quotes. e.g.:
# my.bool.preference=true
#
# Integer preferences should be unquoted numbers. e.g.:
# my.int.preference=123
#
# String preferences should be in quotes. e.g.:
# my.string.preference="foo"

[Preferences]
mozilla.partner.id="testpartner"
app.distributor="testpartner"
app.distributor.channel=
browser.search.distributionID="com.testpartner"

# This section is used as a template for locale-specific properties
# files. They work similarly to the GlobalPrefs section, except that
# the %LOCALE% string gets substituted with the language string.
#
# This section should only be used for localized string preferences.
# Other preference types will not work.

[LocalizablePreferences]
browser.startup.homepage="http://sandmill.org/%LOCALE%/%LOCALE%/"

# This section is an example of an override for a particular locale.
# The override sections do not interpolate %LOCALE% into strings.
# Preferences set in override sections are *merged* with the
# localizable defaults. That is, if you want a pref in
# [LocalizablePreferences] to not be set in a particular locale,
# you'll need to unset it explicitly ("pref.name=" on a line of its
# own).

[LocalizablePreferences-en-US]
browser.foo="testpartner"
#browser.startup.homepage="http://cheese.com/"
#browser.startup.homepage="http://cheese.com/%LOCALE%/"

# If a directory for the locale the browser is running in doesn't
# exist, Firefox will automatically try the 'default' locale, as defined
# by the distribution.searchplugins.defaultLocale preference.

# Bookmarks

# There are two "toplevel" sections, BookmarksToolbar and BookmarksMenu.
# These can reference other sections via the "folder" type item. These
# folder sections must be named "BookmarksFolder-<id>".

# Each section contains a list of numbered item settings, where each
# item represents a bookmark, livemark, separator, folder, or the default
# bookmarks in that container (if any). The default type is bookmark.
#
# Since Firefox 45, it's possible to set an optional keyword or favicon
# for a bookmark.

[BookmarksToolbar]
item.1.title=Queso
item.1.link=http://queso.com/
item.1.description=Quesos deliciosos!
item.1.title.en-US=Cheese
item.1.link.en-US=http://cheese.com/
item.1.description.en-US=Delicious cheeses!
item.1.title.ja-JP=チーズ
item.1.link.ja-JP=http://ja.wikipedia.org/wiki/%E3%83%81%E3%83%BC%E3%82%BA
item.1.description.ja-JP=美味しいチーズです！
item.2.type=default
item.3.type=separator
item.4.type=folder
item.4.title=Título de la Carpeta
item.4.title.en-US=Folder Title
item.4.folderId=1
item.5.title=Mozilla News
item.5.type=livemark
item.5.siteLink=http://blog.mozilla.com/
item.5.feedLink=http://blog.mozilla.com/feed/

[BookmarksMenu]
item.1.type=folder
item.1.title=Another Folder Title
item.1.folderId=2

[BookmarksFolder-1]
item.1.title=Example Bookmarklet
item.1.link=javascript: alert("hi");
item.2.title=Another Example Bookmark
item.2.link=http://example.com/foo
item.2.description=This is a sample site.
item.2.keyword=example
item.2.icon=<nowiki>http://example.org/favicon.png</nowiki>
item.2.iconData=data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAAAAAA6fptVAAAACklEQVQI12NgAAAAAgAB4iG8MwAAAABJRU5ErkJggg==

[BookmarksFolder-2]
item.1.title=Another Example Bookmarklet
item.1.link=javascript: alert("hello");

Firefox/firefox-dev

2021-07-13T14:38:09Z

MikeKaply: Remove extra plus

==Goals==
[https://groups.google.com/g/firefox-dev firefox-dev] is a mailing list with one explicit goal:

* Offer an easy, transparent venue for getting constructive, Firefox-related development work done and providing development status updates.

and some explicit non-goals:
* It does not offer community members the chance to post until they get satisfaction about their concerns.
* It is not a suitable forum for requesting or offering technical support for users of Firefox
* It is not a suitable forum for unsolicited Firefox feature requests or suggestions

Topics related to add-on development in Firefox are best asked on the [https://matrix.to/#/#addons:mozilla.org Add-ons Matrix channel].

==Subscribe==
You can subscribe by sending an email to [mailto:firefox-dev+subscribe@mozilla.org firefox-dev+subscribe@mozilla.org] or using the Google Groups interface at https://groups.google.com/g/firefox-dev.

==Moderation Policy==
firefox-dev is a moderated list:

* Participants must abide by Mozilla's [https://www.mozilla.org/about/governance/policies/participation/ Community Participation Guidelines]
* Anyone can subscribe and read the messages
* Anyone can post. By default, posts will be reviewed by a moderator before being sent to the list
* A smaller number of contributors will be added to a whitelist, and their postings will go directly to the list without having to first be reviewed by a moderator
* Posts which are ranting, venting, and being unnecessarily argumentative may not go to the list

Messages need to abide by two simple rules to be approved by the moderators:

* Be nice (in other words, no personal attacks, ranting, etc.)
* Be constructive (in other words, no whining, repetition, venting, etc.)

Whitelist membership is subject to temporary or permanent suspension. Abuse or conduct complaints should be sent to <firefox-dev-owner@mozilla.org> or <inclusion@mozilla.com>.

This policy is expected to evolve at the discretion of the list-owner (<firefox-dev-owner@mozilla.org>).

==Archives==
There are read-only archives available:
* [https://groups.google.com/g/firefox-dev via Google Groups]
* [http://dir.gmane.org/gmane.comp.mozilla.firefox.devel provided by Gmane (including NNTP support)]
* [https://mail.mozilla.org/pipermail/firefox-dev/ on the web, via mailman]

Firefox/firefox-dev

2021-07-13T14:37:45Z

MikeKaply:

==Goals==
[https://groups.google.com/g/firefox-dev firefox-dev] is a mailing list with one explicit goal:

* Offer an easy, transparent venue for getting constructive, Firefox-related development work done and providing development status updates.

and some explicit non-goals:
* It does not offer community members the chance to post until they get satisfaction about their concerns.
* It is not a suitable forum for requesting or offering technical support for users of Firefox
* It is not a suitable forum for unsolicited Firefox feature requests or suggestions

Topics related to add-on development in Firefox are best asked on the [https://matrix.to/#/#addons:mozilla.org Add-ons Matrix channel].

==Subscribe==
You can subscribe by sending an email to [mailto:firefox-dev+subscribe@mozilla.org firefox-dev++subscribe@mozilla.org] or using the Google Groups interface at https://groups.google.com/g/firefox-dev.

==Moderation Policy==
firefox-dev is a moderated list:

* Participants must abide by Mozilla's [https://www.mozilla.org/about/governance/policies/participation/ Community Participation Guidelines]
* Anyone can subscribe and read the messages
* Anyone can post. By default, posts will be reviewed by a moderator before being sent to the list
* A smaller number of contributors will be added to a whitelist, and their postings will go directly to the list without having to first be reviewed by a moderator
* Posts which are ranting, venting, and being unnecessarily argumentative may not go to the list

Messages need to abide by two simple rules to be approved by the moderators:

* Be nice (in other words, no personal attacks, ranting, etc.)
* Be constructive (in other words, no whining, repetition, venting, etc.)

Whitelist membership is subject to temporary or permanent suspension. Abuse or conduct complaints should be sent to <firefox-dev-owner@mozilla.org> or <inclusion@mozilla.com>.

This policy is expected to evolve at the discretion of the list-owner (<firefox-dev-owner@mozilla.org>).

==Archives==
There are read-only archives available:
* [https://groups.google.com/g/firefox-dev via Google Groups]
* [http://dir.gmane.org/gmane.comp.mozilla.firefox.devel provided by Gmane (including NNTP support)]
* [https://mail.mozilla.org/pipermail/firefox-dev/ on the web, via mailman]

Firefox/firefox-dev

2021-07-13T14:35:05Z

MikeKaply: Update all links

==Goals==
[https://groups.google.com/g/firefox-dev firefox-dev] is a mailing list with one explicit goal:

* Offer an easy, transparent venue for getting constructive, Firefox-related development work done and providing development status updates.

and some explicit non-goals:
* It does not offer community members the chance to post until they get satisfaction about their concerns.
* It is not a suitable forum for requesting or offering technical support for users of Firefox
* It is not a suitable forum for unsolicited Firefox feature requests or suggestions

Topics related to add-on development in Firefox are best asked on the [https://matrix.to/#/#addons:mozilla.org Add-ons Matrix channel].

==Subscribe==
You can subscribe by sending an email to [mailto:enterprise+subscribe@mozilla.org enterprise+subscribe@mozilla.org] or using the Google Groups interface at [https://groups.google.com/g/firefox-dev].

==Moderation Policy==
firefox-dev is a moderated list:

* Participants must abide by Mozilla's [https://www.mozilla.org/about/governance/policies/participation/ Community Participation Guidelines]
* Anyone can subscribe and read the messages
* Anyone can post. By default, posts will be reviewed by a moderator before being sent to the list
* A smaller number of contributors will be added to a whitelist, and their postings will go directly to the list without having to first be reviewed by a moderator
* Posts which are ranting, venting, and being unnecessarily argumentative may not go to the list

Messages need to abide by two simple rules to be approved by the moderators:

* Be nice (in other words, no personal attacks, ranting, etc.)
* Be constructive (in other words, no whining, repetition, venting, etc.)

Whitelist membership is subject to temporary or permanent suspension. Abuse or conduct complaints should be sent to <firefox-dev-owner@mozilla.org> or <inclusion@mozilla.com>.

This policy is expected to evolve at the discretion of the list-owner (<firefox-dev-owner@mozilla.org>).

==Archives==
There are read-only archives available:
* [https://groups.google.com/g/firefox-dev via Google Groups]
* [http://dir.gmane.org/gmane.comp.mozilla.firefox.devel provided by Gmane (including NNTP support)]
* [https://mail.mozilla.org/pipermail/firefox-dev/ on the web, via mailman]

Installer:Command Line Arguments

2020-08-27T16:55:49Z

MikeKaply: Remove all content and have people go elsewhere.

This documentation has moved to https://firefox-source-docs.mozilla.org/browser/installer/windows/installer/FullConfig.html.

Firefox/EnterprisePolicies

2020-05-11T21:06:17Z

MikeKaply: Redirected page to sumo:products/firefox-enterprise/policies-customization-enterprise/policies-overview-enterprise

#REDIRECT [[sumo:products/firefox-enterprise/policies-customization-enterprise/policies-overview-enterprise]]

Firefox/EnterprisePolicies

2020-05-11T21:05:04Z

MikeKaply: Redirect to SUMO

#REDIRECT [[sumo:products/policies-customization-enterprise/policies-overview-enterprise]]

WeeklyUpdates/2019-09-16

2019-09-16T17:56:43Z

MikeKaply: Add Jochai

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* Watch at https://mzl.la/project-meeting-2019-09-16 or anonymously at https://air.mozilla.org. You can also watch on the Mozilla YouTube channel at https://www.youtube.com/watch?v=OB6N8xRMe3k.
* join #weekly-project-call on irc.mozilla.org or Slack for backchannel discussion
* If you plan on presenting, please join the Zoom video chat 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.
* '''Presenters only:''' Zoom Meeting ID: 828 817 988 [https://mozilla.zoom.us/j/828817988 https://mozilla.zoom.us/j/828817988.] Do '''not''' use this room if you're not planning to speak.
* One-tap mobile
** +16465588656,,828817988# US (New York)
** +17207072699,,828817988# US
* Dial-in by your location
** +1 646 558 8656 US (New York)
** +1 720 707 2699 US
** 877 853 5257 US Toll-free
** +61 2 8015 2088 Australia
** +61 8 7150 1149 Australia
** 1800 893 423 Australia Toll-free
** +1 647 558 0588 Canada
** +33 1 8288 0188 France
** +33 7 5678 4048 France
** 0 805 082 588 France Toll-free
** +49 30 5679 5800 Germany
** +49 69 8088 3899 Germany
** +49 30 3080 6188 Germany
** 800 724 3138 Germany Toll-free
** +852 5808 6088 Hong Kong, China
** +44 203 695 0088 United Kingdom
** +44 203 966 3809 United Kingdom
** +44 203 051 2874 United Kingdom
** 0 800 031 5717 United Kingdom Toll-free

__TOC__

= Weekly Project Status Meeting Agenda =

Items in this section will be shared during the live status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* The add-ons team would like to send cheers to Cesar Carruitero for updating dependencies in our [https://github.com/mozilla/sign-addon/pull/268 sign-addon] repository. Updates like this are difficult, time-consuming, and require a lot of research; contributors who contribute patches like this are greatly appreciated.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* Homebrew Website Club
** The '''Homebrew Website Club''' is a growing world-wide network of meetups for everyone who wants to take back their web experience from social media silos, and own their online identities, content, and interactions.

* 17:30-19:30 (local times) at
** '''Nürnberg (GERMANY)'''
** '''Karlsruhe (GERMANY)'''
** '''London (ENGLAND)'''
** '''Nottingham (ENGLAND)'''
** '''Seattle (WA)'''
* Details and '''RSVP''': https://indieweb.org/events/2019-09-18-homebrew-website-club

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
* '''Homebrew Website Club'''
** '''Brighton (ENGLAND)''' (every Thursday)
** '''Oakland (CA)''' {{newbadge}}
* Details and '''RSVP''': https://indieweb.org/events/2019-09-19-homebrew-website-club

* [https://docs.google.com/document/d/1i59ph_aEKLWitF8BFrnIZPZTLuaYnwZEi1qxeyhKP0g/edit# Add-ons Show & Tell]
** Bring your add-ons related projects to show and tell!
** 14:30 UTC / 7:30am PST
** Sign ups and call-in info are on the [https://docs.google.com/document/d/1i59ph_aEKLWitF8BFrnIZPZTLuaYnwZEi1qxeyhKP0g/edit# agenda].

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

=== Later Events and Available Tickets ===

'''Mozilla DevRel Complimentary Tickets'''

Our DevRel Sponsorship team sometimes receives complimentary tickets to share with Mozillians interested in attending the following events. Please fill out this form [https://airtable.com/shrRFuIEm7j2a0Gtu Ticket RequestForm ].
If you have questions, reach out to the DevSponsorship Team at devsponsorship@mozilla.com for more details.

'''[https://jsconfbp.com/ JS Conf & CSS Conf Budapest]''' Budapest, Hungary | 2019-09-25 & 2019-09-26-27

'''[https://fitc.ca/event/webu19/ Web Unleashed 2019]''' Toronto, Canada | 2019-09-13-14

'''[https://redevelop.io/ redevelop]''' Bournemouth, England | 2019-20-09

'''[https://ruhrjs.de/ RuhrJS 2019]''' Rotunde Bochum - Bochum Germany | 2019-10-05 to 2019-10-06

'''[http://connect.tech/ CONNECT.TECH]''' Atlanta, GA, USA | 2019-10-16 to 2019-10-18

'''[https://2018.ffconf.org/ ffconf]''' ffconf (formerly known as Full Frontal) Brighton, England | 2019-10-08 to 2019-10-08

'''[https://scriptconf.org/ Script'19: Javascript for Everyone]'''| Linz, Austria | 2019-10-25

'''[https://perfnow.nl/ performance.now ()]'''| Amsterdam, The Netherlands | 2019-11-21 to 2019-11-22

'''[https://halfstackconf.com/ Halfstack]''' London | 2019-11-22

'''[https://2019.webconf.asia/ Webconf Asia]''' Hong Kong | 2019-11-20-23

'''[https://ntnu.edu/wac2019 Web Audio Conference 2019]''' Trondheim, Norway | 2019-12-04 to 2019-12-06

'''[https://halfstackconf.com/ Halfstack]''' Phoenix, AZ | 2020-01-17

''' Mozilla Sponsored Developer Events'''

Current list of Mozilla sponsored developer events (with their start dates) around the globe (DevRel Events team will update):

Silicon Slopes Localization - Cross-Cultural Management | 9/17/19| Salt Lake City

Halfstack | 9/19/19| Vienna

Armada JS | 9-19/19 | Novi Sad, Serbia

re:develop | 9/20/19 | Bournemouth, UK

We Love Speed | 9/20/19 | Lille, France

Web Weekend Kathmandu | 9/21-22/19 | Kathmandu

Finch Front End | 9/23-25/19 | Edinburgh, UK

CSSConf Budapest 2019 | 9/25/19 | Budapest, Hungary

JSConf Budapest 2019 | 9/26-27/19 | Budapest, Hungary

PromptConf | 09/28/19 | Chicago

ARTIFACT Conference | 9/30-10/2 19 | Austin, Texas US

[https://indieweb.org/2019/Amsterdam ❌ IndieWebCamp Amsterdam] | 9/28/19 - 9/29/19 | Amsterdam, NL | 9/28/19 - 9/29/19 | Amsterdam, NL

View Source 2019 | 9/30/19 - 10/2/19 | Amsterdam, NL

Fronteers | 10/3/19 | Amsterdam, NL

RuhrJS 2019 | 10/5/19 | Bochum, Germany

[https://indieweb.org/2019/NYC 🗽 IndieWebCamp New York City 2019] | 10/5/19 - 10/6/19 | New York City, NY, USA

Paris Web 2019 | 10/10-12/19 | Bois-Colombes and Paris, France

Web Engines Hackfest 2019 | 10/14/19 | Galicia, Spain

CONNECT.TECH | 10/16/19 | Atlanta, GA, USA

[https://indieweb.org/2019/Brighton 🎪 IndieWebCamp Brighton 2019] | 10/19/19 - 10/20/19 | Brighton, England

2019 LLVM Developers' Meeting | 10/22/19 | San Jose

a11yTO Conf | 10/24/19 | Toronto

Script'19: Javascript for Everyone 10/25/19 | Linz, Austria

Security BSides Portland | 10/25-26/19 | Portland, USA

beyond tellerrand // | BERLIN 2019 | 11/4/19 | Berlin, Germany

CascadiaJS | 11/07/19 | Seattle

ffconf | 11/8/19 | Brighton, UK

RustFest Barcelona | 11/09/19 | Barcelona

Performance now |11/21-22/19 | Amsterdam, The Netherlands

Halfstack | 11/22/19| London

WebConf Asia | 11/20-23| Hong Kong

webclerks community conference | 11/25/19 | Vienna

Web Audio Conference 2019 | 12/4/19 | Trondheim, Norway

dotJS 2019 | 12/5-6/19

Halfstack | 01/17/20 | Phoenix

JS Kongress Munich | 04/15-16/20 | Munich, Germany

[https://indieweb.org/2020 ⛰ IndieWeb Summit 2020] | 06/27/20 - 06/28/20 | Portland, Oregon, USA

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Elgin-Skye McLaren
| Hubs Community & Events Manager
| Emerging Technologies weekly update
| Hubs Commons
| yes
| n/a
| [https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#September_16th.2C_2019 ET headlines]
|-
| Janice Wait + Chris Lawrence
| Program Officer, Mozilla Foundation and Director of Strategy, Loup Design and Innovation
| Grant for the Web
| remote
| no
| n/a
| [https://foundation.mozilla.org/en/blog/100-million-investment-reshape-economics-web/ Grant for the Web]
|-
| Andrew Krug
| Staff Security Engineer, Enterprise Information Security
| IT MinIT
| Remote, Via PreRecorded Video
| Please play [https://drive.google.com/open?id=1kW7iLMuRpwzQGc59hvRLoB0FzeFsokaD video]
| n/a
|
* [https://drive.google.com/file/d/155oTJ_7bAhvTJQHwKZW-RavfkLYYhSPk/view?usp=sharing Video]
* [https://wiki.mozilla.org/IT/WeeklyMinIT#2019-09-16 MinIT Wiki Shownotes]
|-
| Asa Dotzler
| Team Firefox
| Weekly Browser Update
| MTV
| no
| n/a
| [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2019-09-16 2019-09-16]
|-
| Jochai Ben-Aie
| MOSS
| MOSS Track 1 Committee
| MTV
| no
| [https://docs.google.com/presentation/d/1JkCssNAT2KOyWOwGYz2qAeusw3lulFuHJ_asKM8DR10/edit?usp=sharing Slides]
| [https://www.mozilla.org/en-US/moss/ MOSS Website]
|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-

|-
| Benjamin Wu
| William Lachance
| Toronto office
| Toronto office
| Data platform engineer
|-
|}

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

Deployment:Deploying Firefox

2019-05-31T16:07:09Z

MikeKaply: Remove outdated content.

Please visit https://support.mozilla.org/en-US/products/firefox-enterprise for our current documentation.

MozWeek/Whistler2019

2019-05-28T21:27:41Z

MikeKaply: Add Wednesday to list.

'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''

=='''Dates and Location'''==
Monday, June 17 - Friday, June 21, 2019 (travel days are Monday the 17th & Saturday the 22nd) in Whistler, British Columbia, Canada.

We are staying at eight hotels in Whistler Village. We will have meetings at the [https://meetings.whistler.com/wcc/facility/ Whistler Conference Centre] and three hotels (Fairmont, Westin, Delta)

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to pre-approved and pre-arranged.''

=='''Registration'''==
Registration is now closed. This is an invite-only event. All full time and Upwork employees are expected to attend this all company event. Contractors, Vendors and seasonal employees are included on a case by case evaluation based upon team needs.

Advance registration is required. Attendees will need to wear their event badge at all times, including to evening events. We will have security at our events who will be ensuring everyone in our space should be there. This includes facilitators, and other related business guests.

=====New Hires=====
We have a process to identify new hires each Monday and Brianna will invite all new hires to register and book travel directly on their start date. No action is necessary from hiring managers other than to let them know about the event (please do not forward any links). Please work closely with your recruiting manager as they are aware of all deadlines.

All regular full time new hires must have a start date of May 28 or earlier and in workday by May 10. Final invites will be extended on May 13. Contractors/vendors who are hired after March 21 will not be invited. All eligible attendees have been invited as of May 13, 2019. If you have any questions, please email bmark@mozilla.com.

=='''Immigration'''==
It is important to look into your entry requirements early as some may need to schedule an in-person biometrics appointment. You can check here to see whether you require only a valid passport, [https://www.canada.ca/en/immigration-refugees-citizenship/services/visit-canada/eta.html an eTA], or a visa to enter Canada: http://www.cic.gc.ca/english/visit/visas.asp. You should also research whether you need a transit visa if you have a layover or change planes in a country that requires it.

If you do need a visa you can request a visa invitation letter during registration.

Those who have committed certain legal infractions are not allowed to enter Canada (known as “inadmissible” under [https://www.canada.ca/en/immigration-refugees-citizenship/services/immigrate-canada/inadmissibility/overcome-criminal-convictions.html Canada’s immigration law]). Check here to see if you might be "inadmissible" (you could be turned away at the border if you are inadmissible, so best to know ahead of time!): http://www.cic.gc.ca/english/information/inadmissibility/index.asp and http://www.ezbordercrossing.com/the-inspection-experience/prior-criminal-offenses/crossing-canadian-border-with-a-dui/#.VThVDRfnfVp

If you have concerns about being inadmissible while traveling to Canada for All Hands, please reach out to Casey McGill on the immigration team at cmcgill@mozilla.com as soon as possible.

=='''Week at a Glance'''==
View [https://docs.google.com/spreadsheets/d/1BTwNRj3JpEQHkHJ5njerioDm-C6HYBTXh28DP_1uagE/edit?usp=sharing Week at a glance]

====Monday====
*Monday is travel/arrival day
*Registration
*Welcome Reception from 6:00 pm - 9:00 pm

====Tuesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Whistler voucher dinner

====Wednesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*[https://wiki.mozilla.org/All_Hands/Whistler2019/Demos Demos] (no guests)
*Whistler voucher dinner

====Thursday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Whistler voucher dinner

====Friday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Closing event at The Roundhouse

====Saturday====
*Breakfast (incl guests)
*Departure day only. No scheduled activities.

=='''Food, Drink & Events'''==
Breakfast, lunch & snacks will be provided and paid for centrally for attendees.
*Breakfast is provided at the Whistler Conference Centre Tuesday - Saturday.
*Lunch is provided Tuesday - Friday (you eat where your homeroom is).

Menus for all events will be posted here closer to the event.

Coffee/Espresso will be served by [http://mountcurriecoffee.com/ Mt. Currie Coffee] Tuesday - Friday from 7 am - 10 am in the Whistler Conference Centre.

Allergies/preferences: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options. If you have severe allergies that we need to know about; you can indicate in registration.

===Hosted Evening Events===
We have evening events on the Monday and Friday nights.

====Tuesday, Wednesday & Thursday Night Dinners====
You'll be on your "own" for these three evenings and we'll provide pre-paid vouchers for specific restaurants in Whistler Village (upper and lower options). You will '''NOT''' be submitting expenses for these evenings, and '''any costs above the vouchers will not be reimbursed.''' A list of participating restaurants is [https://docs.google.com/spreadsheets/d/1i0uGVwX_J1lw9D9QZnhP_jXeajcqCWaMSlz1Pup_Uk4/edit#gid=0 here]. More will be added, so feel free to check back.

=====Groups, Restaurants & Reservations=====
Tuesday, Wednesday and Thursday are open group dinners. All large (six or more people) reservations should go through Lisa Carlson (email lcarlson@mozilla.com, Slack @lisa) - she has contacts at every restaurant that accepts the vouchers, and can make it a smooth process for all. She is happy to help with reservations for fewer than six as well. Dinners must stay within the voucher amount provided, at restaurants on the approved list. Any costs above the voucher amounts, or restaurants who are not on the voucher list are not approved expenses, nor should MoCo corporate cards be used to cover any overage. As all restaurants are within Whistler Village, transportation costs are also not approved expenses. In no case should employees expense or use MoCo corporate cards to cover purchases of alcohol outside of team dinners or the voucher amounts. She is happy to help with reservations for fewer than six as well.

The fine print:
*Team events must be hosted using the vouchers, and stay within the voucher amount.
*No expenses over voucher amounts will be approved.
*Volunteer Contributors will have their own vouchers.
*In no case should employees expense or use MoCo corporate cards to cover purchases of alcohol outside of team dinners or the vouchers.
*All restaurants in Whistler recommend advance reservations.

=='''Wellness'''==
We will be offering outdoor fitness classes each morning and early evening. Advance sign up will not be required, but recommended if you want a custom Mozilla towel. [https://docs.google.com/spreadsheets/d/1hl0rb3BV2hNdOSH1haixIZsb7_T5kTRnclAo1wjiGs8/edit?usp=sharing Sign up here].

* Sign up is not required, but recommended if you want swag and reminders.
* 1 hour bootcamp style class, with easy accommodations for anyone. Expect to jump, run, lift and more.
* Bring: water bottle
* Attire: whatever you are comfortable working out in. Recommend athletic shoes at a minimum.
* Guests are welcome. Waivers will be signed when you arrive. No one under 12 will be permitted at Rebagliati Park, no one under 18 permitted at CORE.

=====Tuesday, June 18=====
6 AM CORE fitness Studio
5:30 PM CORE fitness Studio

=====Wednesday, June 19=====
6 AM Rebagliati Park

=====Thursday, June 20=====
6 AM CORE Fitness Studio
5:30 PM CORE Fitness Studio

=====Friday, June 21=====
6 AM Rebagliati Park

=====Saturday, June 22=====
7 AM CORE Fitness Studio

CORE Fitness Studio is located at 4010 Whistler Way, right outside the main entrance of the Whistler Conference Centre.
Rebagliati Park is tucked beside the covered bridge between the Upper and Lower Village and bordered by Fitzsimmons Creek.

=='''Hotel'''==
Hotels are reserved during registration. Mozilla will pay for your hotel room with a check in date of Monday, June 17 and a check-out of Saturday, June 22. A link to self-book any pre/post stays at your hotel will be available, should that be part of your plan. Please do not book your hotel through Egencia.

====Payment on Check-in====
Everyone will be required to present a form of payment on check-in for incidentals. Upon check-in, the hotel will place a pre-authorization hold on your credit card for any incidentals you may incur during your stay (varies by hotel). Upon departure, the hold on your credit card will be removed.

We recommend providing a '''credit card'''. You can provide a debit card (but we really do not recommend it), but they do put a hold of funds on your card and has been problematic for some international travelers in the past. If you are not able to provide a credit or debit card, email mozilla@shworldwide.com and we'll work with the hotel on accommodating your needs.

====Early Check-in or Late Check Out====
Generally, check in begins at 4:00pm (varies by hotel). If you arrive before this time, you may preregister at the Front Desk. Should your room not be available, the Bellstand can assist you in storing your luggage while you begin to enjoy Whistler Village. '''Please note that hotels are unable to guarantee early check-in unless you pre-pay for the previous night.'''

Checkout time is at 11:00am.

====Early Departure====
Please contact mozilla@shworldwide.com if you change your reservation once you check in. There is typically an early departure fee, but we can sometimes negotiate the fee if we are made aware.

====Pre/post====
Links to self-book any pre/post stays - pre (June 14-16) & post nights (June 23-25) - will be emailed once hotels are assigned.

=='''Travel'''==
The Egencia portal instructions were emailed to '''anyone approved to attend'''. New hires will have individual deadlines based upon hire/start date. Approved contractors, vendors, seasonal, status employees have been notified with an email from bmark@mozilla.com with specific instructions.

Specific instructions were emailed to you about how to book, as we have a new process for anyone based outside the US, Canada & Central/South America. You will '''NOT''' be booking your All Hands travel in the new country based site.

To help you choose yours flights, please keep the below shuttle times in mind.
Shuttles TO Whistler from YVR will be provided for flights arriving:
*Sunday, June 16 between 10:00 and 17:00 (flight LANDING time)
*Monday, June 17 between 07:00 and 21:00 (flight LANDING time)

Shuttles TO YVR will be provided for flights with scheduled flight departure times (and you should plan to leave Whistler 5+ hours prior to your flight):
*Saturday, June 22 between 06:00 and 23:00 (flight DEPARTING time)

Should you need to reach someone at Egencia for special circumstances or changes that can't be done online:
*Call: +1 (877) 264-1622 or +1 (417) 521-0273; Hours of operations are Monday – Friday (except holidays) 5:00 AM– 5:30 PM PST or 8:00 AM – 8:30 PM EST (2 pm - 11 pm UTC). If you call outside these hours, you will get an after hours agent, who may not be as helpful.
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday.

'''Important Details:'''
Everyone should plan to arrive in Vancouver (YVR) on Monday, June 17 and leave on Saturday, June 22. Anyone who plans to arrive ahead of that or to stay longer, regardless of the reason, must follow the "arriving early/departing late guidelines." These guidelines also apply if you want to fly in or out of airports other than your home airport and Vancouver (anything custom). A few notes:
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, those approved have been sent separate email.
*Volunteers will be handled separate from this process.
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.
*If you would like to invite someone who is a business partner, facilitator or some other category that isn't an employee or volunteer (not a personal guest/family), email bmark@mozilla.com.
*Change fees will be covered by Mozilla for business reasons only.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, June 17 and leave on Saturday, June 22. Here are some exceptions:
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, June 14 and Monday, June 24, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You will stay in Vancouver any extra nights, as you'll still be responsible for taking the provided transportation. You must have approval from our benefits team in writing (and send to bmark@mozilla.com) prior to booking any travel. Approvals and expenses will not be applied retroactively.
* If you live in a country where work travel is prohibited on Sunday, you may travel on Saturday, June 15, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You will stay in Vancouver any extra nights, as you'll still be responsible for taking the provided transportation. You must have approval from our benefits team in writing (and send to bmark@mozilla.com) prior to booking any travel. Approvals and expenses will not be applied retroactively.
* If you plan to spend some extra personal time in Vancouver/Whistler or nearby (choosing to arrive before Monday, June 17 or depart after Saturday, June 22), you'll need to create an itinerary in Egencia for standard dates/locations within the Egencia Portal and compare to the custom dates/locations you'd like. Please share the difference via email to bmark@mozilla.com or through the approval comment box when you submit the flight. '''You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of YVR w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.''' This scenario also applies for routing through different airports to/from Vancouver than your home airport (ex. a layover in Chicago for a few days, or flying out of something other than YVR). In all cases, flights in and out of Vancouver should be booked via Egencia.
* If you are attending the Sunday/Monday CI event (by invite), you can arrive on Sunday, June 16.
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is '''no unilateral''' "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You will stay in Vancouver any extra nights, as you'll still be responsible for taking the provided transportation. If you choose to go to Whistler early or stay late, self-booked transportation costs will not be reimbursed. This policy does not apply to volunteer contributors, any jetlag recovery costs must be self funded.

====Booking Family Travel====
Whether your family will accompany you on your flight or join us later; and you have two options: direct with the airline (recommended) or through Egencia.

'''Direct (recommended):'''

First, figure out which flights you want to be on as an employee in Egencia. Hold them in Egencia. Find the flights you want for your family on the airline site and book them. Go back to Egencia and book your flights. Once you have both sets of confirmation numbers, call the airline and ask them to LINK your two reservations. This shows that you are traveling together and shouldn't be moved. When you call, you can also ask the airline agent to assign seats together. By booking your family direct on the airline, it gives them "priority" with the airline over people who book via a third party (expedia, booking.com, kayak, etc). These aren't guarantees, but they do help.

'''Via Egencia:'''

We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com

'''Notes:'''

* If your family is arriving on a different flights than you but would like to take advantage of the airport shuttles on Sunday/Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.
* No matter how you book, give yourself a lot of time on departure. We recommend leaving Whistler FIVE hours prior to your flight, longer with family.
* We are unable to accommodate volunteer contributor families/guests.

====Not Flying====
Mozilla will reimburse for mileage and parking (not valet) for those based in the BC area. For those outside of the BC area who are driving, Mozilla will reimburse for mileage up to the equivalent of a benchmark flight. We will not reimburse for mileage if you booked a flight.

Parking options vary by hotel (many don't have lots, or have valet only parking). Non-hotel parking options [https://www.whistler.com/getting-around/parking/ here]. We will not reimburse for valet parking, rental cars, taxis, Lyft/Uber or any other transportation to Whistler EXCEPT the Whistler Shuttle or YVR SkyLynx if you land outside the shuttle windows. If you are choosing to extend your stay on either side, transportation costs are not-reimbursable.

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members.

=====''Air Travel Fine Print''=====
*Change fees will be covered by Mozilla for '''business reasons only'''. If you need a change and have manager approval, email bmark@mozilla.com prior to requesting the change with Egencia. Once you have approval, call Egencia to make the change at +1 (702) 939-2530 or +1-877-264-1622 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.
*Mozilla will '''not''' reimburse for Business/First class upgrades or tickets.
*''Mozilla Frequent Flyer perks do not apply for All Hands''.
*Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

=='''Ground Transportation'''==
====Airport Shuttle====
All Mozillians and guests who have '''flights arriving''' into YVR per below will be transported to Whistler (scheduled arrival time of flight):
*Sunday, June 16 between 10:00 and 17:00 (flight LANDING time)
*Monday, June 17 between 07:00 and 21:00 (flight LANDING time)
''Note - this is different than recent All hands.''

All Mozillians and guests who have '''flights departing''' from YVR per below will be transported from Whistler (scheduled departure time of flight):
*Saturday, June 22 between 06:00 and 23:00 (flight DEPARTING time)

'''Transfer time between the airport and Whistler is 2-3 hours depending on time of day.'''

If you arrive into another airport; or on a different date - ground transportation is on your own to book and pay for, and must have manager approval to expense to your team cost center travel budget. If your family is arriving on different flights than you but would like to take advantage of the shuttles on Monday & Saturday, email their itinerary to mozilla@shworldwide.com.

=====Arrivals to Vancouver (YVR)=====
Look for a greeter holding up a Mozilla sign. Please identify yourself to the greeter and they will direct you to the shuttles.

=====Departures from Whistler Village to Vancouver (YVR)=====
Everyone departing on Saturday, June 22 between 06:00 and 23:00, will receive shuttle transportation to YVR. More details about departures will be sent via email. Plan to depart the hotel 5+ hours prior to your flight time - this allows for a 2 hour transfer time and 3 hours at the airport. If you are departing on Friday night (on your own), we recommend allowing 6 hours.

=====Bringing family?=====
If you are bringing family and are all arriving on Monday, June 17 and departing Saturday, June 22, you may all use our company-arranged transportation provided you request it ahead of time (for your guests). You will do this during registration.

=====Arriving early and/or leaving late (w/ or w/out family)?=====
If you arrive/depart other than the times listed below, you will have to arrange for your own ground transportation, to and from YVR, including rental cars and parking.
*Sunday, June 16 between 10:00 and 17:00 (flight landing time)
*Monday, June 17 between 07:00 and 21:00 (flight landing time)
*Saturday, June 22 between 06:00 and 23:00 (flight departing time)

====Recommended Airport Shuttle (for outside Mozilla shuttle times)====
Approved shuttle: https://www.ridebooker.com/events/all-hands-2019 (note this is a Mozilla specific link with a discount)

Mozilla will reimburse for mileage and parking (not valet) for those based in the BC area. For those outside of the BC area who are driving, Mozilla will reimburse for mileage up to the equivalent of a benchmark flight. We will not reimburse for mileage if you booked a flight.

Parking options vary by hotel (many don't have lots, or have valet only parking). Non-hotel parking options [https://www.whistler.com/getting-around/parking/ here]. We will not reimburse for valet parking, rental cars, taxis, Lyft/Uber or any other transportation to Whistler EXCEPT the [https://www.ridebooker.com/events/all-hands-2019 Whistler Shuttle] if you land outside the shuttle windows. If you are choosing to extend your stay on either side for personal time, transportation costs are not-reimbursable. If you are leaving Friday, [https://www.ridebooker.com/events/all-hands-2019 Whistler Shuttle] is reimbursable up to $58 CAD.

====Vancouver "office" Shuttle====
MONDAY, June 17
Departure time: 1:00 pm
Departure Location: Waterfront Station (601 West Cordova Street)
Arrival Location: Whistler Conference Centre (likely with some shuttles to further hotels)

SATURDAY, June 22
Departure time: 11:30 am
Departure Location: TBD in Whistler
Arrival Location: Waterfront Station (601 West Cordova Street)

=='''Safety & Security'''==
=====Alcohol at Events=====
To better support and sustain an environment (and workplace culture) where people feel safe and included, we have made a set of changes regarding alcohol at our events. In all cases, our approach aligns with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).
*All participants are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.
*We will '''limit bar-servings to beer and wine''' and ensure an equal number and quality (i.e. not just Coke) of non-alcoholic drink options are available and displayed.
*Team dinners should be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.
*Clearly outlined, communicated (to event teams, HR and managers) and understood '''escalation process''' for behavior that might be deemed counter to the spirit of our CPG.

=====Device Security=====
If you are traveling to the All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Physical Security=====
Badges are required to access all meeting spaces and evening events.

=='''Accessibility'''==
====Evenings====
Monday Night reception is at the Whistler Conference Center, on the main level. No stairs or elevators required.

Friday Night reception is at the Roundhouse, on the top of Whistler Mountain. Access is via 25 min ride on a gondola. If you have questions/concerns about this, please reach out to bmark@mozilla.com.

====Meeting spaces====
* Fairmont: [http://www.fairmont.com/whistler/pdf/fairmont-chateau-whistler-meeting-rooms-floor-plans/ floorplans available here]. There is a small lift available just before entering the meeting space on the right. Once on the main meeting space floor, no lifts or elevators are required. 3rd floor meeting rooms are accessible by guestroom elevators.
* Westin: [https://www.marriott.com/hotels/event-planning/business-meeting/ysewi-the-westin-resort-and-spa-whistler/#m-capacity-container floorplans available here]. All meeting space levels are accessible by guestroom elevators.
* Delta: [https://www.marriott.com/hotels/event-planning/business-meeting/ysewv-delta-hotels-whistler-village-suites/#m-capacity-container floorplans available here]. All meeting space is on the ground level, located just off the lobby.
* Whistler Conference Centre: [https://meetings.whistler.com/wcc/facility/ virtual tour and floorplans available here]. Main level (where breakfast and plenary is) is ground level. Lower level is accessible via elevator just inside the lobby.

====Listen Systems====
We will have Listen Systems available for any meeting in the Sea to Sky Ballroom A. Visit the AV booth at the side of the room to pick one up.

====Bathrooms====
The Whistler Conference Center has 4 bathrooms on the main level - 2 gendered bathrooms (with multiple stalls each), 1 non-gendered (multiple stalls) and one non-gendered accessible bathroom.

The Westin has private accessible washrooms on the Lobby Level - by west elevators between men's and women's washroom and the Second Level by west elevators behind Alpine foyer between men's and women's washroom.

The Fairmont meeting spaces have two sets of bathrooms, one by the Macdonald and the other by the Frontenac. Both are stalls are gendered bathrooms, and they do not have separate family or non-gender bathroom options on the meeting space floor. The bathroom next to the Frontenac/Empress does have a larger wheelchair accessible stall in each. The two sets of bathrooms in the lobby area are the same. 3rd floor meeting rooms have a single bathroom inside each room that is not gender specific.

Delta has gendered washrooms located close to the meeting space and have accessible stalls.

====Breastfeeding/pumping stations====
We will have a guestroom available at Westin and Fairmont for breastfeeding/pumping families. Grab a key to the room from the event info desk when you need it (we'll tell you the guestroom number), and turn it back in when you are done. The rooms will have a fridge so you can store what you need for the day, and take it to your guestroom at your hotel at the end of the day. Please plan your day to pick up your stored items at 5:00 pm each day. There is not currently an option at Delta or Whistler Conference Centre, please reach out to bmark@mozilla.com if you think you need an option at either location.

=='''Families/Guests'''==
Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made. Please note that what are able to do for families varies by each location. We are unable to accommodate volunteer contributor or intern families/guests at our All Hands.

====Quick summary logistics====

=====Air Travel=====
Employees do need to book via Egencia regardless of how families are booked. See Air Travel above for specifics and recommendations.

=====Hotel=====
Family/friends are welcome to stay with you, however, any additional room expenses will be yours to cover. All room rates are based upon single occupancy and costs to add guests vary by hotel. Breakfast is not included in any of the guest room rates.

=====Breakfast=====
Family/guests who are registered for the event and registered with the hotel are invited to join us for breakfast each morning. Breakfast will be provided on Tuesday - Friday.

=====Lunch & Dinner=====
Family will be on their own for lunch daily and dinner on Tuesday, Wednesday & Thursday.

=====Monday & Friday Night Events=====
Family members who are registered for the event and registered with the hotel, are invited to join us for our evening events.

=====Family Friendly Activities=====

Visit [https://www.whistler.com/activities/summer/ here] for several options.

=====Childcare Services=====
We will not provide centralized childcare services in Whistler. Please visit [https://www.whistler.com/family/childcare/ here] for Childcare, Babysitting & Camp options.

=='''Whistler All Hands Expense Policy'''==
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. Whistler All Hands Expense Report). Each expense must be tagged with "All Hands - June 2019"

2. It must contain only those expenses relative to the All Hands Event in Whistler. For Tuesday, Wednesday, and Thursday evenings, no expenses above the provided voucher amount is reimbursable.

3. If your submitted expense report for All Hands is submitted outside these guidelines, it will be rejected and you will be asked to re-submit with only All Hands Expenses

4. The deadline to submit the All Hands Expense Report is '''July 31, 2019'''.

5. Expenses related to team events, parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved.

6. Approved ground transportation outside of the Mozilla shuttle is the Whistler Shuttle or YVR SkyLynx shuttles, not to exceed $65CAD each way.

'''The intention of our all hands are to centrally organize a structure that includes:'''
*Meals (2 evening events + Vouchers for 3 nights + breakfast, lunch, drinks and snacks Tuesday - Friday)
*Transportation
*Accommodations

Expenses submitted can not exceed the approved amounts. Any social events that are not part of our central plan will generally be self-organized and funded by participants.

=====Cell phone reimbursement policy=====
Cell phone reimbursement must be approved by your manager prior to submitting the expense. Teams will decide for their staff what is appropriate to expense.

=====Internet reimbursement policy=====
Internet will be provided in all guestrooms and meeting space in all hotels. If you opt to upgrade/add service, those costs are not reimbursable, unless previously approved by your manager and are for business reasons.

If you have questions about any of this, please reach out to bmark@mozilla.com

=='''Activities'''==
* [https://www.whistler.com/activities/ Whistler Activities]
* [[All_Hands/Whistler2019/Running|Running]]
* [https://public.etherpad-mozilla.org/p/whistler-day-hike '''Hiking!''']
* [[All_Hands/Whistler2019/Scuba|Scuba]]
* [[All_Hands/Whistler2019/Tiny Computers|Tiny Computer Hacking]]
* [https://mozilla.slack.com/messages/CJ0J2CU7K/ Magic: The Gathering Draft]

MozWeek/Whistler2019

2019-03-08T15:34:20Z

MikeKaply: Move time info into shuttle section

'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''

=='''Dates and Location'''==
Monday, June 17 - Friday, June 21, 2019 (travel days are Monday the 17th & Saturday the 22nd) in Whistler, British Columbia, Canada.

We are staying at nine hotels in Whistler Village. We will have meetings at the [https://meetings.whistler.com/wcc/facility/ Whistler Conference Centre] and two hotels.

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to pre-approved and pre-arranged.''

=='''Registration'''==
This is an invite-only event. All full time and Upwork employees are expected to attend this all company event. Contractors, Vendors and seasonal employees are included on a case by case evaluation based upon team needs.

Advance registration is required. Attendees will need to wear their event badge at all times, including to evening events. We will have security at our events who will be ensuring everyone in our space should be there.

=====New Hires=====
We have a process to identify new hires each Monday and will invite them to book travel. No action necessary from managers other than to let them know about the event. Please work closely with your recruiting manager as they are aware of all deadlines.

All new hires must have a start date of May 31 or earlier and able to register/book travel by May 13.

=='''Immigration'''==
It is important to look into your entry requirements early as some may need to schedule an in-person biometrics appointment. You can check here to see whether you require only a valid passport, [https://www.canada.ca/en/immigration-refugees-citizenship/services/visit-canada/eta.html an eTA], or a visa to enter Canada: http://www.cic.gc.ca/english/visit/visas.asp. You should also research whether you need a transit visa if you have a layover or change planes in a country that requires it.

If you do need a visa you can request a visa invitation letter during registration.

Those who have committed certain legal infractions are not allowed to enter Canada (known as “inadmissible” under [https://www.canada.ca/en/immigration-refugees-citizenship/services/immigrate-canada/inadmissibility/overcome-criminal-convictions.html Canada’s immigration law]). Check here to see if you might be "inadmissible" (you could be turned away at the border if you are inadmissible, so best to know ahead of time!): http://www.cic.gc.ca/english/information/inadmissibility/index.asp and http://www.ezbordercrossing.com/the-inspection-experience/prior-criminal-offenses/crossing-canadian-border-with-a-dui/#.VThVDRfnfVp

If you have concerns about being inadmissible while traveling to Canada for All Hands, please reach out to Casey McGill on the immigration team at cmcgill@mozilla.com as soon as possible.

=='''Week at a Glance'''==

====Monday====
*Monday is travel/arrival day
*Registration
*Welcome Reception from 6:00 pm - 9:00 pm

====Tuesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Whistler Dine-around

====Wednesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Whistler Dine-around

====Thursday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Whistler Dine-around

====Friday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Closing event at The Roundhouse

====Saturday====
*Breakfast (incl guests)
*Departure day only. No scheduled activities.

=='''Food, Drink & Events'''==
Breakfast, lunch & snacks will be provided and paid for centrally for attendees. Breakfast is provided Tuesday - Saturday and lunch is provided Tuesday - Friday. Menus will be posted here closer to the event.

Allergies/preferences: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options. If you have severe allergies that we need to know about; you can indicate in registration.

===Hosted Evening Events===
We have evening events on the Monday and Friday nights.

====Tuesday, Wednesday & Thursday Night Dinners====
You'll be on your "own" for these three evenings and we'll provide pre-paid vouchers for specific restaurants in Whistler Village (upper and lower options). You will '''NOT''' be submitting expenses for these evenings, and '''any costs above the vouchers will not be reimbursed.''' A list of participating restaurants will be available by the end of March.

=====Groups, Restaurants & Reservations=====
*Group dinners - All large (eight or more people) reservations '''must''' go through Lisa Carlson (email lcarlson@mozilla.com) and dinners must stay within the voucher amount. Lisa has contacts at every restaurant on the list and will cooridnate reservations. She is happy to help with reservations for fewer than eight as well.

The fine print:
*Team events must be hosted using the vouchers, and stay within the voucher amount.
*No expenses over voucher amounts will be approved.
*Volunteer Contributors will their own vouchers.
*In no case should employees expense or use MoCo corporate cards to cover purchases of alcohol outside of team dinners or the vouchers.
*All restaurants in Whistler recommend advance reservations.

=='''Hotel'''==
Hotels are reserved during registration. Mozilla will pay for your hotel room with a check in date of Monday, June 17 and a check-out of Saturday, June 22. A link to self-book any pre/post stays at your hotel will be available, should that be part of your plan. Please do not book your hotel through Egencia.

====Payment on Check-in====
Everyone will be required to present a form of payment on check-in for incidentals. Upon check-in, the hotel will place a pre-authorization hold on your credit card for any incidentals you may incur during your stay (varies by hotel). Upon departure, the hold on your credit card will be removed.

We recommend providing a '''credit card'''. You can provide a debit card (but we really do not recommend it), but they do put a hold of funds on your card and has been problematic for some international travelers in the past. If you are not able to provide a credit or debit card, email mozilla@shworldwide.com and we'll work with the hotel on accommodating your needs.

====Early Check-in or Late Check Out====
Generally, check in begins at 4:00pm (varies by hotel). If you arrive before this time, you may preregister at the Front Desk. Should your room not be available, the Bellstand can assist you in storing your luggage while you begin to enjoy Whistler Village. '''Please note that hotels are unable to guarantee early check-in unless you pre-pay for the previous night.'''

Checkout time is at 11:00am.

====Early Departure====
Please contact mozilla@shworldwide.com if you change your reservation once you check in. There is typically an early departure fee, but we can sometimes negotiate the fee if we are made aware.

====Pre/post====
Links to self-book any pre/post stays - pre (June 14-16) & post nights (June 23-25) - will be emailed once hotels are assigned.

=='''Travel'''==
The Egencia portal open March 8 and booking instructions will be emailed to '''anyone approved to attend'''. New hires will have individual deadlines based upon hire/start date. Contractors, vendors, seasonal, status employees should wait to book travel until they get an email from Bmark@mozilla.com with specific instructions.

Specific instructions will be emailed to you about how to book, as we have a new process for anyone based outside the US, Canada & Central/South America. You will '''NOT''' be booking your All Hands travel in the new country based site.

To help you choose yours flights, please keep the below shuttle times in mind.
Shuttles TO Whistler from YVR will be provided for flights arriving:
*Sunday, June 16 between 10:00 and 16:30
*Monday, June 17 between 07:00 and 21:00

Shuttles TO YVR will be provided for flights with scheduled flight departure times (and you should plan to leave Whistler 5+ hours prior to your flight):
*Saturday, June 22 between 06:00 and 23:00

Should you need to reach someone for special circumstances or changes that can't be done online:
*Call: +1 (877) 264-1622 or +1 (417) 521-0273; Hours of operations are Monday – Friday (except holidays) 5:00 AM– 5:30 PM PST or 8:00 AM – 8:30 PM EST (2 pm - 11 pm UTC). If you call outside these hours, you will get an after hours agent, who may not be as helpful.
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday.

'''Important Details:'''
Everyone should plan to arrive in Vancouver (YVR) on Monday, June 17 and leave on Saturday, June 22. Anyone who plans to arrive ahead of that or to stay longer, regardless of the reason, must follow the "arriving early/departing late guidelines." These guidelines also apply if you want to fly in or out of airports other than your home airport and Vancouver (anything custom). A few notes:
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, your manager must confirm your participation before you will be able to book travel. You will receive a separate email shortly if you have already been approved.
*Volunteers will be handled separate from this process.
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.
*If you would like to invite someone who is a business partner, facilitator or some other category that isn't an employee or volunteer (not a personal guestfamily), email bmark@mozilla.com.
*Change fees will be covered by Mozilla for business reasons only.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, June 17 and leave on Saturday, June 22. Here are some exceptions:
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, June 14 and Monday, June 24, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You will stay in Vancouver any extra nights, as you'll still be responsible for taking the provided transportation. You must have approval from our benefits team in writing (and send to bmark@mozilla.com) prior to booking any travel. Approvals and expenses will not be applied retroactively.
* If you live in a country where work travel is prohibited on Sunday, you may travel on Saturday, June 15, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You will stay in Vancouver any extra nights, as you'll still be responsible for taking the provided transportation. You must have approval from our benefits team in writing (and send to bmark@mozilla.com) prior to booking any travel. Approvals and expenses will not be applied retroactively.
* If you plan to spend some extra personal time in Vancouver/Whistler or nearby (choosing to arrive before Monday, June 17 or depart after Saturday, June 22), you'll need to create an itinerary in Egencia for standard dates/locations within the Egencia Portal and compare to the custom dates/locations you'd like. Please share the difference via email to bmark@mozilla.com or through the approval comment box when you submit the flight. '''You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of YVR w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.''' This scenario also applies for routing through different airports to/from Vancouver than your home airport (ex. a layover in Chicago for a few days, or flying out of something other than YVR). In all cases, flights in and out of Vancouver should be booked via Egencia.
* If you are attending the Sunday/Monday CI event (by invite), you can arrive on Sunday, June 16.
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is '''no unilateral''' "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You will stay in Vancouver any extra nights, as you'll still be responsible for taking the provided transportation. If you choose to go to Whistler early or stay late, self-booked transportation costs will not be reimbursed. This policy does not apply to volunteer contributors, any jetlag recovery costs must be self funded.

====Booking Family Travel====
Whether your family will accompany you on your flight or join us later; and you have two options: direct with the airline (recommended) or through Egencia.

'''Direct (recommended):'''

First, figure out which flights you want to be on as an employee in Egencia. Hold them in Egencia. Find the flights you want for your family on the airline site and book them. Go back to Egencia and book your flights. Once you have both sets of confirmation numbers, call the airline and ask them to LINK your two reservations. This shows that you are traveling together and shouldn't be moved. When you call, you can also ask the airline agent to assign seats together. By booking your family direct on the airline, it gives them "priority" with the airline over people who book via a third party (expedia, booking.com, kayak, etc). These aren't guarantees, but they do help.

'''Via Egencia:'''

We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com

'''Notes:'''

* If your family is arriving on a different flights than you but would like to take advantage of the airport shuttles on Sunday/Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.
* No matter how you book, give yourself a lot of time on departure. We recommend leaving Whistler FIVE hours prior to your flight, longer with family.
* We are unable to accommodate volunteer contributor families/guests.

====Not Flying====
Parking options vary by hotel, and within the village. Mozilla will not reimburse for parking, unless you are BC based and did not book a flight. More options [https://www.whistler.com/getting-around/parking/ here].

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo & MoFo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members.

=====''Air Travel Fine Print''=====
*Change fees will be covered by Mozilla for '''business reasons only'''. If you need a change and have manager approval, email bmark@mozilla.com prior to requesting the change with Egencia. Once you have approval, call Egencia to make the change at +1 (702) 939-2530 or +1-877-264-1622 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.
*Mozilla will '''not''' reimburse for Business/First class upgrades or tickets.
*''Mozilla Frequent Flyer perks do not apply for All Hands''.
*Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

=='''Ground Transportation'''==
====Airport Shuttle====
All Mozillians and guests who have flights arriving into YVR per below will be transported to Whistler (scheduled arrival time of flight):
*Sunday, June 16 between 10:00 and 16:30
*Monday, June 17 between 07:00 and 21:00
''Note - this is different than recent All hands.''

All Mozillians and guests who have flights departing from YVR per below will be transported from Whistler (scheduled departure time of flight):
*Saturday, June 22 between 06:00 and 23:00

'''Transfer time between the airport and Whistler is 2-3 hours depending on time of day.'''

If you arrive into another airport; or on a different date - ground transportation is on your own (not reimbursable). If your family is arriving on different flights than you but would like to take advantage of the shuttles on Monday & Saturday, email their itinerary to mozilla@shworldwide.com.

=====Arrivals to Vancouver (YVR)=====
Look for a greeter holding up a Mozilla sign. Please identify yourself to the greeter and they will direct you to the shuttles.

=====Departures from Whistler Village to Vancouver (YVR)=====
Everyone departing on Saturday, June 22 between 06:00 and 23:00, will receive shuttle transportation to YVR. More details about departures will be sent via email. Plan to depart the hotel 5+ hours prior to your flight time - this allows for a 2 hour transfer time and 3 hours at the airport.

=====Bringing family?=====
If you are bringing family and are all arriving on Monday, June 17 and departing Saturday, June 22, you may all use our company-arranged transportation provided you request it ahead of time (for your guests). You will do this during registration.

=====Arriving early and/or leaving late (w/ or w/out family)?=====
If you arrive/depart other than the times listed below, you will have to arrange/pay for your own ground transportation, to and from YVR, including rental cars and parking.
*Sunday, June 16 between 10:00 and 16:30
*Monday, June 17 between 07:00 and 21:00
*Saturday, June 22 between 06:00 and 23:00

'''Recommended Airport Shuttle:'''
https://www.whistler.com/getting-here/road/shuttle/

=='''Safety & Security'''==
=====Alcohol at Events=====
To better support and sustain an environment (and workplace culture) where people feel safe and included, we have made a set of changes regarding alcohol at our events. In all cases, our approach aligns with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).
*All participants are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.
*We will '''limit bar-servings to beer and wine''' and ensure an equal number and quality (i.e. not just Coke) of non-alcoholic drink options are available and displayed.
*Team dinners should be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.
*Clearly outlined, communicated (to event teams, HR and managers) and understood '''escalation process''' for behavior that might be deemed counter to the spirit of our CPG.

=====Device Security=====
If you are traveling to the All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Physical Security=====
Badges are required to access all meeting spaces and evening events.

=='''Accessibility'''==
====Evenings====
Monday Night reception is at the Whistler Conference Center, on the main level. No stairs or elevators required.

Friday Night reception is at the Roundhouse, on the top of Whistler Mountain. Access is via 25 min ride on a gondola. If you have questions/concerns about this, please reach out to bmark@mozilla.com.

====Listen Systems====
We will have Listen Systems available for any meeting in the Sea to Sky Ballroom A. Visit the AV booth at the back of the room to pick one up.

====Bathrooms====
The Whistler Conference Center has 4 bathrooms on the main level - 2 gendered bathrooms (with multiple stalls each), 1 non-gendered (multiple stalls) and one non-gendered accessible bathroom.

=='''Families/Guests'''==
Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made. Please note that what are able to do for families varies by each location. We are unable to accommodate volunteer contributor or intern families/guests at our All Hands.

====Quick summary logistics====

=====Air Travel=====
Employees do need to book via Egencia regardless of how families are booked. See Air Travel above for specifics and recommendations.

=====Hotel=====
Family/friends are welcome to stay with you, however, any additional room expenses will be yours to cover. All room rates are based upon single occupancy and costs to add guests vary by hotel. Breakfast is not included in any of the guest room rates.

=====Breakfast=====
Family/guests who are registered for the event and registered with the hotel are invited to join us for breakfast each morning. Breakfast will be provided on Tuesday - Friday.

=====Lunch & Dinner=====
Family will be on their own for lunch daily and dinner on Tuesday, Wednesday & Thursday.

=====Monday & Friday Night Events=====
Family members who are registered for the event and registered with the hotel, are invited to join us for our evening events.

=====Family Friendly Activities=====

Visit [https://www.whistler.com/activities/summer/ here] for several options.

=====Childcare Services=====
We will not provide centralized childcare services in Whistler. Please visit [https://www.whistler.com/family/childcare/ here] for Childcare, Babysitting & Camp options.

=='''Activities'''==
* [https://www.whistler.com/activities/ Whistler Activities]
* [[All_Hands/Whistler2019/Running|Running]]
* [[All_Hands/Whistler2019/Tiny Computers|Tiny Computer Hacking]]

MozWeek/Whistler2019

2019-03-08T15:30:59Z

MikeKaply: Bold transfer time.

'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''

=='''Dates and Location'''==
Monday, June 17 - Friday, June 21, 2019 (travel days are Monday the 17th & Saturday the 22nd) in Whistler, British Columbia, Canada.

We are staying at nine hotels in Whistler Village. We will have meetings at the [https://meetings.whistler.com/wcc/facility/ Whistler Conference Centre] and two hotels.

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to pre-approved and pre-arranged.''

=='''Registration'''==
This is an invite-only event. All full time and Upwork employees are expected to attend this all company event. Contractors, Vendors and seasonal employees are included on a case by case evaluation based upon team needs.

Advance registration is required. Attendees will need to wear their event badge at all times, including to evening events. We will have security at our events who will be ensuring everyone in our space should be there.

=====New Hires=====
We have a process to identify new hires each Monday and will invite them to book travel. No action necessary from managers other than to let them know about the event. Please work closely with your recruiting manager as they are aware of all deadlines.

All new hires must have a start date of May 31 or earlier and able to register/book travel by May 13.

=='''Immigration'''==
It is important to look into your entry requirements early as some may need to schedule an in-person biometrics appointment. You can check here to see whether you require only a valid passport, [https://www.canada.ca/en/immigration-refugees-citizenship/services/visit-canada/eta.html an eTA], or a visa to enter Canada: http://www.cic.gc.ca/english/visit/visas.asp. You should also research whether you need a transit visa if you have a layover or change planes in a country that requires it.

If you do need a visa you can request a visa invitation letter during registration.

Those who have committed certain legal infractions are not allowed to enter Canada (known as “inadmissible” under [https://www.canada.ca/en/immigration-refugees-citizenship/services/immigrate-canada/inadmissibility/overcome-criminal-convictions.html Canada’s immigration law]). Check here to see if you might be "inadmissible" (you could be turned away at the border if you are inadmissible, so best to know ahead of time!): http://www.cic.gc.ca/english/information/inadmissibility/index.asp and http://www.ezbordercrossing.com/the-inspection-experience/prior-criminal-offenses/crossing-canadian-border-with-a-dui/#.VThVDRfnfVp

If you have concerns about being inadmissible while traveling to Canada for All Hands, please reach out to Casey McGill on the immigration team at cmcgill@mozilla.com as soon as possible.

=='''Week at a Glance'''==

====Monday====
*Monday is travel/arrival day
*Registration
*Welcome Reception from 6:00 pm - 9:00 pm

====Tuesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Whistler Dine-around

====Wednesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Whistler Dine-around

====Thursday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Whistler Dine-around

====Friday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Closing event at The Roundhouse

====Saturday====
*Breakfast (incl guests)
*Departure day only. No scheduled activities.

=='''Food, Drink & Events'''==
Breakfast, lunch & snacks will be provided and paid for centrally for attendees. Breakfast is provided Tuesday - Saturday and lunch is provided Tuesday - Friday. Menus will be posted here closer to the event.

Allergies/preferences: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options. If you have severe allergies that we need to know about; you can indicate in registration.

===Hosted Evening Events===
We have evening events on the Monday and Friday nights.

====Tuesday, Wednesday & Thursday Night Dinners====
You'll be on your "own" for these three evenings and we'll provide pre-paid vouchers for specific restaurants in Whistler Village (upper and lower options). You will '''NOT''' be submitting expenses for these evenings, and '''any costs above the vouchers will not be reimbursed.''' A list of participating restaurants will be available by the end of March.

=====Groups, Restaurants & Reservations=====
*Group dinners - All large (eight or more people) reservations '''must''' go through Lisa Carlson (email lcarlson@mozilla.com) and dinners must stay within the voucher amount. Lisa has contacts at every restaurant on the list and will cooridnate reservations. She is happy to help with reservations for fewer than eight as well.

The fine print:
*Team events must be hosted using the vouchers, and stay within the voucher amount.
*No expenses over voucher amounts will be approved.
*Volunteer Contributors will their own vouchers.
*In no case should employees expense or use MoCo corporate cards to cover purchases of alcohol outside of team dinners or the vouchers.
*All restaurants in Whistler recommend advance reservations.

=='''Hotel'''==
Hotels are reserved during registration. Mozilla will pay for your hotel room with a check in date of Monday, June 17 and a check-out of Saturday, June 22. A link to self-book any pre/post stays at your hotel will be available, should that be part of your plan. Please do not book your hotel through Egencia.

====Payment on Check-in====
Everyone will be required to present a form of payment on check-in for incidentals. Upon check-in, the hotel will place a pre-authorization hold on your credit card for any incidentals you may incur during your stay (varies by hotel). Upon departure, the hold on your credit card will be removed.

We recommend providing a '''credit card'''. You can provide a debit card (but we really do not recommend it), but they do put a hold of funds on your card and has been problematic for some international travelers in the past. If you are not able to provide a credit or debit card, email mozilla@shworldwide.com and we'll work with the hotel on accommodating your needs.

====Early Check-in or Late Check Out====
Generally, check in begins at 4:00pm (varies by hotel). If you arrive before this time, you may preregister at the Front Desk. Should your room not be available, the Bellstand can assist you in storing your luggage while you begin to enjoy Whistler Village. '''Please note that hotels are unable to guarantee early check-in unless you pre-pay for the previous night.'''

Checkout time is at 11:00am.

====Early Departure====
Please contact mozilla@shworldwide.com if you change your reservation once you check in. There is typically an early departure fee, but we can sometimes negotiate the fee if we are made aware.

====Pre/post====
Links to self-book any pre/post stays - pre (June 14-16) & post nights (June 23-25) - will be emailed once hotels are assigned.

=='''Travel'''==
The Egencia portal open March 8 and booking instructions will be emailed to '''anyone approved to attend'''. New hires will have individual deadlines based upon hire/start date. Contractors, vendors, seasonal, status employees should wait to book travel until they get an email from Bmark@mozilla.com with specific instructions.

Specific instructions will be emailed to you about how to book, as we have a new process for anyone based outside the US, Canada & Central/South America. You will '''NOT''' be booking your All Hands travel in the new country based site.

To help you choose yours flights, please keep the below shuttle times in mind.
Shuttles TO Whistler from YVR will be provided for flights arriving:
*Sunday, June 16 between 10:00 and 16:30
*Monday, June 17 between 07:00 and 21:00

Shuttles TO YVR will be provided for flights with scheduled flight departure times (and you should plan to leave Whistler 5+ hours prior to your flight):
*Saturday, June 22 between 06:00 and 23:00

Should you need to reach someone for special circumstances or changes that can't be done online:
*Call: +1 (877) 264-1622 or +1 (417) 521-0273; Hours of operations are Monday – Friday (except holidays) 5:00 AM– 5:30 PM PST or 8:00 AM – 8:30 PM EST (2 pm - 11 pm UTC). If you call outside these hours, you will get an after hours agent, who may not be as helpful.
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday.

'''Important Details:'''
Everyone should plan to arrive in Vancouver (YVR) on Monday, June 17 and leave on Saturday, June 22. Anyone who plans to arrive ahead of that or to stay longer, regardless of the reason, must follow the "arriving early/departing late guidelines." These guidelines also apply if you want to fly in or out of airports other than your home airport and Vancouver (anything custom). A few notes:
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, your manager must confirm your participation before you will be able to book travel. You will receive a separate email shortly if you have already been approved.
*Volunteers will be handled separate from this process.
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.
*If you would like to invite someone who is a business partner, facilitator or some other category that isn't an employee or volunteer (not a personal guestfamily), email bmark@mozilla.com.
*Change fees will be covered by Mozilla for business reasons only.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, June 17 and leave on Saturday, June 22. Here are some exceptions:
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, June 14 and Monday, June 24, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You will stay in Vancouver any extra nights, as you'll still be responsible for taking the provided transportation. You must have approval from our benefits team in writing (and send to bmark@mozilla.com) prior to booking any travel. Approvals and expenses will not be applied retroactively.
* If you live in a country where work travel is prohibited on Sunday, you may travel on Saturday, June 15, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You will stay in Vancouver any extra nights, as you'll still be responsible for taking the provided transportation. You must have approval from our benefits team in writing (and send to bmark@mozilla.com) prior to booking any travel. Approvals and expenses will not be applied retroactively.
* If you plan to spend some extra personal time in Vancouver/Whistler or nearby (choosing to arrive before Monday, June 17 or depart after Saturday, June 22), you'll need to create an itinerary in Egencia for standard dates/locations within the Egencia Portal and compare to the custom dates/locations you'd like. Please share the difference via email to bmark@mozilla.com or through the approval comment box when you submit the flight. '''You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of YVR w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.''' This scenario also applies for routing through different airports to/from Vancouver than your home airport (ex. a layover in Chicago for a few days, or flying out of something other than YVR). In all cases, flights in and out of Vancouver should be booked via Egencia.
* If you are attending the Sunday/Monday CI event (by invite), you can arrive on Sunday, June 16.
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is '''no unilateral''' "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). You will stay in Vancouver any extra nights, as you'll still be responsible for taking the provided transportation. If you choose to go to Whistler early or stay late, self-booked transportation costs will not be reimbursed. This policy does not apply to volunteer contributors, any jetlag recovery costs must be self funded.

====Booking Family Travel====
Whether your family will accompany you on your flight or join us later; and you have two options: direct with the airline (recommended) or through Egencia.

'''Direct (recommended):'''

First, figure out which flights you want to be on as an employee in Egencia. Hold them in Egencia. Find the flights you want for your family on the airline site and book them. Go back to Egencia and book your flights. Once you have both sets of confirmation numbers, call the airline and ask them to LINK your two reservations. This shows that you are traveling together and shouldn't be moved. When you call, you can also ask the airline agent to assign seats together. By booking your family direct on the airline, it gives them "priority" with the airline over people who book via a third party (expedia, booking.com, kayak, etc). These aren't guarantees, but they do help.

'''Via Egencia:'''

We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com

'''Notes:'''

* If your family is arriving on a different flights than you but would like to take advantage of the airport shuttles on Sunday/Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.
* No matter how you book, give yourself a lot of time on departure. We recommend leaving Whistler FIVE hours prior to your flight, longer with family.
* We are unable to accommodate volunteer contributor families/guests.

====Not Flying====
Parking options vary by hotel, and within the village. Mozilla will not reimburse for parking, unless you are BC based and did not book a flight. More options [https://www.whistler.com/getting-around/parking/ here].

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo & MoFo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members.

=====''Air Travel Fine Print''=====
*Change fees will be covered by Mozilla for '''business reasons only'''. If you need a change and have manager approval, email bmark@mozilla.com prior to requesting the change with Egencia. Once you have approval, call Egencia to make the change at +1 (702) 939-2530 or +1-877-264-1622 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.
*Mozilla will '''not''' reimburse for Business/First class upgrades or tickets.
*''Mozilla Frequent Flyer perks do not apply for All Hands''.
*Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

=='''Ground Transportation'''==
====Airport Shuttle====
All Mozillians and guests who have flights arriving into YVR per below will be transported to Whistler (scheduled arrival time of flight):
*Sunday, June 16 between 10:00 and 16:30
*Monday, June 17 between 07:00 and 21:00
''Note - this is different than recent All hands.''

All Mozillians and guests who have flights departing from YVR per below will be transported from Whistler (scheduled departure time of flight):
*Saturday, June 22 between 06:00 and 23:00

If you arrive into another airport; or on a different date - ground transportation is on your own (not reimbursable). If your family is arriving on different flights than you but would like to take advantage of the shuttles on Monday & Saturday, email their itinerary to mozilla@shworldwide.com.

=====Arrivals to Vancouver (YVR)=====
Look for a greeter holding up a Mozilla sign. Please identify yourself to the greeter and they will direct you to the shuttles. '''Transfer time from the airport to Whistler is 2-3 hours depending on time of day.'''

=====Departures from Whistler Village to Vancouver (YVR)=====
Everyone departing on Saturday, June 22 between 06:00 and 23:00, will receive shuttle transportation to YVR. More details about departures will be sent via email. Plan to depart the hotel 5+ hours prior to your flight time - this allows for a 2 hour transfer time and 3 hours at the airport.

=====Bringing family?=====
If you are bringing family and are all arriving on Monday, June 17 and departing Saturday, June 22, you may all use our company-arranged transportation provided you request it ahead of time (for your guests). You will do this during registration.

=====Arriving early and/or leaving late (w/ or w/out family)?=====
If you arrive/depart other than the times listed below, you will have to arrange/pay for your own ground transportation, to and from YVR, including rental cars and parking.
*Sunday, June 16 between 10:00 and 16:30
*Monday, June 17 between 07:00 and 21:00
*Saturday, June 22 between 06:00 and 23:00

'''Recommended Airport Shuttle:'''
https://www.whistler.com/getting-here/road/shuttle/

=='''Safety & Security'''==
=====Alcohol at Events=====
To better support and sustain an environment (and workplace culture) where people feel safe and included, we have made a set of changes regarding alcohol at our events. In all cases, our approach aligns with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).
*All participants are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.
*We will '''limit bar-servings to beer and wine''' and ensure an equal number and quality (i.e. not just Coke) of non-alcoholic drink options are available and displayed.
*Team dinners should be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.
*Clearly outlined, communicated (to event teams, HR and managers) and understood '''escalation process''' for behavior that might be deemed counter to the spirit of our CPG.

=====Device Security=====
If you are traveling to the All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Physical Security=====
Badges are required to access all meeting spaces and evening events.

=='''Accessibility'''==
====Evenings====
Monday Night reception is at the Whistler Conference Center, on the main level. No stairs or elevators required.

Friday Night reception is at the Roundhouse, on the top of Whistler Mountain. Access is via 25 min ride on a gondola. If you have questions/concerns about this, please reach out to bmark@mozilla.com.

====Listen Systems====
We will have Listen Systems available for any meeting in the Sea to Sky Ballroom A. Visit the AV booth at the back of the room to pick one up.

====Bathrooms====
The Whistler Conference Center has 4 bathrooms on the main level - 2 gendered bathrooms (with multiple stalls each), 1 non-gendered (multiple stalls) and one non-gendered accessible bathroom.

=='''Families/Guests'''==
Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made. Please note that what are able to do for families varies by each location. We are unable to accommodate volunteer contributor or intern families/guests at our All Hands.

====Quick summary logistics====

=====Air Travel=====
Employees do need to book via Egencia regardless of how families are booked. See Air Travel above for specifics and recommendations.

=====Hotel=====
Family/friends are welcome to stay with you, however, any additional room expenses will be yours to cover. All room rates are based upon single occupancy and costs to add guests vary by hotel. Breakfast is not included in any of the guest room rates.

=====Breakfast=====
Family/guests who are registered for the event and registered with the hotel are invited to join us for breakfast each morning. Breakfast will be provided on Tuesday - Friday.

=====Lunch & Dinner=====
Family will be on their own for lunch daily and dinner on Tuesday, Wednesday & Thursday.

=====Monday & Friday Night Events=====
Family members who are registered for the event and registered with the hotel, are invited to join us for our evening events.

=====Family Friendly Activities=====

Visit [https://www.whistler.com/activities/summer/ here] for several options.

=====Childcare Services=====
We will not provide centralized childcare services in Whistler. Please visit [https://www.whistler.com/family/childcare/ here] for Childcare, Babysitting & Camp options.

=='''Activities'''==
* [https://www.whistler.com/activities/ Whistler Activities]
* [[All_Hands/Whistler2019/Running|Running]]
* [[All_Hands/Whistler2019/Tiny Computers|Tiny Computer Hacking]]

MozWeek/Orlando2018

2018-08-30T14:30:55Z

MikeKaply: Add link to Disney Spreadsheet.

'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''

=='''Dates, Location and Weather'''==
Monday, December 3 - Friday, December 7, 2018 (travel days are Monday the 3rd & Saturday the 8th) in Orlando, FL.

We are staying at [http://swandolphin.com/ Swan & Dolphin].

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to pre-approved and pre-arranged.''

=='''Registration'''==
This is an invite-only event. All full time and Upwork employees are expected to attend this all company event. Contractors, Vendors and seasonal employees are included on a case by case evaluation based upon team needs.

Advance registration is required. Attendees will need to wear their event badge at all times, including to evening events. We will have security at our events who will be ensuring everyone in our space should be there.

=====New Hires=====
We have a process to identify new hires each Monday and will invite them to book travel. No action necessary from managers other than to let them know about the event. Please work closely with your recruiting manager as they are aware of all deadlines.

All new hires must have a start date of November 16 and able to register/book travel by November 1.

==== Volunteer contributor participation ====
All nominations will be done by employees, with a coordinator from each of the Firefox, Emerging Technologies, Marketing, Open Innovation and Operations parts of the organization. There will be no open call for nominations from volunteer Mozillians.

Please note: The information on this wiki primarily applies to Full time and contractor staff. If you have questions about how specifics apply to you, please email groter@mozilla.com and bmark@mozilla.com.

=='''Week at a Glance'''==

====Monday====
*Monday is primarily your travel day. You'll be able to pick up your registration stuff between 12:00 pm and 9:00 pm, as well as attend the *Welcome Reception from 6:00 pm - 9:00 pm.

====Tuesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Evening out to enjoy Orlando (or any part of Disney World should you [https://wiki.mozilla.org/All_Hands/Orlando2018#Disney_Park_Passes purchase passes]).

====Wednesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*All company evening event at [https://www.kennedyspacecenter.com/ Kennedy Space Center] (incl guests)

====Thursday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Evening out to enjoy Orlando (or any part of Disney World should you [https://wiki.mozilla.org/All_Hands/Orlando2018#Disney_Park_Passes purchase passes]).

====Friday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Closing event at [https://www.universalorlando.com/web/en/us/universal-orlando-resort/the-wizarding-world-of-harry-potter/hub/index.html The Wizarding World of Harry Potter] at Universal Studios from 7:00 pm - 12:00 am. We'll have transportation to/from the venue and hotel.

====Saturday====
*Centrally located breakfast (incl guests)
*Departure day only. No scheduled activities.

=='''Food, Drink & Events'''==
Breakfast, lunch & snacks will be provided and paid for centrally for attendees. Breakfast is provided Tuesday - Saturday and lunch is provided Tuesday - Friday. Menus will be posted here closer to the event.

Allergies/preferences: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options. If you have severe allergies that we need to know about; you can indicate in registration.

====Evening Events====
We have evening events on the Monday, Wednesday and Friday nights.

====Tuesday & Thursday Night Dinners====
You'll be on your own for Tuesday & Thursday and will have a similar expense policy from San Francisco ($60/night - $120 total to include food, beverage, transportation, exchange fees, etc). We will not be providing [https://wiki.mozilla.org/All_Hands/Orlando2018#Disney_Park_Passes park passes] or Disney gift cards.

Here is how this will work:

For both of these evenings, once your meetings have concluded, you and your team, friends, new acquaintances, are free to explore and to find somewhere great to eat that suits you. Each of you can expense a total of $120 over the two days (or $60/night).

This amount includes:
*Meal cost, including tax & gratuity
*Any beverages
*Transportation to/from the restaurant
*Conversion fees (for credit cards) or cash withdrawal fees

Anything over the $120 for the two evenings will be your own expense. The fine print:
*If your team is hosting an evening event 1 of the nights and the payment is coordinated (meaning, you don’t have to open your wallet and pay), you can expense up to $60 for the other night.
*You will be asked (later) to submit an Mozlando only expense report. You can submit ONE report for Orlando only and must be submitted no later than December 31, 2018.
*If your manager approves expenses above the $60 per night, that expense will go directly to your travel budget in your cost center.

Volunteer Contributors will have a separate process that will be communicated directly.

=====Restaurants & Reservations=====
*All restaurants in Orlando recommend advance reservations.
The hotel has several onsite [https://www.swandolphin.com/feedback/dining.html restaurants].

*[https://disneyworld.disney.go.com/dining/ DisneyWorld] has a searchable database of all of their restaurants - by park (ticketed or not) + cuisine, dining type, price range and rating.

*[https://www.timeout.com/orlando/restaurants/best-restaurants-in-orlando 26 of the best restaurants in Orlando] because Orlando is about more than theme parks and chain eateries—as proven by these overall best local restaurants.

=====Disney Park Passes=====
We will not be providing Disney Park Passes for evenings. Purchase discounted passes [https://www.mydisneygroup.com/mozilla here] and for more information, see [https://wiki.mozilla.org/All_Hands/Orlando2018#Discounted_Disney_Park_Passes here].

=='''Safety & Security'''==
=====Alcohol at Events=====
To better support and sustain an environment (and workplace culture) where people feel safe and included, we plan make a set of changes regarding alcohol at our events. In all cases, our approach will align with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).
*All participants were/are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.
*We will '''limit bar-servings to beer and wine''' and ensure an equal number and quality (i.e. not just Coke) of non-alcoholic drink options are available and displayed.
*When teams undertake smaller, “off campus” adventures (team dinners or events), leaders will be asked (and reminded) to be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.
*Clearly outlined, communicated (to event teams, HR and managers) and understood '''escalation process''' for behavior that might be deemed counter to the spirit of our CPG.

=====Device Security=====
If you are traveling to the Mozlando All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Physical Security=====
Badges are required to access all meeting spaces and evening events.

=='''Hotel'''==
Hotels are reserved during registration. Mozilla will pay for your hotel room with a check in date of Monday, December 3 and a check-out of Saturday, December 8. A link to self-book any pre/post stays at your hotel will be available, should that be part of your plan. Please do not book your hotel through Egencia.

====Payment on Check-in====
Everyone will be required to present a form of payment on check-in for incidentals at $50 per day. This is a US hotel standard and we aren't able to waive it (we tried).

We recommend providing a credit card. You can provide a debit card, but they do put a hold of funds on your card and has been problematic for some international travelers in the past. If you are not able to provide a credit or debit card, email mozilla@shworldwide.com and we'll work with the hotel on accommodating.

====Pre/post====
A link to self-book any pre/post stays at your hotel will be available to book pre (Nov 30, Dec 1-2) & post nights (Dec 8-10). If you'd like it in advance of the communication, email bmark@mozilla.com

=='''Travel'''==
The Mozlando 2018 Egencia portal will open in late August and booking instructions will be emailed. The deadline to book travel is September 14.

To access, log into Egencia using your LDAP, click Book → Meetings → Mozlando 2018. If you don’t see Mozlando 2018, email bmark@mozilla.com and I’ll add you. Please do not book outside the portal. Please fly into and out of Orlando International Airport (MCO).

Should you need to reach someone for special circumstances or changes that can't be done online:
*Call: +1 (877) 264-1622 or +1 (417) 521-0273; Monday - Friday 9 am - 6 pm Eastern (2 pm - 11 pm UTC). If you call outside these hours, you will get an after hours agent, who may not be as helpful.
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday 9 am - 6 pm Eastern (2 pm - 11 pm UTC).

'''Important Details:'''
Everyone should plan to arrive in Orlando on Monday, December 3rd and leave on Saturday, December 8th. Anyone who plans to arrive ahead of that or to stay longer, regardless of the reason, must follow the "arriving early/departing late guidelines." These guidelines also apply if you want to fly in or out of airports other than your home airport and Orlando (anything custom). A few notes:
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, your manager must confirm your participation before you will be able to book travel. You will receive a separate email shortly if you have already been approved.
*Volunteers will be handled separate from this process.
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.
*If you would like to invite someone who is a partner, facilitator or some other category that isn't an employee or volunteer, email bmark@mozilla.com.
*Change fees will be covered by Mozilla for business reasons only.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, December 3 and leave on Saturday, December 8. Here are some exceptions:
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, November 30 and Monday, December 18, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).
* If you live in a country where work travel is prohibited on Sunday (ex France), you may travel on Saturday, December 1 and Saturday, December 8, if you’d prefer (not required). You will get your Monday, December 3 and 10 off. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).
* If you plan to spend some extra personal time in Orlando or nearby (choosing to arrive before Monday, December 3 or depart after Saturday, December 8), you'll need to create an itinerary in Egencia for standard dates/locations within the Mozlando 2018 Portal and compare to the custom dates/locations you'd like. Please share the difference via email to bmark@mozilla.com or through the approval comment box when you submit the flight. '''You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of MCO w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.''' This scenario also applies for routing through different airports to/from Orlando than your home airport (ex. a layover in Chicago for a few days, or flying out of MIA instead of MCO). In all cases, flights in and out of Orlando should be booked via Egencia.
* If you are attending the Sunday/Monday CI event (by invite), you can arrive on Sunday, December 2.
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is '''no unilateral''' "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). This policy does not apply to volunteer contributors, any jetlag recovery costs must be self funded.

====Booking Family Travel====
Whether your family will accompany you on your flight or join us later; and you have two options: direct with the airline (recommended) or through Egencia.

'''Direct (recommended):'''

First, figure out which flights you want to be on as an employee in Egencia. Hold them in Egencia. Find the flights you want for your family on the airline site and book them. Go back to Egencia and book your flights. Once you have both sets of confirmation numbers, call the airline and ask them to LINK your two reservations. This shows that you are traveling together and shouldn't be moved. When you call, you can also ask the airline agent to assign seats together. By booking your family direct on the airline, it gives them "priority" with the airline over people who book via a third party (expedia, booking.com, kayak, etc). These aren't guarantees, but they do help.

'''Via Egencia:'''

We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com

'''Notes:'''

* If your family is arriving on a different flights than you but would like to take advantage of the shuttles on Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.
* No matter how you book, give yourself a lot of time at MCO on departure. This airport can chaotic (almost everyone leaving is a family with young kids) so not being in a hurry helps stress-levels.
* We are unable to accommodate volunteer contributor families/guests.

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo & MoFo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members.

=====''Air Travel Fine Print''=====
Change fees will be covered by Mozilla for business reasons only. If you need a change and have manager approval, email bmark@mozilla.com prior to requesting the change with Egencia. Once you have approval, call Egencia to make the change at +1 (702) 939-2530 or +1-877-264-1622 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.

Mozilla will '''not''' reimburse for Business/First class upgrades or tickets. ''Mozilla Frequent Flyer perks do not apply for All Hands''.

Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

=='''Ground Transportation'''==
====Airport Shuttle====
All Mozillians and guests who have flights arriving anytime on Monday, December 3rd in Orlando International Airport (MCO) and out on Saturday, December 8th, will be transferred to/from the hotel. If you arrive into another airport; or on a different date - ground transportation is on your own. If your family is arriving on different flights than you but would like to take advantage of the shuttles on Monday & Saturday, email their itinerary to mozilla@shworldwide.com.

=====Arrivals to Orlando Int’l Airport (MCO)=====
Everyone will be greeted in Baggage Claim (regardless if you check a bag). At the bottom of the escalator in the baggage claim level, look for a greeter holding up a Mozilla/Mozlando sign. Please identify yourself to the greeter and they will direct you to the shuttles. Transfer time from the airport to the hotel is approximately 20 minutes.

''For Domestic Arrivals''

Upon arrival, proceed to the baggage claim area of your respective airline. There are two separate baggage claims – A or B. Please listen for the announcements from your airline flight attendants or while you are on the shuttle from the gates to the main terminal, for your baggage claim. Once you exit past Security, look to the left and right to see the large A or B to find your respective baggage claim.

''For International Arrivals''

Upon arrival, you will proceed thru Customs. Some International flights allow you to take your luggage directly from Customs to the main terminal and some require you to put it on the luggage carousel and re-collect it in the main baggage claim. Regardless if you collect your luggage at Customs or not, you have to take the shuttle to the main terminal. Once there, please proceed down the escalator to the Baggage Claim, Level 2.
(Do not go directly to Level 1.)

=====Departures from Dolphin Hotel to Orlando Int’l Airport (MCO)=====
Everyone departing on Saturday, December 8th, will receive shuttle transportation to MCO. You will be met by transportation staff in the hotel lobbies and assisted onto the shuttles. More details about departures will be sent via email.

Regardless of international or domeestic, plan to depart the hotel 3 hours prior to your flight time.

=====Bringing family?=====
If you are bringing family and are all arriving on Monday, December 3rd and departing Saturday, December 8th, you may all use our company-arranged transportation provided you request it ahead of time (for your guests). You will do this during registration.

=====Arriving early and/or leaving late (w/ or w/out family)?=====
If you arrive other than December 3rd or depart other than December 8th, with or without guests, you will have to cover and arrange your own ground transportation, to and from MCO, including rental cars and parking.

'''Recommended Airport Shuttle:'''
Mears Transportation http://www.mearstransportation.com/global/orlando/
Loading is on Level One at the airport, clearly marked, and the shuttle makes 1-3 stops at hotels in the same proximity.

Additional help is here:
*Transportation Information (airport and parks) http://swananddolphin.com/aboutus/transportation.html
*Transportation FAQ: http://swananddolphin.com/feedback/transportation.html
*Transportation booking (via Swan & Dolphin): https://swandolphinconcierge.com/

Exceptions are those attending the CI meeting on Monday. Transportation will be arranged for you.

=='''Accessibility'''==
====Evenings====
The Monday Night reception is at the Swan & Dolphin hotel, accessible by elevators and escalators. Both offsite evening events are accessible, specific details to be shared soon.

====Listen Systems====
We will have Listen Systems available for the Plenary on Tuesday. Visit the AV booth at the back of the room to pick one up.

=='''Immigration'''==
'''Any''' questions on immigration should be sent to immigration@mozilla.com.

If you are from a country that requires a B-1/B-2 business visitor visa to enter the US, please plan for it early as government processing times constantly change.

Please visit the following website to learn more about the visa application process and timing for your country: http://travel.state.gov/content/visas/english/visit/visitor.html#overview. Current estimated processing times at the US Embassies and Consulates abroad can be found at: https://travel.state.gov/content/visas/en/general/wait-times.html/

Some travelers may be eligible to travel to the United States without first applying for a B-1/B-2 visa, if they are eligible for the Visa Waiver Program (VWP or "ESTA"). You are eligible to apply for admission under the Visa Waiver Program (VWP) if you:

*Intend to enter the United States for 90 days or less for business, pleasure or transit
*Have a valid passport lawfully issued to you by a Visa Waiver Program country: http://www.esta.us/visa_waiver_countries.html
*Have authorization to travel via the Electronic System for Travel Authorization: https://esta.cbp.dhs.gov/
*Arrive via a Visa Waiver Program signatory carrier (all commercial airlines meet this requirement)
*Have a return or onward ticket
*Travel may not terminate in contiguous territory or adjacent islands unless the traveler is a resident of one of those areas

=====Employee Travel FAQ=====
This [https://mana.mozilla.org/wiki/display/PR/Travel+FAQ FAQ] addresses questions about how to handle security concerns and electronic devices at the border and how to engage with US Customs & Border Protection (CBP). While it specifically focuses on concerns related to travel to the United States, much of this guidance is applicable to travel elsewhere. Mana access required.

=====Pocket Letter=====
A pocket letter is recommended to keep on hand for those who are entering the United States. It should accompany you whether or not you are required to have a visa to enter. You may request a copy of that letter when you register. Please contact immigration@mozilla.com if you require a specific letter for your visa application or if you have any questions regarding your citizenship, visa capabilities or travel related questions.

=====ESTA Point of Contact=====
In the ESTA application you need to give a "U.S. Point of Contact Information".

Please list Casey McGill as your US Point of Contact.
Address: 331 East Evelyn Avenue, Mountain View, CA 94041 Phone: 408.505.3028

=='''Mozlando 2018 All Hands Expense Policy'''==
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. Mozlando All Hands Expense Report). Each expense must be tagged with "Orlando 2018"

2. It must contain only those expenses relative to the All Hands Event in Orlando.

3. If your submitted expense report for All Hands is submitted outside these guidelines, it will be rejected and you will be asked to re-submit with only All Hands Expenses

4. The deadline to submit the Orlando All Hands Expense Report is '''January 31, 2018'''.

5. Expenses related to team events, parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved.

'''The intention of our all hands are to centrally organize a structure that includes:'''
*Meals (two/day + snacks)
*Transportation
*Accommodations
*Some number of social events

Expenses submitted can not exceed the approved amounts. Any social events that are not part of our central plan will generally be self-organized and funded by participants.

=====Cell phone reimbursement policy=====
Cell phone reimbursement must be approved by your manager prior to submitting the expense. Teams will decide for their staff what is appropriate to expense.

=====Internet reimbursement policy=====
Internet will be provided in all guestrooms and meeting space in all hotels. If you opt to upgrade/add service, those costs are not reimbursable, unless previously approved by your manager and are for business reasons.

If you have questions about any of this, please reach out to bmark@mozilla.com

=='''Families/Guests in Orlando'''==
Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made.

Please note that what are able to do for families varies by each location.

Please note: we are unable to accommodate volunteer contributor families/guests.

====Quick summary logistics====

=====Air Travel=====

Employees do need to book via Egencia regardless of how families are booked. See Air Travel above for specifics and recommendations.

=====Hotel=====

They are welcome to stay with you, however, any additional room expenses will be yours to cover. All room rates are based upon single occupancy and costs to add guests vary by hotel. Breakfast is not included in any of the guest room rates.

=====Breakfast=====

Family members who are registered for the event and registered with the hotel are invited to join us for breakfast each morning. Breakfast will be provided on Tuesday, December 3rd - Saturday, December 8th.

=====Lunch & Dinner=====

Family will be on their own for lunch daily and dinner on Tuesday & Thursday.

=====Monday, Wednesday & Friday Night Events=====

Family members who are registered for the event and registered with the hotel, are invited to join us for our three evening events.

=====Family Friendly Activities=====

The [https://www.swandolphin.com/activities/index.html hotel] offers several options and [https://www.swandolphin.com/kids/index.html child specific] options.

=====Evening Childcare Services=====

[https://www.swandolphin.com/kids/campdolphin.html Camp Dolphin] is available nightly from 5:00 pm - 12:00 am. Reservations are required for Camp Dolphin's evening program. The cost is $12 per hour, per child. A kids meal from Picabu can be included for an additional $10. Here is the [https://www.swandolphin.com/feedback/child.html FAQ].

===Discounted Disney Park Passes===
https://www.mydisneygroup.com/mozilla

This site will EXPIRE for Advance Purchase Sales on December 2, 2018.

These "Meeting and Convention" tickets offer advance purchase savings of 10% on our Full-Multi-Day (2 days or longer) Tickets and include one (1) complimentary +1 FUN visit to an additional Disney Experience at any one (1) of the following (additional details are listed on the website):
*Disney’s Typhoon Lagoon Water Park
*Disney’s Blizzard Beach Water Park
*Disney’s Winter Summerland or Disney’s Fantasia Gardens Miniature Golf Courses (before 4 p.m.)
*Greens Fees for one round of golf at Disney’s Oak Trail Golf Course, our 9-hole walking course

The site also contains our partial-day tickets, which are discounted off of our full 1-Day tickets. "Meeting and Convention" Tickets purchased here will be valid from November 27 - December 14, 2018.

Please note, the ticket prices on the ticket store reflect any applicable discounts and include tax. These tickets are not available for purchase to the general public and are not sold at our theme park ticket windows. Since these Meeting & Convention partial-day and multi-day tickets are not available for purchase at our Theme Park Ticket Windows, you are only able to purchase them here: https://www.mydisneygroup.com/mozilla

Discounts do not apply for Mickey's Very Merry Christmas Party at Magic Kingdom (each Sun, Tue, Thur, Fri in December).

=====Disney FastPasses=====
All of the Meeting & Convention tickets include the ability to pre-select up to three FastPasses per theme park visit day. Details on how to create a My Disney Experience Account and pre-select FastPasses can be found here: https://www.mydisneygroup.com/mozilla under PLAN YOUR VISIT tab.

=='''Extracurricular Activities'''==
Costs for these activities are self-funded and can not be expensed. Feel free to add activities and invite others.

*[https://wiki.mozilla.org/All_Hands/Orlando2018#Discounted_Disney_Park_Passes Disney Park Passes]
*[https://docs.google.com/spreadsheets/d/1Wi_BZxCtsRAXH0bEzpA880m8OhpnGk73-y1P0aqQyrg/edit#gid=225771109 Spreadsheet with lots of Disney info]

MozWeek/Orlando2018

2018-08-24T19:22:37Z

MikeKaply: Fixed airport typo

'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''

=='''Dates, Location and Weather'''==
Monday, December 3 - Friday, December 7, 2018 (travel days are Monday the 3rd & Saturday the 8th) in Orlando, FL.

We are staying at [http://swandolphin.com/ Swan & Dolphin].

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to pre-approved and pre-arranged.''

=='''Registration'''==
This is an invite-only event. All full time and Upwork employees are expected to attend this all company event. Contractors, Vendors and seasonal employees are included on a case by case evaluation based upon team needs.

Advance registration is required. Attendees will need to wear their event badge at all times, including to evening events. We will have security at our events who will be ensuring everyone in our space should be there.

=====New Hires=====
We have a process to identify new hires each Monday and will invite them to book travel. No action necessary from managers other than to let them know about the event. Please work closely with your recruiting manager as they are aware of all deadlines.

All new hires must have a start date of November 16 and able to register/book travel by November 1.

==== Volunteer contributor participation ====
All nominations will be done by employees, with a coordinator from each of the Firefox, Emerging Technologies, Marketing, Open Innovation and Operations parts of the organization. There will be no open call for nominations from volunteer Mozillians.

Please note: The information on this wiki primarily applies to Full time and contractor staff. If you have questions about how specifics apply to you, please email groter@mozilla.com and bmark@mozilla.com.

=='''Week at a Glance'''==

====Monday====
*Monday is primarily your travel day. You'll be able to pick up your registration stuff between 12:00 pm and 9:00 pm, as well as attend the *Welcome Reception from 6:00 pm - 9:00 pm.

====Tuesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Evening out to enjoy Orlando (or any part of Disney World should you [https://wiki.mozilla.org/All_Hands/Orlando2018#Disney_Park_Passes purchase passes]).

====Wednesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*All company evening event

====Thursday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Evening out to enjoy Orlando (or any part of Disney World should you [https://wiki.mozilla.org/All_Hands/Orlando2018#Disney_Park_Passes purchase passes]).

====Friday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Closing event from 7:00 pm - 12:00 am. We'll have transportation to/from the venue and hotel.

====Saturday====
*Centrally located breakfast (incl guests)
*Departure day only. No scheduled activities.

=='''Food, Drink & Events'''==
Breakfast, lunch & snacks will be provided and paid for centrally for attendees. Breakfast is provided Tuesday - Saturday and lunch is provided Tuesday - Friday. Menus will be posted here closer to the event.

Allergies/preferences: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options. If you have severe allergies that we need to know about; you can indicate in registration.

====Evening Events====
We have evening events on the Monday, Wednesday and Friday nights.

====Tuesday & Thursday Night Dinners====
You'll be on your own for Tuesday & Thursday and will have a similar expense policy from San Francisco ($60/night - $120 total to include food, beverage, transportation, exchange fees, etc). We will not be providing [https://wiki.mozilla.org/All_Hands/Orlando2018#Disney_Park_Passes park passes] or Disney gift cards.

Here is how this will work:

For both of these evenings, once your meetings have concluded, you and your team, friends, new acquaintances, are free to explore and to find somewhere great to eat that suits you. Each of you can expense a total of $120 over the two days (or $60/night).

This amount includes:
*Meal cost, including tax & gratuity
*Any beverages
*Transportation to/from the restaurant
*Conversion fees (for credit cards) or cash withdrawal fees

Anything over the $120 for the two evenings will be your own expense. The fine print:
*If your team is hosting an evening event 1 of the nights and the payment is coordinated (meaning, you don’t have to open your wallet and pay), you can expense up to $60 for the other night.
*You will be asked (later) to submit an Mozlando only expense report. You can submit ONE report for Orlando only and must be submitted no later than December 31, 2018.
*If your manager approves expenses above the $60 per night, that expense will go directly to your travel budget in your cost center.

Volunteer Contributors will have a separate process that will be communicated directly.

=====Restaurants & Reservations=====
*All restaurants in Orlando recommend advance reservations.
The hotel has several onsite [https://www.swandolphin.com/feedback/dining.html restaurants].

*[https://disneyworld.disney.go.com/dining/ DisneyWorld] has a searchable database of all of their restaurants - by park (ticketed or not) + cuisine, dining type, price range and rating.

*[https://www.timeout.com/orlando/restaurants/best-restaurants-in-orlando 26 of the best restaurants in Orlando] because Orlando is about more than theme parks and chain eateries—as proven by these overall best local restaurants.

=====Disney Park Passes=====
We will not be providing Disney Park Passes for evenings. Purchase discounted passes [https://www.mydisneygroup.com/mozilla here] and for more information, see [https://wiki.mozilla.org/All_Hands/Orlando2018#Discounted_Disney_Park_Passes here].

=='''Safety & Security'''==
=====Alcohol at Events=====
To better support and sustain an environment (and workplace culture) where people feel safe and included, we plan make a set of changes regarding alcohol at our events. In all cases, our approach will align with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).
*All participants were/are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.
*We will '''limit bar-servings to beer and wine''' and ensure an equal number and quality (i.e. not just Coke) of non-alcoholic drink options are available and displayed.
*When teams undertake smaller, “off campus” adventures (team dinners or events), leaders will be asked (and reminded) to be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.
*Clearly outlined, communicated (to event teams, HR and managers) and understood '''escalation process''' for behavior that might be deemed counter to the spirit of our CPG.

=====Device Security=====
If you are traveling to the Mozlando All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Physical Security=====
Badges are required to access all meeting spaces and evening events.

=='''Hotel'''==
Hotels are reserved during registration. Mozilla will pay for your hotel room with a check in date of Monday, December 3 and a check-out of Saturday, December 8. A link to self-book any pre/post stays at your hotel will be available, should that be part of your plan. Please do not book your hotel through Egencia.

====Payment on Check-in====
Everyone will be required to present a form of payment on check-in for incidentals at $50 per day. This is a US hotel standard and we aren't able to waive it (we tried).

We recommend providing a credit card. You can provide a debit card, but they do put a hold of funds on your card and has been problematic for some international travelers in the past. If you are not able to provide a credit or debit card, email mozilla@shworldwide.com and we'll work with the hotel on accommodating.

====Pre/post====
A link to self-book any pre/post stays at your hotel will be available to book pre (Nov 30, Dec 1-2) & post nights (Dec 8-10). If you'd like it in advance of the communication, email bmark@mozilla.com

=='''Travel'''==
The Mozlando 2018 Egencia portal will open in late August and booking instructions will be emailed. The deadline to book travel is September 14.

To access, log into Egencia using your LDAP, click Book → Meetings → Mozlando 2018. If you don’t see Mozlando 2018, email bmark@mozilla.com and I’ll add you. Please do not book outside the portal. Please fly into and out of Orlando International Airport (MCO).

Should you need to reach someone for special circumstances or changes that can't be done online:
*Call: +1 (877) 264-1622 or +1 (417) 521-0273; Monday - Friday 9 am - 6 pm Eastern (2 pm - 11 pm UTC). If you call outside these hours, you will get an after hours agent, who may not be as helpful.
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday 9 am - 6 pm Eastern (2 pm - 11 pm UTC).

'''Important Details:'''
Everyone should plan to arrive in Orlando on Monday, December 3rd and leave on Saturday, December 8th. Anyone who plans to arrive ahead of that or to stay longer, regardless of the reason, must follow the "arriving early/departing late guidelines." These guidelines also apply if you want to fly in or out of airports other than your home airport and Orlando (anything custom). A few notes:
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, your manager must confirm your participation before you will be able to book travel. You will receive a separate email shortly if you have already been approved.
*Volunteers will be handled separate from this process.
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.
*If you would like to invite someone who is a partner, facilitator or some other category that isn't an employee or volunteer, email bmark@mozilla.com.
*Change fees will be covered by Mozilla for business reasons only.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, December 3 and leave on Saturday, December 8. Here are some exceptions:
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, November 30 and Monday, December 18, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).
* If you live in a country where work travel is prohibited on Sunday (ex France), you may travel on Saturday, December 1 and Saturday, December 8, if you’d prefer (not required). You will get your Monday, December 3 and 10 off. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).
* If you plan to spend some extra personal time in Orlando or nearby (choosing to arrive before Monday, December 3 or depart after Saturday, December 8), you'll need to create an itinerary in Egencia for standard dates/locations within the Mozlando 2018 Portal and compare to the custom dates/locations you'd like. Please share the difference via email to bmark@mozilla.com or through the approval comment box when you submit the flight. '''You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of MCO w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.''' This scenario also applies for routing through different airports to/from Orlando than your home airport (ex. a layover in Chicago for a few days, or flying out of MIA instead of MCO). In all cases, flights in and out of Orlando should be booked via Egencia.
* If you are attending the Sunday/Monday CI event (by invite), you can arrive on Sunday, December 2.
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is '''no unilateral''' "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). This policy does not apply to volunteer contributors, any jetlag recovery costs must be self funded.

====Booking Family Travel====
Whether your family will accompany you on your flight or join us later; and you have two options: direct with the airline (recommended) or through Egencia.

'''Direct (recommended):'''

First, figure out which flights you want to be on as an employee in Egencia. Hold them in Egencia. Find the flights you want for your family on the airline site and book them. Go back to Egencia and book your flights. Once you have both sets of confirmation numbers, call the airline and ask them to LINK your two reservations. This shows that you are traveling together and shouldn't be moved. When you call, you can also ask the airline agent to assign seats together. By booking your family direct on the airline, it gives them "priority" with the airline over people who book via a third party (expedia, booking.com, kayak, etc). These aren't guarantees, but they do help.

'''Via Egencia:'''

We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com

'''Notes:'''

* If your family is arriving on a different flights than you but would like to take advantage of the shuttles on Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.
* No matter how you book, give yourself a lot of time at MCO on departure. This airport can chaotic (almost everyone leaving is a family with young kids) so not being in a hurry helps stress-levels.
* We are unable to accommodate volunteer contributor families/guests.

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo & MoFo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members.

=====''Air Travel Fine Print''=====
Change fees will be covered by Mozilla for business reasons only. If you need a change and have manager approval, email bmark@mozilla.com prior to requesting the change with Egencia. Once you have approval, call Egencia to make the change at +1 (702) 939-2530 or +1-877-264-1622 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.

Mozilla will '''not''' reimburse for Business/First class upgrades or tickets. ''Mozilla Frequent Flyer perks do not apply for All Hands''.

Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

=='''Ground Transportation'''==
====Airport Shuttle====
All Mozillians and guests who have flights arriving anytime on Monday, December 3rd in Orlando International Airport (MCO) and out on Saturday, December 8th, will be transferred to/from the hotel. If you arrive into another airport; or on a different date - ground transportation is on your own. If your family is arriving on different flights than you but would like to take advantage of the shuttles on Monday & Saturday, email their itinerary to mozilla@shworldwide.com.

=====Arrivals to Orlando Int’l Airport (MCO)=====
Everyone will be greeted in Baggage Claim (regardless if you check a bag). At the bottom of the escalator in the baggage claim level, look for a greeter holding up a Mozilla/Mozlando sign. Please identify yourself to the greeter and they will direct you to the shuttles. Transfer time from the airport to the hotel is approximately 20 minutes.

''For Domestic Arrivals''

Upon arrival, proceed to the baggage claim area of your respective airline. There are two separate baggage claims – A or B. Please listen for the announcements from your airline flight attendants or while you are on the shuttle from the gates to the main terminal, for your baggage claim. Once you exit past Security, look to the left and right to see the large A or B to find your respective baggage claim.

''For International Arrivals''

Upon arrival, you will proceed thru Customs. Some International flights allow you to take your luggage directly from Customs to the main terminal and some require you to put it on the luggage carousel and re-collect it in the main baggage claim. Regardless if you collect your luggage at Customs or not, you have to take the shuttle to the main terminal. Once there, please proceed down the escalator to the Baggage Claim, Level 2.
(Do not go directly to Level 1.)

=====Departures from Dolphin Hotel to Orlando Int’l Airport (MCO)=====
Everyone departing on Saturday, December 8th, will receive shuttle transportation to MCO. You will be met by transportation staff in the hotel lobbies and assisted onto the shuttles. More details about departures will be sent via email.

Regardless of international or domeestic, plan to depart the hotel 3 hours prior to your flight time.

=====Bringing family?=====
If you are bringing family and are all arriving on Monday, December 3rd and departing Saturday, December 8th, you may all use our company-arranged transportation provided you request it ahead of time (for your guests). You will do this during registration.

=====Arriving early and/or leaving late (w/ or w/out family)?=====
If you arrive other than December 3rd or depart other than December 8th, with or without guests, you will have to cover and arrange your own ground transportation, to and from MCO, including rental cars and parking.

'''Recommended Airport Shuttle:'''
Mears Transportation http://www.mearstransportation.com/global/orlando/
Loading is on Level One at the airport, clearly marked, and the shuttle makes 1-3 stops at hotels in the same proximity.

Additional help is here:
*Transportation Information (airport and parks) http://swananddolphin.com/aboutus/transportation.html
*Transportation FAQ: http://swananddolphin.com/feedback/transportation.html
*Transportation booking (via Swan & Dolphin): https://swandolphinconcierge.com/

Exceptions are those attending the CI meeting on Monday. Transportation will be arranged for you.

=='''Accessibility'''==
====Evenings====
The Monday Night reception is at the Swan & Dolphin hotel, accessible by elevators and escalators. Both offsite evening events are accessible, specific details to be shared soon.

====Listen Systems====
We will have Listen Systems available for the Plenary on Tuesday. Visit the AV booth at the back of the room to pick one up.

=='''Immigration'''==
'''Any''' questions on immigration should be sent to immigration@mozilla.com.

If you are from a country that requires a B-1/B-2 business visitor visa to enter the US, please plan for it early as government processing times constantly change.

Please visit the following website to learn more about the visa application process and timing for your country: http://travel.state.gov/content/visas/english/visit/visitor.html#overview. Current estimated processing times at the US Embassies and Consulates abroad can be found at: https://travel.state.gov/content/visas/en/general/wait-times.html/

Some travelers may be eligible to travel to the United States without first applying for a B-1/B-2 visa, if they are eligible for the Visa Waiver Program (VWP or "ESTA"). You are eligible to apply for admission under the Visa Waiver Program (VWP) if you:

*Intend to enter the United States for 90 days or less for business, pleasure or transit
*Have a valid passport lawfully issued to you by a Visa Waiver Program country: http://www.esta.us/visa_waiver_countries.html
*Have authorization to travel via the Electronic System for Travel Authorization: https://esta.cbp.dhs.gov/
*Arrive via a Visa Waiver Program signatory carrier (all commercial airlines meet this requirement)
*Have a return or onward ticket
*Travel may not terminate in contiguous territory or adjacent islands unless the traveler is a resident of one of those areas

=====Employee Travel FAQ=====
This [https://mana.mozilla.org/wiki/display/PR/Travel+FAQ FAQ] addresses questions about how to handle security concerns and electronic devices at the border and how to engage with US Customs & Border Protection (CBP). While it specifically focuses on concerns related to travel to the United States, much of this guidance is applicable to travel elsewhere. Mana access required.

=====Pocket Letter=====
A pocket letter is recommended to keep on hand for those who are entering the United States. It should accompany you whether or not you are required to have a visa to enter. You may request a copy of that letter when you register. Please contact immigration@mozilla.com if you require a specific letter for your visa application or if you have any questions regarding your citizenship, visa capabilities or travel related questions.

=====ESTA Point of Contact=====
In the ESTA application you need to give a "U.S. Point of Contact Information".

Please list Casey McGill as your US Point of Contact.
Address: 331 East Evelyn Avenue, Mountain View, CA 94041 Phone: 408.505.3028

=='''Mozlando 2018 All Hands Expense Policy'''==
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. Mozlando All Hands Expense Report). Each expense must be tagged with "Orlando 2018"

2. It must contain only those expenses relative to the All Hands Event in Orlando.

3. If your submitted expense report for All Hands is submitted outside these guidelines, it will be rejected and you will be asked to re-submit with only All Hands Expenses

4. The deadline to submit the Orlando All Hands Expense Report is '''January 31, 2018'''.

5. Expenses related to team events, parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved.

'''The intention of our all hands are to centrally organize a structure that includes:'''
*Meals (two/day + snacks)
*Transportation
*Accommodations
*Some number of social events

Expenses submitted can not exceed the approved amounts. Any social events that are not part of our central plan will generally be self-organized and funded by participants.

=====Cell phone reimbursement policy=====
Cell phone reimbursement must be approved by your manager prior to submitting the expense. Teams will decide for their staff what is appropriate to expense.

=====Internet reimbursement policy=====
Internet will be provided in all guestrooms and meeting space in all hotels. If you opt to upgrade/add service, those costs are not reimbursable, unless previously approved by your manager and are for business reasons.

If you have questions about any of this, please reach out to bmark@mozilla.com

=='''Families/Guests in Orlando'''==
Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made.

Please note that what are able to do for families varies by each location.

Please note: we are unable to accommodate volunteer contributor families/guests.

====Quick summary logistics====

=====Air Travel=====

Employees do need to book via Egencia regardless of how families are booked. See Air Travel above for specifics and recommendations.

=====Hotel=====

They are welcome to stay with you, however, any additional room expenses will be yours to cover. All room rates are based upon single occupancy and costs to add guests vary by hotel. Breakfast is not included in any of the guest room rates.

=====Breakfast=====

Family members who are registered for the event and registered with the hotel are invited to join us for breakfast each morning. Breakfast will be provided on Tuesday, December 3rd - Saturday, December 8th.

=====Lunch & Dinner=====

Family will be on their own for lunch daily and dinner on Tuesday & Thursday.

=====Monday, Wednesday & Friday Night Events=====

Family members who are registered for the event and registered with the hotel, are invited to join us for our three evening events.

=====Family Friendly Activities=====

The [https://www.swandolphin.com/activities/index.html hotel] offers several options and [https://www.swandolphin.com/kids/index.html child specific] options.

=====Evening Childcare Services=====

[https://www.swandolphin.com/kids/campdolphin.html Camp Dolphin] is available nightly from 5:00 pm - 12:00 am. Reservations are required for Camp Dolphin's evening program. The cost is $12 per hour, per child. A kids meal from Picabu can be included for an additional $10. Here is the [https://www.swandolphin.com/feedback/child.html FAQ].

===Discounted Disney Park Passes===
https://www.mydisneygroup.com/mozilla

This site will EXPIRE for Advance Purchase Sales on December 2, 2018.

These "Meeting and Convention" tickets offer advance purchase savings of 10% on our Full-Multi-Day (2 days or longer) Tickets and include one (1) complimentary +1 FUN visit to an additional Disney Experience at any one (1) of the following (additional details are listed on the website):
*Disney’s Typhoon Lagoon Water Park
*Disney’s Blizzard Beach Water Park
*Disney’s Winter Summerland or Disney’s Fantasia Gardens Miniature Golf Courses (before 4 p.m.)
*Greens Fees for one round of golf at Disney’s Oak Trail Golf Course, our 9-hole walking course

The site also contains our partial-day tickets, which are discounted off of our full 1-Day tickets. "Meeting and Convention" Tickets purchased here will be valid from November 27 - December 14, 2018.

Please note, the ticket prices on the ticket store reflect any applicable discounts and include tax. These tickets are not available for purchase to the general public and are not sold at our theme park ticket windows. Since these Meeting & Convention partial-day and multi-day tickets are not available for purchase at our Theme Park Ticket Windows, you are only able to purchase them here: https://www.mydisneygroup.com/mozilla

Discounts do not apply for Mickey's Very Merry Christmas Party at Magic Kingdom (each Sun, Tue, Thur, Fri in December).

=====Disney FastPasses=====
All of the Meeting & Convention tickets include the ability to pre-select up to three FastPasses per theme park visit day. Details on how to create a My Disney Experience Account and pre-select FastPasses can be found here: https://www.mydisneygroup.com/mozilla under PLAN YOUR VISIT tab.

=='''Extracurricular Activities'''==
Costs for these activities are self-funded and can not be expensed. Feel free to add activities and invite others.

*[https://wiki.mozilla.org/All_Hands/Orlando2018#Discounted_Disney_Park_Passes Disney Park Passes]

Enterprise

2018-08-21T16:15:14Z

MikeKaply: Add redirect (incorrect, but better than the content)

#REDIRECT [[mdn::Firefox/Enterprise_deployment]]

The Mozilla Enterprise User Working Group is where enterprise developers, IT staff, Firefox and Thunderbird developers can discuss the challenges, ideas and best practices for deploying Firefox and Thunderbird in the enterprise. The group will meet monthly via phone and continue conversations on the discussion list as well as at an annual forum. This wiki can be used for sharing common config info, tips, references that are useful for enterprise environments.

== Motivation ==
Web browsers are the unsung heroes of an enterprise environment. Usually unnoticed in favor of the content and applications they host, they have silently established unquestioned status as a core, mission-critical application on every desktop. Notably, a knowledge worker spends so much time in a web browser, that productivity-driven efforts to personalize the end-user experience have steadily pushed the Browser to a Development Platform status. In fact, when speaking about its ever-popular Firefox, Mozilla explains the architecture of the Browser as "built on top of the Mozilla Platform".

As a Development Platform, the Browser is well positioned to be an influential player in the desktop productivity arena, bridging the gap between the "out there" internet, and the "in here" desktop. Still, with all the hype and expectations, institutions and enterprises continue to struggle with the basics of management and security and frequent updates.

The Mozilla Enterprise User Working group is a place for enterprise developers and Firefox and Thunderbird developers to discuss the challenges, ideas and best practices for deploying Firefox and Thunderbird in the enterprise. It will also be a channel for getting information about Mozilla plans as well as a place to ask questions and get the latest news as well as the thinking behind the decisions we make.

Welcome to the Mozilla Enterprise User Working Group!

== Objectives ==
* To establish a unified governance body around enterprise users of Firefox and Thunderbird.
* To drive enterprise requirements for the benefit of all enterprise-scale firms and institutions
* To help each other succeed in deploying Firefox and Thunderbird within our environments
* To recruit like-minded firms
* To share risk and cost
* To use industry influence to "raise the bar" on Web Browsers and push for WebDev best practices and open standards
* To offer prescriptive guidelines around Firefox and Thunderbird to peers
* '''Please Add Or Revise as you see appropriate!'''

== Rules of Engagement ==
Each of the calls will be organized around a central theme, with the primary goal being to simply communicate information and document that information, in the hopes that people inside and outside the group can learn from our experiences.

Calls will be private to the group. No one is required to share their affiliation on the phone call or in any documents produced by the Mozilla Enterprise User Working Group unless they choose to do so. Minutes will be published publicly without identifying which participant said which to enable enterprises to participate as fully as possible.

== How to Participate and Post ==
* [http://www.mozilla.org/en-US/firefox/organizations/ Join the mailing list.]
* Participate in the monthly phone calls. First Thursday of every month at 9am PT.

= Enterprise Firefox in the Blogosphere =

[https://wiki.mozilla.org/Enterprise/Meetings Meetings]

= Participants =
Please use anonymous information here if necessary

= Bugzilla Issues Tracked by EWG =
The [[Enterprise:Bugs|EWG Bugzilla]] page will highlight and track Bugs, Issues, Feature Requests, etc that are of interest to the Enterprise community. We encourage our peers to elevate these issues by voting on Bugzilla.

= Resources =
* [[Enterprise:Wishlist|Enterprise Wishlist]]
* Extended Support Releases: [http://www.mozilla.org/firefox/organizations/ Firefox-ESR], [http://www.mozilla.org/thunderbird/organizations/ Thunderbird-ESR]
* [[Deployment:Deploying_Firefox|Deploying Firefox]]
* [[Firefox:2.0_Institutional_Deployment|Institutional Deployment]]
* [[Firefox/Feature Brainstorming:Mobile and Enterprise Support|Mobile and Enterprise Support]]
* [http://www.pcc-services.com/kixtart/firefox-script.html Firefox Network Deployment Utility]
* [http://www.libx.org/ LibX - A Firefox Extension for Libraries]
* [[Thunderbird/Enterprise|Thunderbird in the Enterprise]]

Enterprise

2018-08-21T16:09:36Z

MikeKaply: Update URLs

This information is outdated.

The latest information is available here:

[https://support.mozilla.org/products/firefox-enterprise https://support.mozilla.org/products/firefox-enterprise].
and here:
[https://www.mozilla.org/en-US/firefox/enterprise/ https://www.mozilla.org/en-US/firefox/enterprise/]

The Mozilla Enterprise User Working Group is where enterprise developers, IT staff, Firefox and Thunderbird developers can discuss the challenges, ideas and best practices for deploying Firefox and Thunderbird in the enterprise. The group will meet monthly via phone and continue conversations on the discussion list as well as at an annual forum. This wiki can be used for sharing common config info, tips, references that are useful for enterprise environments.

== Motivation ==
Web browsers are the unsung heroes of an enterprise environment. Usually unnoticed in favor of the content and applications they host, they have silently established unquestioned status as a core, mission-critical application on every desktop. Notably, a knowledge worker spends so much time in a web browser, that productivity-driven efforts to personalize the end-user experience have steadily pushed the Browser to a Development Platform status. In fact, when speaking about its ever-popular Firefox, Mozilla explains the architecture of the Browser as "built on top of the Mozilla Platform".

As a Development Platform, the Browser is well positioned to be an influential player in the desktop productivity arena, bridging the gap between the "out there" internet, and the "in here" desktop. Still, with all the hype and expectations, institutions and enterprises continue to struggle with the basics of management and security and frequent updates.

The Mozilla Enterprise User Working group is a place for enterprise developers and Firefox and Thunderbird developers to discuss the challenges, ideas and best practices for deploying Firefox and Thunderbird in the enterprise. It will also be a channel for getting information about Mozilla plans as well as a place to ask questions and get the latest news as well as the thinking behind the decisions we make.

Welcome to the Mozilla Enterprise User Working Group!

== Objectives ==
* To establish a unified governance body around enterprise users of Firefox and Thunderbird.
* To drive enterprise requirements for the benefit of all enterprise-scale firms and institutions
* To help each other succeed in deploying Firefox and Thunderbird within our environments
* To recruit like-minded firms
* To share risk and cost
* To use industry influence to "raise the bar" on Web Browsers and push for WebDev best practices and open standards
* To offer prescriptive guidelines around Firefox and Thunderbird to peers
* '''Please Add Or Revise as you see appropriate!'''

== Rules of Engagement ==
Each of the calls will be organized around a central theme, with the primary goal being to simply communicate information and document that information, in the hopes that people inside and outside the group can learn from our experiences.

Calls will be private to the group. No one is required to share their affiliation on the phone call or in any documents produced by the Mozilla Enterprise User Working Group unless they choose to do so. Minutes will be published publicly without identifying which participant said which to enable enterprises to participate as fully as possible.

== How to Participate and Post ==
* [http://www.mozilla.org/en-US/firefox/organizations/ Join the mailing list.]
* Participate in the monthly phone calls. First Thursday of every month at 9am PT.

= Enterprise Firefox in the Blogosphere =

[https://wiki.mozilla.org/Enterprise/Meetings Meetings]

= Participants =
Please use anonymous information here if necessary

= Bugzilla Issues Tracked by EWG =
The [[Enterprise:Bugs|EWG Bugzilla]] page will highlight and track Bugs, Issues, Feature Requests, etc that are of interest to the Enterprise community. We encourage our peers to elevate these issues by voting on Bugzilla.

= Resources =
* [[Enterprise:Wishlist|Enterprise Wishlist]]
* Extended Support Releases: [http://www.mozilla.org/firefox/organizations/ Firefox-ESR], [http://www.mozilla.org/thunderbird/organizations/ Thunderbird-ESR]
* [[Deployment:Deploying_Firefox|Deploying Firefox]]
* [[Firefox:2.0_Institutional_Deployment|Institutional Deployment]]
* [[Firefox/Feature Brainstorming:Mobile and Enterprise Support|Mobile and Enterprise Support]]
* [http://www.pcc-services.com/kixtart/firefox-script.html Firefox Network Deployment Utility]
* [http://www.libx.org/ LibX - A Firefox Extension for Libraries]
* [[Thunderbird/Enterprise|Thunderbird in the Enterprise]]

Enterprise

2018-06-05T20:43:34Z

MikeKaply: Undo revision 1195166 by MikeKaply (talk)

#REDIRECT [[https://support.mozilla.org/products/firefox-enterprise]]

The Mozilla Enterprise User Working Group is where enterprise developers, IT staff, Firefox and Thunderbird developers can discuss the challenges, ideas and best practices for deploying Firefox and Thunderbird in the enterprise. The group will meet monthly via phone and continue conversations on the discussion list as well as at an annual forum. This wiki can be used for sharing common config info, tips, references that are useful for enterprise environments.

== Motivation ==
Web browsers are the unsung heroes of an enterprise environment. Usually unnoticed in favor of the content and applications they host, they have silently established unquestioned status as a core, mission-critical application on every desktop. Notably, a knowledge worker spends so much time in a web browser, that productivity-driven efforts to personalize the end-user experience have steadily pushed the Browser to a Development Platform status. In fact, when speaking about its ever-popular Firefox, Mozilla explains the architecture of the Browser as "built on top of the Mozilla Platform".

As a Development Platform, the Browser is well positioned to be an influential player in the desktop productivity arena, bridging the gap between the "out there" internet, and the "in here" desktop. Still, with all the hype and expectations, institutions and enterprises continue to struggle with the basics of management and security and frequent updates.

The Mozilla Enterprise User Working group is a place for enterprise developers and Firefox and Thunderbird developers to discuss the challenges, ideas and best practices for deploying Firefox and Thunderbird in the enterprise. It will also be a channel for getting information about Mozilla plans as well as a place to ask questions and get the latest news as well as the thinking behind the decisions we make.

Welcome to the Mozilla Enterprise User Working Group!

== Objectives ==
* To establish a unified governance body around enterprise users of Firefox and Thunderbird.
* To drive enterprise requirements for the benefit of all enterprise-scale firms and institutions
* To help each other succeed in deploying Firefox and Thunderbird within our environments
* To recruit like-minded firms
* To share risk and cost
* To use industry influence to "raise the bar" on Web Browsers and push for WebDev best practices and open standards
* To offer prescriptive guidelines around Firefox and Thunderbird to peers
* '''Please Add Or Revise as you see appropriate!'''

== Rules of Engagement ==
Each of the calls will be organized around a central theme, with the primary goal being to simply communicate information and document that information, in the hopes that people inside and outside the group can learn from our experiences.

Calls will be private to the group. No one is required to share their affiliation on the phone call or in any documents produced by the Mozilla Enterprise User Working Group unless they choose to do so. Minutes will be published publicly without identifying which participant said which to enable enterprises to participate as fully as possible.

== How to Participate and Post ==
* [http://www.mozilla.org/en-US/firefox/organizations/ Join the mailing list.]
* Participate in the monthly phone calls. First Thursday of every month at 9am PT.

= Enterprise Firefox in the Blogosphere =

[https://wiki.mozilla.org/Enterprise/Meetings Meetings]

= Participants =
Please use anonymous information here if necessary

= Bugzilla Issues Tracked by EWG =
The [[Enterprise:Bugs|EWG Bugzilla]] page will highlight and track Bugs, Issues, Feature Requests, etc that are of interest to the Enterprise community. We encourage our peers to elevate these issues by voting on Bugzilla.

= Resources =
* [[Enterprise:Wishlist|Enterprise Wishlist]]
* Extended Support Releases: [http://www.mozilla.org/firefox/organizations/ Firefox-ESR], [http://www.mozilla.org/thunderbird/organizations/ Thunderbird-ESR]
* [[Deployment:Deploying_Firefox|Deploying Firefox]]
* [[Firefox:2.0_Institutional_Deployment|Institutional Deployment]]
* [[Firefox/Feature Brainstorming:Mobile and Enterprise Support|Mobile and Enterprise Support]]
* [http://www.pcc-services.com/kixtart/firefox-script.html Firefox Network Deployment Utility]
* [http://www.libx.org/ LibX - A Firefox Extension for Libraries]
* [[Thunderbird/Enterprise|Thunderbird in the Enterprise]]

Enterprise

2018-06-05T20:41:47Z

MikeKaply: Correct redirect typo

#REDIRECT [https://support.mozilla.org/products/firefox-enterprise]

The Mozilla Enterprise User Working Group is where enterprise developers, IT staff, Firefox and Thunderbird developers can discuss the challenges, ideas and best practices for deploying Firefox and Thunderbird in the enterprise. The group will meet monthly via phone and continue conversations on the discussion list as well as at an annual forum. This wiki can be used for sharing common config info, tips, references that are useful for enterprise environments.

== Motivation ==
Web browsers are the unsung heroes of an enterprise environment. Usually unnoticed in favor of the content and applications they host, they have silently established unquestioned status as a core, mission-critical application on every desktop. Notably, a knowledge worker spends so much time in a web browser, that productivity-driven efforts to personalize the end-user experience have steadily pushed the Browser to a Development Platform status. In fact, when speaking about its ever-popular Firefox, Mozilla explains the architecture of the Browser as "built on top of the Mozilla Platform".

As a Development Platform, the Browser is well positioned to be an influential player in the desktop productivity arena, bridging the gap between the "out there" internet, and the "in here" desktop. Still, with all the hype and expectations, institutions and enterprises continue to struggle with the basics of management and security and frequent updates.

The Mozilla Enterprise User Working group is a place for enterprise developers and Firefox and Thunderbird developers to discuss the challenges, ideas and best practices for deploying Firefox and Thunderbird in the enterprise. It will also be a channel for getting information about Mozilla plans as well as a place to ask questions and get the latest news as well as the thinking behind the decisions we make.

Welcome to the Mozilla Enterprise User Working Group!

== Objectives ==
* To establish a unified governance body around enterprise users of Firefox and Thunderbird.
* To drive enterprise requirements for the benefit of all enterprise-scale firms and institutions
* To help each other succeed in deploying Firefox and Thunderbird within our environments
* To recruit like-minded firms
* To share risk and cost
* To use industry influence to "raise the bar" on Web Browsers and push for WebDev best practices and open standards
* To offer prescriptive guidelines around Firefox and Thunderbird to peers
* '''Please Add Or Revise as you see appropriate!'''

== Rules of Engagement ==
Each of the calls will be organized around a central theme, with the primary goal being to simply communicate information and document that information, in the hopes that people inside and outside the group can learn from our experiences.

Calls will be private to the group. No one is required to share their affiliation on the phone call or in any documents produced by the Mozilla Enterprise User Working Group unless they choose to do so. Minutes will be published publicly without identifying which participant said which to enable enterprises to participate as fully as possible.

== How to Participate and Post ==
* [http://www.mozilla.org/en-US/firefox/organizations/ Join the mailing list.]
* Participate in the monthly phone calls. First Thursday of every month at 9am PT.

= Enterprise Firefox in the Blogosphere =

[https://wiki.mozilla.org/Enterprise/Meetings Meetings]

= Participants =
Please use anonymous information here if necessary

= Bugzilla Issues Tracked by EWG =
The [[Enterprise:Bugs|EWG Bugzilla]] page will highlight and track Bugs, Issues, Feature Requests, etc that are of interest to the Enterprise community. We encourage our peers to elevate these issues by voting on Bugzilla.

= Resources =
* [[Enterprise:Wishlist|Enterprise Wishlist]]
* Extended Support Releases: [http://www.mozilla.org/firefox/organizations/ Firefox-ESR], [http://www.mozilla.org/thunderbird/organizations/ Thunderbird-ESR]
* [[Deployment:Deploying_Firefox|Deploying Firefox]]
* [[Firefox:2.0_Institutional_Deployment|Institutional Deployment]]
* [[Firefox/Feature Brainstorming:Mobile and Enterprise Support|Mobile and Enterprise Support]]
* [http://www.pcc-services.com/kixtart/firefox-script.html Firefox Network Deployment Utility]
* [http://www.libx.org/ LibX - A Firefox Extension for Libraries]
* [[Thunderbird/Enterprise|Thunderbird in the Enterprise]]

MozWeek/SanFrancisco2018

2018-05-15T19:24:27Z

MikeKaply: Add Museum of Ice Cream

'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''

=='''Dates, Location and Weather'''==
Monday, June 11 - Friday, June 15, 2018 (travel days are Monday the 11th & Saturday the 16th) in San Francisco, CA.

We are staying at [http://www.marriott.com/hotels/travel/sfodt-san-francisco-marriott-marquis/ San Francisco Marriott Marquis].

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to be pre-approved and pre-arranged.''

Weather:
* National Weather Service: [http://forecast.weather.gov/MapClick.php?smap=1&lat=37.785&lon=-122.410&unit=1&mp=1 forecast in ⁰C], [http://forecast.weather.gov/MapClick.php?smap=1&lat=37.785&lon=-122.410&mp=1 forecast in ⁰F]
* Temperatures ''in downtown San Francisco'' in late June are likely to have nighttime lows around 10-13 ⁰C / 50-56 ⁰F and daytime highs around 16-24 ⁰C / 61-75 ⁰F. But the weather is very occasionally warmer with highs around 27⁰C / 81⁰F.
* Weather in San Francisco in the summer is variable; it can become substantially cooler and foggier in the late afternoon; be prepared for temperatures to fall to 13⁰C / 56⁰F and the winds to pick up in the afternoon. Be prepared by carrying a warmer layer with you.
* Weather in other parts of the Bay Area can be much warmer than in San Francisco, even if you're only traveling 15km away. Look at the weather forecasts for where you're going. It's entirely possible for it to be 19⁰C / 66⁰F in San Francisco and simultaneously be 32⁰C / 90⁰F in Orinda. But if you're right on the ocean, the air temperature is likely to match the water temperature, which is probably around 12⁰C / 54⁰F.

=='''Registration'''==
This is an invitation-only event.

Advance registration is required. Attendees, guests and local guests will need to wear their event badge at all times, including to evening events.

=====New Hires=====
We have a process to identify new hires each Monday and will invite them to book travel. No action necessary from managers other than to let them know about the event. Please work closely with your recruiting manager as they are aware of all deadlines.

Monday, May 7 is the deadline for hiring. Friday, May 11 is the deadline that all new hires who must travel to the all hands but be registered and have travel booked. Friday, May 18 is the deadline for Bay Area/local new hires who do not need hotel or to travel need to be registered. All new hires must start on or before May 29.

====Contributors participation====
The process for this is [[All Hands/SanFrancisco2018/Contributor_nominations|outlined on this page]].

All nominations will be done by employees, with a coordinator from each of the Firefox/Product, Emerging Technologies, Marketing, Open Innovation and People parts of the organization. There will be no open call for nominations from contributors or volunteer Mozillians.

Please note: The information on this wiki primarily applies to fulltime and contractor staff. If you have questions about how specifics apply to you, please email groter@mozilla.com and bmark@mozilla.com.

====Mozilla Foundation====
The Foundation has decided to host our own All Hands from June 12-15 in Toronto. Information about their All Hands will be available on the Mana soon.

=='''Week at a Glance'''==

[https://docs.google.com/spreadsheets/d/1CEA1bnC5A4RrGirqojSEtGjv-LgR2RQz6Sm4j8XA8qo/edit?usp=sharing Here] is what the week looks like (subject to change)

=====Monday=====
Monday is primarily your travel day. You'll be able to pick up your registration stuff between 12:00 pm and 9:00 pm, as well as attend the Welcome Reception at the City View at Metreon from 6:00 pm - 9:00 pm.

=====Tuesday=====
We'll start Tuesday with a Plenary session, followed by various team meetings and Product/Tech Lightning Talk Sessions. The evening is open for dinner on your own or team dinners.

=====Wednesday=====
Wednesday is split between team time and Product/Tech Conference Sessions. The evening is open for dinner on your own or team dinners.

=====Thursday=====
Thursday is team time. The evening is open for dinner on your own or team dinners.

=====Friday=====
Friday is team time. Our closing party with be at the Exploratorium from 7:00 pm- 11:00 pm. We'll provide transportation to/from the hotel & venue + if the weather is nice, you could walk (about 1.5 miles / 2.4 km, 30 minutes).

=====Saturday=====
Departure day only. No scheduled activities, except optional breakfast.

==San Francisco All Hands Event Calendar==
Now live! https://sanfranciscoallhandsjune2018.sched.com/

The event has a password to access sessions. The password was provided in an email.

Don't see stuff for your org yet? Don't fret! The schedule changes regularly as meetings and events are confirmed. Keep checking back.

=====Create an account=====
We don’t recommend using the same email & password as anything like bank accounts, etc. We care about your security!

If you already have a Sched account from past All Hands, it still works, just log in with that.

=====Add items to your calendar=====
Select the circle on any agenda item to add it to your calendar (you do need to have an account & be logged in to do this)

You can also share a link to meetings to invite others. Go into the meeting and copy the short link. You can email that out to anyone and they can quickly add it to their calendar.

=====Subscribe to GCal Calendar Link=====
Click on the mobile phone on the right hand side of the screen. All the calendar options are available here.
You have the option to choose ALL meetings or YOUR meetings. Unless you have 400 items on your calendar, just select your calendar. It will add anything on your calendar to your GCal (also an option for Outlook and iCal). It syncs once per day.

The "only syncs once per day" only applies to Google Calendar. With almost all other clients (like Apple Calendar, Outlook, or the calendar app on your phone) you can set the refresh interval, and Sched's instructions recommend 1 hour.

Warning: This is a link that utilizes your username for the .ics file.

=====From Mobile=====
Visit from any mobile device - bookmark or add to your homescreen for quick access. There is a bonus icon you get by doing this. It caches the last time you opened the page offline and refreshes anytime you are connected.

=====Cool things=====
'''Filters'''

We have filtering functionality. You can filter by:
Departments (ex: Product Org)
AND
Functional Teams (ex: Firefox Addons)

*Search by Room, Speaker/Leader

'''Further Filtering'''
*Audience - who should be there (ex: Team only or Invite)
*Homerooms (you can quickly see what is happening in homerooms, by team) - why do you care? If you have a cross team meeting in their room, its a quick way to search
*Views - Lots of view options. It defaults to the simple view, but there are quite a few options.

=='''Food & Drink'''==
Breakfast, lunch & snacks will be provided and paid for centrally for attendees. Breakfast is provided Tuesday - Saturday and lunch is provided Tuesday - Friday.

Allergies/preferences: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options. If you have severe allergies that we need to know about; you can indicate in registration.

===Monday Night===
We will provide dinner at the Welcome Reception from 6:00 pm - 9:00 pm at City View by Meteron at the Welcome Reception. Since most of Monday is a travel day, you'll be on your own for meals except dinner.

===Tuesday, Wednesday & Thursday Nights===
Tuesday, Wednesday and Thursday evenings will be of your own to structure as you wish. Given how much you all seemed to like a more flexible dining experience, these three evenings will be of your own to structure as you wish.

Here is how this will work:

For each of these three evenings, once your meetings have concluded, you and your team, friends, new acquaintances, are free to explore San Francisco and to find somewhere great to eat that suits you. Each of you can expense a total of $180 over the three days (or $60/night).

This amount includes:
* Meal cost, including tax & gratuity
* Any beverages
* Transportation to/from the restaurant
* Conversion fees (for credit cards) or cash withdrawal fees

Anything over the $180 for the three evenings will be your own expense. The fine print:
* If your team is hosting an evening event 1 of the 3 nights and the payment is coordinated (meaning, you don’t have to open your wallet and pay), you can expense up to $120 for the other 2 nights ($60 for each of the 2 nights you did have to open your wallet and pay).
* You will be asked (later) to submit a San Francisco only expense report. You can submit ONE report for San Francisco only and must be submitted no later than August 31, 2018.
* If your manager approves expenses above the $60 per night, that expense will go directly to your travel budget in your cost center.

Volunteer Contributors & Interns will have a separate process that will be communicated directly.

===Friday Night===
We will provide dinner at the Closing Party from 7:00 pm - 11:00 pm at The Exploratorium.

'''What you need'''

Your SF All Hands name badge and Identification (you may be carded for alcohol).

=='''Photos'''==
==== Red Lanyards ====
If you see someone with a red lanyard, please don't take photos of them. They have opted out of being in photography. We'll have these available at the registration desk.

=='''Safety & Security'''==

=====Personal Security=====
While in the Mozilla meeting spaces, a name badge is required.

When you leave the hotel, you should remove your badge. Pickpocketers have been known to target people wear conference badges in the neighborhood we are in.

=====Meeting Security=====
You'll need to have your badge on at all times in the hotel, as will your partners, vendors and family members anytime they are in the spaces.

=====Device Security=====
If you are traveling to the San Francisco All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Safety Tips=====
SF Travel team also has some [https://sftravel.ent.box.com/s/p2ve63e1ctn74e0ai2x48mmgr9fdlvul tips about safety] in the city, including safety numbers and local hospitals.

=='''Hotel'''==
Hotel rooms are reserved for all employees & volunteers to stay all week, including employees based in San Francisco (just as if we were somewhere you don't live). We are hopeful Mozilla-locals will stay with the rest of us in the hotel - it's really part of what makes these events great. You will have the option to opt out of hotel in registration if you are local to the Bay Area and wish to commute.

A few things to note:
*Everyone will be required to present a form of payment on check-in for incidentals at $50 per day. This is a US-resort standard and we aren't able to waive it (we tried). Please reach out to mozilla@shworldwide.com if this creates a hardship for you.
*If you have any changes or questions about your reservation, email mozilla@shworldwide.com. The hotel cannot make changes to All Hands reservations (other than to add your guests) so we’d like very much if you didn’t try (it complicates things).
*If you have guests joining you for all or part of the week, you will be responsible for adding them to your reservation (and covering any additional fees). To do this, you will need your confirmation number(s) and to know how old your kids are. Details on how to add them will come a few weeks after registration closes.
*Volunteers, summer interns and outreachy interns will be sharing rooms.

====Payment on Check-in====
Everyone will be required to present a form of payment on check-in for incidentals at $50 per day. This is a US hotel standard and we aren't able to waive it (we tried).

We recommend providing a credit card. You can provide a debit card, but they do put a hold of funds on your card and has been problematic for some international travelers in the past. If you are not able to provide a credit or debit card, email mozilla@shworldwide.com and we'll work with the hotel on accommodating.

====Pre/post====
Links will be provided when you are invited to register in mid-April to book hotel 3 days pre and 3 days post at our negotiated rate. The pre/post reservations will require the use of an LDAP email* so we can link them to your All Hands reservation. Rooms booked by any method except this link will not be linked to your main reservation.

Rates start $179+tax/fees & for double occupancy.

====Parking====
Self-Parking is available at several lots nearby. The Marriott Marquis offers valet only - please do not park valet. Mozilla will not reimburse for parking, plan to commute the way you normally would in the city. If you have questions about parking, email bmark@mozilla.com.

=='''Travel'''==
Booking travel is now open. Please book itineraries by Friday, April 13, 2018.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, June 11 and leave on Saturday, June 16. Here are some exceptions:
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, June 8 and Monday, June 18, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).
* If you plan to spend some extra personal time in San Francisco (choosing to arrive before Monday, June 11 or depart after Saturday, June 16), you'll need to create an itinerary in Egencia for standard dates/locations within the San Francisco June 2018 Portal and compare to the custom dates you'd like. Please share the difference via email to bmark@mozilla.com before submitting the flight. You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of SFO w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.
* If you are attending the Monday Core Influencer's event (by invite).
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is no unilateral "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).

====Booking Family Travel====
Once travel has opened to staff, you may book family, whether they will accompany you on your flight or join us later; and you have two options: Direct or through Egencia.

If you choose to book family through Egencia, please first book your own flight and then call Egencia with your airline confirmation number (staff do have to go through Egencia). Otherwise, you can book family direct (either through the airline or through another third party) and call the ticketing airline(s) with both confirmation numbers and ask them to link your reservations, so they know you are traveling together. They should also be able to assign seats together. You will avoid the limited hours Egencia offers and avoid paying their ticketing fee.

If you prefer to book your family through Egencia, you can pay (including the Egencia booking fees) and coordinate with your own travel (recommend to book and then call/email Egencia with your itinerary number to match for family). Note that booking through Egencia does not put you on the same reservation, nor guarantee the reservations will be linked (you would still need to call the airline to link them).

''Volunteers, summer interns and outreachy interns will be sharing rooms and are unable to invite family to join them.''

* '''Call:''' +1 (877) 264-1622 or +1 (417) 521-0273; Monday - Friday 9 am - 6 pm EST. If you call outside these hours, you will get an after hours agent, who may not be as helpful.

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+insurance%3A+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members.

=====''Air Travel Fine Print''=====
Change fees will be covered by Mozilla for '''business reasons only'''. If you need a change and have manager approval, email bmark@mozilla.com prior to requesting the change with Egencia. Once you have approval, call Egencia to make the change at +1 (702) 939-2530 or +1-877-264-1622 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.

Mozilla will not reimburse for Business/First class upgrades or tickets.

Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

=='''Airport Shuttle'''==
All Mozillians and guests who have flights arriving anytime on Monday, June 11th in San Francisco International Airport (SFO) and out on Saturday, June 16th, will be transferred to the hotel. If you arrive into another airport (OAK or SJC) or on a different date, ground transportation is on your own.

=====Arrivals to San Francisco International Airport (SFO)=====
The airport has four terminals: Terminal 1, 2 & 3, and the International Terminal. For domestic flights In Terminals 1, 2 & 3 and the International Terminal (there are domestic flights), everyone will be greeted at the bottom of the escalator in the baggage claim for your terminal (even if you have no checked bags). Please identify yourself to the greeter and they will direct you to the shuttles for your terminal.

For International Flights into the International terminal, you will collect your luggage and pass through customs. Once through customs, you will walk directly out to the main lobby, where you’ll find a greeter and they will direct your to your shuttle.

Transfer time from the airport to the hotel is approximately 40-60 minutes.

=====Departures from San Francisco International Airport (SFO)=====

Everyone departing on Saturday, June 16th, will receive transportation to SFO. You will be met by transportation staff in the Marriott hotel lobby and assisted onto the shuttles.

If you have questions about arrivals or departures, please email mozilla@shworldwide.com.

====Alternate Transportation Options====
For those arriving or departing on dates other than June 11 and 16.
*[http://www.bart.gov/stations/powl BART] goes from SFO to the Powell Street Station for $8.95. Tickets can be purchased at the airport or in advance.
*[http://www.samtrans.com/schedulesandmaps/timetables/292.html SamTrans bus Route 292] goes from SFO to Mission St. & 5th St. only for [http://www.samtrans.com/fares/farechart.html $2.25 (inbound) or $4 (outbound)].
*[https://www.supershuttle.com/locations/sanfranciscosfo/ Super Shuttle]. Shared shuttle service. Book in advance.

Other options can be found on the [https://www.flysfo.com/to-from/ground-transportation SFO website].

====Mountain View Office Shuttle====
We will provide a shuttle from the Mountain View office on Monday, June 11th (1:00 pm and 3:00 pm). They will depart from the main entrance. We will return to Mountain View on Saturday, June 16 (10:00 am and 12:30 pm). They will depart the Marriott.

You can get dropped off or park at the office until 10:00 pm Sunday, June17. There will be normal security patrols however, you should remove valuables from view and secure your vehicle.

====From the Bay Area but not taking the Mountain View Office Shuttle?====
Our expectation is that you commute to the hotel just as you would to the office in the Bay Area. If you normally take the BART or MUNI, do that. If you normally drive and pay for parking - that's up to you but hotel parking is not a reimbursable expense for the All Hands.

=='''Accessibility'''==

====Marriott Marquis====

The guestroom tower has accessible elevators, and accessible rooms (on request). The main entrance and pathway to hotel registration are accessible. All meeting space can be access via elevators.

====Evenings====
The Monday Night reception is at City View, which is located on the 4th floor of the METREON and is accessible from the ground floor via 2 passenger elevators and escalators. There is ADA access from all building entrances as well.. The Friday Night Party is at [https://www.exploratorium.edu/visit/accessibility Exploratorium], which has access to all levels by elevator.

=='''Immigration'''==
'''Any''' questions on immigration should be sent to immigration@mozilla.com.

If you are from a country that requires a B-1/B-2 business visitor visa to enter the US, please plan for it early as government processing times constantly change.

Please visit the following website to learn more about the visa application process and timing for your country: http://travel.state.gov/content/visas/english/visit/visitor.html#overview. Current estimated processing times at the US Embassies and Consulates abroad can be found at: https://travel.state.gov/content/visas/en/general/wait-times.html/

Some travelers may be eligible to travel to the United States without first applying for a B-1/B-2 visa, if they are eligible for the Visa Waiver Program (VWP or "ESTA"). You are eligible to apply for admission under the Visa Waiver Program (VWP) if you:

*Intend to enter the United States for 90 days or less for business, pleasure or transit
*Have a valid passport lawfully issued to you by a Visa Waiver Program country: http://www.esta.us/visa_waiver_countries.html
*Have authorization to travel via the Electronic System for Travel Authorization: https://esta.cbp.dhs.gov/
*Arrive via a Visa Waiver Program signatory carrier (all commercial airlines meet this requirement)
*Have a return or onward ticket
*Travel may not terminate in contiguous territory or adjacent islands unless the traveler is a resident of one of those areas

=====Employee Travel FAQ=====
This [https://mana.mozilla.org/wiki/display/PR/Travel+FAQ FAQ] addresses questions about how to handle security concerns and electronic devices at the border and how to engage with US Customs & Border Protection (CBP). While it specifically focuses on concerns related to travel to the United States, much of this guidance is applicable to travel elsewhere. Mana access required.

=====Pocket Letter=====
A pocket letter is recommended to keep on hand for those who are entering the United States. It should accompany you whether or not you are required to have a visa to enter. You may request a copy of that letter when you register online. Please contact immigration@mozilla.com if you require a specific letter for your visa application or if you have any questions regarding your citizenship, visa capabilities or travel related questions.

=====ESTA Point of Contact=====
In the ESTA application you need to give a "U.S. Point of Contact Information".

Please list Casey McGill as your US Point of Contact.
Address: 331 East Evelyn Avenue, Mountain View, CA 94041 Phone: 408.505.3028

=='''San Francisco All Hands Expense Policy'''==
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. San Francisco All Hands Expense Report)

2. It must contain only those expenses relative to the All Hands Event (5-10 days of pre-post activity only)

3. If your submitted expense report for All Hands is submitted outside these guidelines, it will be rejected and you will be asked to re-submit with only All Hands Expenses

4. The deadline to submit the San Francisco All Hands Expense Report is '''July 31, 2018'''.

5. Expenses related to team events, parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved.

'''The intention of our all hands are to centrally organize a structure that includes:'''
*Meals (two/day + snacks)
*Transportation^
*Accommodations
*Some number of social events

Due to the nature of the San Francisco, employees will be expensing specific meals. The amount that can be expensed will be communicated and expenses submitted can not exceed the approved amounts. Any social events that are not part of our central plan will generally be self-organized and funded by participants.

^Transportation for those based in the Bay Area is limited to "commuting" as you normally would. Expenses for commuting are not reimbursable. We have provided shuttles from the MV office for those based in the south bay. For those who that doesn't make sense to use, commute using your normal means. We will not reimburse for hotel parking.

=====Cell phone reimbursement policy=====
Cell phone reimbursement must be approved by your manager prior to submitting the expense. Teams will decide for their staff what is appropriate to expense.

=====Internet reimbursement policy=====
Internet will be provided in all guestrooms and meeting space in all hotels. If you opt to upgrade/add service, those costs are not reimbursable, unless previously approved by your manager and are for business reasons.

If you have questions about any of this, please reach out to bmark@mozilla.com

=='''Families/Guests in San Francisco'''==

Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made. Family should not join you during your work sessions and meals. Please note that what we are able to do for families varies by each location.

''Volunteers, summer interns and outreachy interns will be sharing rooms and are unable to invite family to join them.''

====Quick summary logistics====

'''Air Travel''': Family travel can be booked/coordinated through Egencia by calling direct; or on your own. Employees do need to book via Egencia regardless of how families are booked.

'''Hotel''': They are welcome to stay with you, however, any additional room expenses will be yours to cover. All room rates are based upon single occupancy and costs to add guests vary by hotel. Breakfast is not included in any of the guest room rates. Once hotel reservations are made, we will provide a link or contact add guests.

'''Meals''': Breakfast will be provided to All Hands registered guests, for lunch families are on their own. They are invited to join our Monday & Friday evening festivities, we just ask that you let us know they'll be there in registration.

=='''Extracurricular Activities'''==
Costs for these activities are self-funded and can not be expensed. Feel free to add activities and invite others.

* '''[https://public.etherpad-mozilla.org/p/sf-day-hike-2018 Hiking!]'''
* '''[https://docs.google.com/document/d/1X1SdrUQWUiE82vfu-pjff-TZb7poLvPRZOIaPzjaUqI/ Running!]'''
* '''[https://docs.google.com/spreadsheets/d/1bPvBtcwNac_ObdiKjmypdujMDNduS2OfliMUxDisVNM/edit?usp=sharing Major League Baseball! Houston Astros vs Oakland Athletics, June 12 19:05 PDT]'''
* '''[https://www.museumoficecream.com/ Museum of Ice Cream]'''

Firefox/EnterprisePolicies

2018-03-14T16:31:22Z

MikeKaply: Point to devmo

This content is now hosted on developer.mozilla.org:

https://developer.mozilla.org/Firefox/Enterprise_deployment

WeeklyUpdates/2018-03-12

2018-03-12T16:57:41Z

MikeKaply: Fix URL

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* https://air.mozilla.org/channels/project-meeting/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

* Big thanks to Tech Speakers Yuli, Flaki, Miguel, and Ram who gave tech talks and workshops last week in Spain, Iceland, Venezuela, and India.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
* [[WebExtensions/Triage#Purpose_of_Meeting|WebExtensions APIs triage]]
** 17:30 UTC / 10:30am PDT | ACE Vidyo Rooms
** Because of North American Daylight Saving Time, the time of this meeting might have shifted for you! Please doublecheck the timezone conversion for your region.

* 2018 [[Internet Health Report]] Preview & GAMESHOW!
** Mozilla’s 2018 Internet Health Report is officially launching on March 20th, and all Mozillians (staff & NDA) are invited to this exclusive sneak peek! Join your host Solana (Internet Health Report Editor) and three special guests to see, discuss and debate some of the most interesting findings in the report.
** ''When:'' 9:30am PST/12:30pm EST/5:30pm CET
** ''Where:'' Air Mozilla and/or in Mozilla offices
** ''Participate:'' #InternetHealthReport on Slack

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [[Add-ons/Community/Meetings|Add-ons Community Meeting]]
** 15:30 UTC / 8:30am PDT

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
*SUMO Day Firefox 59, come and help Firefox users in [https://mzl.la/2esAaWE Social] and in the [https://support.mozilla.org Support Forums]:
**Sign up today: [https://public.etherpad-mozilla.org/p/sumo-day Etherpad with all the details] and see you there!

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
*Social Support Meeting 9am PST Meeting agenda [https://mzl.la/2esAaWE Meeting agenda]
**Join live in the SUMO Vidyo room(details on how to join in the agenda doc)
*SUMO Day Firefox 59, come and help Firefox users in [https://mzl.la/2esAaWE Social] and in the [https://support.mozilla.org Support Forums]:
**Curious about how support works at mozilla? Contact guigs@mozilla.com
**What is SUMO?[https://support.mozilla.org/en-US/get-involved Read more here]

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Caitlin Neiman
| Add-ons Community Manager
| The Quantum Extensions Challenge
| MTV
| No
| https://docs.google.com/presentation/d/1ujT6FkE_GfwxvHybwrw2-ffP9bN5mS_7JrPx763Sl48/edit?usp=sharing
| https://extensionschallenge.com
|-
| Asa Dotzler
| Firefox Roadmap
| Weekly Firefox Update
| MTV
| No
| n/a
| [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2018-03-12 2018-03-12]
|-
| Mike Kaply
| Enterprise and more
| Firefox Enterprise
| MTV
| No
| n/a
| [https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment Enterprise on devmo]
|-
| Michael Van Kleeck
| Enterprise Solutions Architect
| The Weekly MinIT!
| MozPDX- The New Commons!
| No
| n/a
| https://wiki.mozilla.org/IT/WeeklyMinIT
|-
| Jessica Margolin
| Analysis & Research Community Manager
| n/a
| ARC call
| No
| n/a
| n/a
|-
| Azita Rashed
| Senior Director of Engineering, Research
| Emerging Technologies Weekly Update
| MTV
| No
| n/a
| https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#March_12th.2C_2018
|-
| Lisa Gray
|
| New Hire Onboarding
| MTV
| Yes
| Slides: https://docs.google.com/presentation/d/1C9MOhRdhbT5Fo-UxfXMReTey4JCgqFGCnyIgrWWe9ek/edit?ts=5aa61cef
|
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-

|-
| Their Name
| Your Name
| Intro location
| Their Location
| Their Role
|-
|-
| March Cultural Onboarding NHs
| Lisa Gray
| MV Commons
| MV Commons
| Various
|-
|}

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

WeeklyUpdates/2018-03-12

2018-03-12T16:55:26Z

MikeKaply: Add Enterprise speaker

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* https://air.mozilla.org/channels/project-meeting/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

* Big thanks to Tech Speakers Yuli, Flaki, Miguel, and Ram who gave tech talks and workshops last week in Spain, Iceland, Venezuela, and India.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
* [[WebExtensions/Triage#Purpose_of_Meeting|WebExtensions APIs triage]]
** 17:30 UTC / 10:30am PDT | ACE Vidyo Rooms
** Because of North American Daylight Saving Time, the time of this meeting might have shifted for you! Please doublecheck the timezone conversion for your region.

* 2018 [[Internet Health Report]] Preview & GAMESHOW!
** Mozilla’s 2018 Internet Health Report is officially launching on March 20th, and all Mozillians (staff & NDA) are invited to this exclusive sneak peek! Join your host Solana (Internet Health Report Editor) and three special guests to see, discuss and debate some of the most interesting findings in the report.
** ''When:'' 9:30am PST/12:30pm EST/5:30pm CET
** ''Where:'' Air Mozilla and/or in Mozilla offices
** ''Participate:'' #InternetHealthReport on Slack

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [[Add-ons/Community/Meetings|Add-ons Community Meeting]]
** 15:30 UTC / 8:30am PDT

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
*SUMO Day Firefox 59, come and help Firefox users in [https://mzl.la/2esAaWE Social] and in the [https://support.mozilla.org Support Forums]:
**Sign up today: [https://public.etherpad-mozilla.org/p/sumo-day Etherpad with all the details] and see you there!

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
*Social Support Meeting 9am PST Meeting agenda [https://mzl.la/2esAaWE Meeting agenda]
**Join live in the SUMO Vidyo room(details on how to join in the agenda doc)
*SUMO Day Firefox 59, come and help Firefox users in [https://mzl.la/2esAaWE Social] and in the [https://support.mozilla.org Support Forums]:
**Curious about how support works at mozilla? Contact guigs@mozilla.com
**What is SUMO?[https://support.mozilla.org/en-US/get-involved Read more here]

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Caitlin Neiman
| Add-ons Community Manager
| The Quantum Extensions Challenge
| MTV
| No
| https://docs.google.com/presentation/d/1ujT6FkE_GfwxvHybwrw2-ffP9bN5mS_7JrPx763Sl48/edit?usp=sharing
| https://extensionschallenge.com
|-
| Asa Dotzler
| Firefox Roadmap
| Weekly Firefox Update
| MTV
| No
| n/a
| [https://wiki.mozilla.org/Firefox/Roadmap/Updates#2018-03-12 2018-03-12]
|-
| Mike Kaply
| Enterprise and more
| Firefox Enterprise
| MTV
| No
| n/a
| [https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment]
|-
| Michael Van Kleeck
| Enterprise Solutions Architect
| The Weekly MinIT!
| MozPDX- The New Commons!
| No
| n/a
| https://wiki.mozilla.org/IT/WeeklyMinIT
|-
| Jessica Margolin
| Analysis & Research Community Manager
| n/a
| ARC call
| No
| n/a
| n/a
|-
| Azita Rashed
| Senior Director of Engineering, Research
| Emerging Technologies Weekly Update
| MTV
| No
| n/a
| https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology#March_12th.2C_2018
|-
| Lisa Gray
|
| New Hire Onboarding
| MTV
| Yes
| Slides: https://docs.google.com/presentation/d/1C9MOhRdhbT5Fo-UxfXMReTey4JCgqFGCnyIgrWWe9ek/edit?ts=5aa61cef
|
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-

|-
| Their Name
| Your Name
| Intro location
| Their Location
| Their Role
|-
|-
| March Cultural Onboarding NHs
| Lisa Gray
| MV Commons
| MV Commons
| Various
|-
|}

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

Mobile/Platform/Notes/27-Sep-2017

2017-09-29T19:33:59Z

MikeKaply: Add Huawei bugs

__NOTOC__
== Details ==

* Wednesdays - 8:30am Pacific, 11:30pm Eastern, 15:30 UTC
{{conf|99998}}
* irc.mozilla.org #mobile for backchannel
* [https://v.mozilla.com/flex.html?roomdirect.html&key=xpW6Vm67G2iW Mobile] Vidyo Room

== Schedule ==
* [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Release calendar]

== Topics for This Week ==

== Tracking Review ==
===Beta===
*Next Build: 

<bugzilla>
{
"cf_blocking_fennec": "57+",
"resolution": "---",
"include_fields": "id, summary, status, assigned_to, last_change_time",
"order": "bug_id"
}
</bugzilla>

===Nightly===
*Next Build: 

<bugzilla>
{
"cf_blocking_fennec": "Nightly+",
"resolution": "---",
"include_fields": "id, summary, status, assigned_to, last_change_time",
"order": "bug_id"
}
</bugzilla>

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?

===James W. (snorp)===







* Looking at why audio doesn't work in GeckoView outside of Fennec

===JChen===



{{mybugs|nchen@mozilla.com}}



===Randall Barker===

===Eugen Sawin===

{{mybugs|esawin@mozilla.com}}

===Dylan Roeh===

{{mybugs|droeh@mozilla.com}}

===Bob Clary===
* Stability much improved with crash fixes.
* Performance much improved over September.
* Working on re-enabling Unit Tests.
* GeckoView example now running with e10s and non-e10s.

===Mike Kaply===

Huawei Bugs
* FIXED {{Bug|1401279}} java.lang.IllegalArgumentException: Cannot add a null child view to a ViewGroup when dismissing main menu
* {{Bug|1401269}} java.lang.IndexOutOfBoundsException in Home Pager touch event handling
* {{Bug|1401275}} ANR on Android O reported by partner - at org.mozilla.gecko.gfx.LayerView.updateCompositor(LayerView.java:593)
* {{Bug|1401280}} java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.TextView.setEnabled(boolean)' on a null object reference at org.mozilla.gecko.preferences.CustomListPreference.configureShownDialog (Android O)
* {{Bug|1401281}} ANR on Android O reported by partner at org.mozilla.gecko.widget.GeckoPopupMenu.setAnchor(GeckoPopupMenu.java:119)
* {{Bug|1401282}} Sending a null intent to the search activity crashes Firefox
* {{Bug|1401285}} ANR on Android O reported by partner

[[Category:Wikipage templates]]

Mobile/Platform/Notes

2017-09-13T05:08:58Z

MikeKaply: Add Sept 13

{{AndroidNav}}
There will be a meeting each week to discuss the general status of [[Mobile]]. Please use [irc://irc.mozilla.org/%23mobile #mobile] or [https://mail.mozilla.org/listinfo/mobile-firefox-dev mobile-firefox-dev@mozilla.org] for communication.

== Meeting Details ==

*Tuesdays @ 9:00AM PST
{{conf|99998}}
*[irc://irc.mozilla.org/%23mobile #mobile] for backchannel
*[https://v.mozilla.com/flex.html?roomdirect.html&key=xpW6Vm67G2iW Mobile Vidyo Room]

== Meeting Notes ==
Create a new weekly agenda from the [[Mobile/Platform/Notes/Template|template]]:

'''''Remember:''''' You'll still need to link it below!
<createbox>
align=left
type=create
preload=Mobile/Platform/Notes/Template
default={{#time: d-M-Y | wednesday}}
prefix=Mobile/Platform/Notes/
</createbox>

{| class="wikitable collapsible" style="width: 100%"
! 2017
|-
|
* [[/13-Sep-2017|Sep 13, 2017]]
* [[/06-Sep-2017|Sep 6, 2017]]
* [[/30-Aug-2017|Aug 30, 2017]]
* [[/23-Aug-2017|Aug 23, 2017]]
* [[/16-Aug-2017|Aug 16, 2017]]
* [[/09-Aug-2017|Aug 9, 2017]]
* [[/02-Aug-2017|Aug 2, 2017]]
* [[/19-Jul-2017|Jul 19, 2017]]
* [[/12-Jul-2017|Jul 12, 2017]]
* [[/05-Jul-2017|Jul 5, 2017]] (no meeting)
* [[/28-Jun-2017|Jun 28, 2017]] (no meeting: All Hands San Francisco)
* [[/21-Jun-2017|Jun 21, 2017]] (no meeting)
* [[/14-Jun-2017|Jun 14, 2017]]
* [[/07-Jun-2017|Jun 7, 2017]]
* [[/31-May-2017|May 31, 2017]]
* [[/24-May-2017|May 24, 2017]]
* [[/17-May-2017|May 17, 2017]]
* [[/10-May-2017|May 10, 2017]]
* [[/03-May-2017|May 03, 2017]]
* [[/26-Apr-2017|Apr 26, 2017]]
* [[/19-Apr-2017|Apr 19, 2017]]
* [[/12-Apr-2017|Apr 12, 2017]]
* [[/05-Apr-2017|Apr 5, 2017]]
* [[/29-Mar-2017|Mar 29, 2017]]
* [[/15-Mar-2017|Mar 15, 2017]]
* [[/08-Mar-2017|Mar 8, 2017]]
* [[/01-Mar-2017|Mar 1, 2017]]
* [[/22-Feb-2017|Feb 22, 2017]]
* [[/15-Feb-2017|Feb 15, 2017]]
* [[/08-Feb-2017|Feb 08, 2017]]
* [[/01-Feb-2017|Feb 01, 2017]]
* [[/25-Jan-2017|Jan 25, 2017]]
* [[/18-Jan-2017|Jan 18, 2017]]
* [[/04-Jan-2017|Jan 4, 2017]]
|}

{| class="wikitable collapsible" style="width: 100%"
! 2016
|-
|
* [[/21-Dec-2016|Dec 21, 2016]]
* [[/14-Dec-2016|Dec 14, 2016]] (no meeting)
* [[/07-Dec-2016|Dec 7, 2016]] (no meeting: All Hands Hawaii)
* [[/30-Nov-2016|Nov 30, 2016]]
* [[/23-Nov-2016|Nov 23, 2016]]
* [[/16-Nov-2016|Nov 16, 2016]]
* [[/09-Nov-2016|Nov 9, 2016]]
* [[/02-Nov-2016|Nov 2, 2016]]
* [[/26-Oct-2016|Oct 26, 2016]]
* [[/19-Oct-2016|Oct 19, 2016]]
* [[/12-Oct-2016|Oct 12, 2016]] (no meeting)
* [[/05-Oct-2016|Oct 5, 2016]]
* [[/28-Sep-2016|Sep 28, 2016]]
* [[/21-Sep-2016|Sep 21, 2016]]
* [[/14-Sep-2016|Sep 14, 2016]]
* [[/07-Sep-2016|Sep 7, 2016]]
* [[/31-Aug-2016|Aug 31, 2016]]
* [[/24-Aug-2016|Aug 24, 2016]]
* [[/17-Aug-2016|Aug 17, 2016]]
* [[/10-Aug-2016|Aug 10, 2016]]
* [[/03-Aug-2016|Aug 3, 2016]]
* [[/27-Jul-2016|Jul 27, 2016]]
* [[/20-Jul-2016|Jul 20, 2016]] (missing esawin, droeh)
* [[/13-Jul-2016|Jul 13, 2016]] (no meeting)
* [[/06-Jul-2016|Jul 6, 2016]]
* [[/29-Jun-2016|Jun 29, 2016]] (no meeting)
* [[/22-Jun-2016|Jun 22, 2016]]
* [[/15-Jun-2016|Jun 15, 2016]] (no meeting: All Hands London)
* [[/08-Jun-2016|Jun 8, 2016]]
* [[/01-Jun-2016|Jun 1, 2016]]
* [[/25-May-2016|May 25, 2016]]
* [[/18-May-2016|May 18, 2016]]
* [[/11-May-2016|May 11, 2016]]
* [[/04-May-2016|May 04, 2016]]
* [[/27-Apr-2016|Apr 27, 2016]]
* [[/20-Apr-2016|Apr 20, 2016]]
* [[/06-Apr-2016|Apr 6, 2016]]
* [[/30-Mar-2016|Mar 30, 2016]]
* [[/23-Mar-2016|Mar 23, 2016]]
* [[/16-Mar-2016|Mar 16, 2016]]
* [[/09-Mar-2016|Mar 9, 2016]]
* [[/02-Mar-2016|Mar 2, 2016]]
* [[/24-Feb-2016|Feb 24, 2016]]
* [[/17-Feb-2016|Feb 17, 2016]]
* [[/10-Feb-2016|Feb 10, 2016]]
* [[/03-Feb-2016|Feb 3, 2016]]
* [[/27-Jan-2016|Jan 27, 2016]]
* [[/20-Jan-2016|Jan 20, 2016]]
* [[/05-Jan-2016|Jan 5, 2016]]
|}

{| class="wikitable collapsible" style="width: 100%"
! 2015
|-
|
* [[/15-Dec-2015|Dec 15, 2015]]
* [[/01-Dec-2015|Dec 1, 2015]]
* [[/24-Nov-2015|Nov 24, 2015]]
* [[/10-Nov-2015|Nov 10, 2015]]
* [[/03-Nov-2015|Nov 3, 2015]]
* [[/27-Oct-2015|October 27, 2015]]
* [[/20-Oct-2015|October 20, 2015]]
* [[/13-Oct-2015|October 13, 2015]]
* [[/06-Oct-2015|October 6, 2015]]
* [[/29-Sep-2015|September 29, 2015]]
* [[/22-Sep-2015|September 22, 2015]]
* [[/15-Sep-2015|September 15, 2015]]
* [[/08-Sep-2015|September 8, 2014]]
* [[/01-Sep-2015|September 1, 2015]]
|}

Mobile/Platform/Notes/13-Sep-2017

2017-09-13T05:06:23Z

MikeKaply: Created page with "__NOTOC__ == Details == * Wednesdays - 8:30am Pacific, 11:30pm Eastern, 15:30 UTC {{conf|99998}} * irc.mozilla.org #mobile for backchannel * [https://v.mozilla.com/flex.html?..."

Mobile/Distribution Files

2017-09-11T18:54:59Z

MikeKaply: Title Guidance

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* ApplicationPreferences (optional)
** This sets as the app-scoped SharedPreferences for the entire application. Since GeckoPreferenceFragment only accept application-scoped sharedPreferences, this object will let partner also have the ability to override them.
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"ApplicationPreferences": {
"newtab.load_homepage": "true"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The title of your suggested site should be short, as it will only be displayed one line. Multiple suggested sites should not begin with the same text.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds) - Firefox 57 and above'''
* xxhdpi: 270x270
* xhdpi: 180x180
* hdpi: 135x135

'''Images Sizes (Bounds) - Firefox 56 and below'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 45 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details) or add ''export MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER='' to mozconfig in Firefox 50 or later.
** For '''Firefox for Android 44 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
# mount -o rw,remount /system
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.firefox or org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.firefox/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

You can also do this from another Android application:
<pre>
Intent i = new Intent("com.android.vending.INSTALL_REFERRER");
i.setPackage("org.mozilla.firefox");
i.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
i.putExtra("referrer", "utm_source=mozilla&utm_content=testsigned&utm_campaign=distribution");
getContext().sendBroadcast(i);
</pre>

You can the below example link to install the testsigned example package:

https://play.google.com/store/apps/details?id=org.mozilla.firefox&referrer=utm_source%3Dmozilla%26utm_content%3Dtestsigned%26utm_campaign%3Ddistribution

This must be on a device that does not have Firefox installed.

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Mobile/Distribution Files

2017-09-11T18:54:08Z

MikeKaply: Title guidance

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* ApplicationPreferences (optional)
** This sets as the app-scoped SharedPreferences for the entire application. Since GeckoPreferenceFragment only accept application-scoped sharedPreferences, this object will let partner also have the ability to override them.
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"ApplicationPreferences": {
"newtab.load_homepage": "true"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

The title of your suggested site should be short, as it will only be displayed one line. Multiple suggested sites should not begin with the same text.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds) - Firefox 57 and above'''
* xxhdpi: 270x270
* xhdpi: 180x180
* hdpi: 135x135

'''Images Sizes (Bounds) - Firefox 56 and below'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 45 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details) or add ''export MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER='' to mozconfig in Firefox 50 or later.
** For '''Firefox for Android 44 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
# mount -o rw,remount /system
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.firefox or org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.firefox/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

You can also do this from another Android application:
<pre>
Intent i = new Intent("com.android.vending.INSTALL_REFERRER");
i.setPackage("org.mozilla.firefox");
i.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
i.putExtra("referrer", "utm_source=mozilla&utm_content=testsigned&utm_campaign=distribution");
getContext().sendBroadcast(i);
</pre>

You can the below example link to install the testsigned example package:

https://play.google.com/store/apps/details?id=org.mozilla.firefox&referrer=utm_source%3Dmozilla%26utm_content%3Dtestsigned%26utm_campaign%3Ddistribution

This must be on a device that does not have Firefox installed.

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Mobile/Distribution Files

2017-09-11T18:52:42Z

MikeKaply: Update Image specs

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* ApplicationPreferences (optional)
** This sets as the app-scoped SharedPreferences for the entire application. Since GeckoPreferenceFragment only accept application-scoped sharedPreferences, this object will let partner also have the ability to override them.
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"ApplicationPreferences": {
"newtab.load_homepage": "true"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds) - Firefox 57 and above'''
* xxhdpi: 270x270
* xhdpi: 180x180
* hdpi: 135x135

'''Images Sizes (Bounds) - Firefox 56 and below'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 45 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details) or add ''export MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER='' to mozconfig in Firefox 50 or later.
** For '''Firefox for Android 44 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
# mount -o rw,remount /system
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.firefox or org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.firefox/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

You can also do this from another Android application:
<pre>
Intent i = new Intent("com.android.vending.INSTALL_REFERRER");
i.setPackage("org.mozilla.firefox");
i.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
i.putExtra("referrer", "utm_source=mozilla&utm_content=testsigned&utm_campaign=distribution");
getContext().sendBroadcast(i);
</pre>

You can the below example link to install the testsigned example package:

https://play.google.com/store/apps/details?id=org.mozilla.firefox&referrer=utm_source%3Dmozilla%26utm_content%3Dtestsigned%26utm_campaign%3Ddistribution

This must be on a device that does not have Firefox installed.

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

MozWeek/Austin

2017-09-11T15:16:21Z

MikeKaply: Fix link

MozWeek/Austin

2017-09-11T15:15:40Z

MikeKaply: Add new Austin activities

Mobile/Platform/Notes/30-Aug-2017

2017-08-30T15:28:00Z

MikeKaply: Update status

__NOTOC__
== Details ==

* Wednesdays - 8:30am Pacific, 11:30pm Eastern, 15:30 UTC
{{conf|99998}}
* irc.mozilla.org #mobile for backchannel
* [https://v.mozilla.com/flex.html?roomdirect.html&key=xpW6Vm67G2iW Mobile] Vidyo Room

== Schedule ==
* [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Release calendar]

== Topics for This Week ==

== Tracking Review ==
===Beta===
*Next Build: 

<bugzilla>
{
"cf_blocking_fennec": "56+",
"resolution": "---",
"include_fields": "id, summary, status, assigned_to, last_change_time",
"order": "bug_id"
}
</bugzilla>

===Nightly===
*Next Build: 

<bugzilla>
{
"cf_blocking_fennec": "Nightly+",
"resolution": "---",
"include_fields": "id, summary, status, assigned_to, last_change_time",
"order": "bug_id"
}
</bugzilla>

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?

===James W. (snorp)===







===JChen===



{{mybugs|nchen@mozilla.com}}



===Randall Barker===

===Eugen Sawin===

{{mybugs|esawin@mozilla.com}}

===Dylan Roeh===

{{mybugs|droeh@mozilla.com}}

===Bob Clary===
* tested Randall's patch in {{Bug|1392705}} - Intermittent autophone-s1s2 | application crashed [@ libc.so + 0x49da0]
* Would be nice:
** {{Bug|1392690}} - Intermittent autophone-s1s2 | application crashed [@ libc.so + 0x1a772]
** {{Bug|1392693}} - Intermittent autophone-s1s2 | application crashed [@ libc.so + 0x42374]
* Fixed {{Bug|1394960}} - Autophone - add android-api-16 as a supported platform.
** Note for try we need to use platform android-api-16 on trunk and android-api-15 on beta and release. Currently trychooser only supports android-api-15.
** Missed builds due to api change:
*** [https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-searchStr=autophone&exclusion_profile=false&group_state=expanded&fromchange=d814f791de3bba0fce843614b41ca9696ce57b15&tochange=8f221407c6006ac1de529da77ecc18431dde3e99 mozilla-central]
*** [https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&filter-searchStr=autophone&exclusion_profile=false&group_state=expanded&fromchange=816239d6caef3912ad00be8e2cb6f6dae7ebf240&tochange=2f39c03124665364d7465c7b9873a6e5c3c1f2b9 mozilla-inbound]
*** [https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=autophone&exclusion_profile=false&fromchange=e3c7045f22a712f062e45ab45642c55fca0e48f7&group_state=expanded&tochange=04b1b915604a918556f7b6d9ce36ca591752715c autoland]
** Unit tests particularly media have gone to hell.

===Mike Kaply===

* Need to move to latest Adjust SDK - {{Bug|1394840}}
* Any timeline for Android O?

[[Category:Wikipage templates]]

File:ReportSiteNightlyIcon.png

2017-08-21T13:47:59Z

MikeKaply: MikeKaply uploaded a new version of "File:ReportSiteNightlyIcon.png"

Report Site Issue icon in Firefox Nightly menu

Mobile/Distribution Files

2017-07-17T16:06:58Z

MikeKaply: Adding play store URL

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* ApplicationPreferences (optional)
** This sets as the app-scoped SharedPreferences for the entire application. Since GeckoPreferenceFragment only accept application-scoped sharedPreferences, this object will let partner also have the ability to override them.
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"ApplicationPreferences": {
"newtab.load_homepage": "true"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds)'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 45 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details) or add ''export MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER='' to mozconfig in Firefox 50 or later.
** For '''Firefox for Android 44 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
# mount -o rw,remount /system
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.firefox or org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.firefox/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

You can also do this from another Android application:
<pre>
Intent i = new Intent("com.android.vending.INSTALL_REFERRER");
i.setPackage("org.mozilla.firefox");
i.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
i.putExtra("referrer", "utm_source=mozilla&utm_content=testsigned&utm_campaign=distribution");
getContext().sendBroadcast(i);
</pre>

You can the below example link to install the testsigned example package:

https://play.google.com/store/apps/details?id=org.mozilla.firefox&referrer=utm_source%3Dmozilla%26utm_content%3Dtestsigned%26utm_campaign%3Ddistribution

This must be on a device that does not have Firefox installed.

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Partnering/Repacks/Policy and Process

2017-05-19T18:43:26Z

MikeKaply: Removing old Mercurial info

== Overview ==

This document outlines the high level policy for Firefox custom bundles, applicable to all custom distributions of Firefox produced by Mozilla for partners. Some of these requirements may be in conflict with existing written agreements, otherwise all existing distributions are expected to come into compliance with these requirements as soon as possible, and no later than June 30, 2015. Some requirements will come into place over the first half of 2015, in order to allow time for any required changes to products or processes.

For more information on becoming a Mozilla distribution partner, please refer to Becoming a Mozilla Distribution Partner.

== Review Process and Timelines ==

* Changes to custom configurations must be submitted no later than three weeks prior to the next regularly scheduled release, in order to be included in custom builds for that release.
** After this time, only significant bug fix changes will be considered for that release.
* Beta builds are produced twice weekly, and upon approval reviewers will advise as to the next set of builds which will contain the approved changes.
* Release candidate builds will generally be available one week prior to the target release date.
* Partners are not permitted to distribute custom builds prior to the official Mozilla release.

For an overview of the change submission process, please refer to the [[#Submitting_Changes|instructions below]].

== Build Identification ==

* Each unique configuration must be identified separately through a unique distribution ID.
* For each new custom distribution, partners must clearly identify the target market(s) and languages for the desired configuration, as well as any other reasonable information necessary to understand the scope for any potential distribution.

== Quality Requirements ==

* Mozilla will review and approve all changes to custom configuration. Mozilla does not do formal Quality Assurance testing on custom bundles. Distributors are expected to verify that all of their customizations are working as intended in the provided builds.

== Preferences ==

* All preference changes not explicitly required under existing agreements must be approved by Mozilla.
* No preference changes will be permitted that negatively impact the security or user experience of end users.
* Except where expressly covered by the distribution agreement, search default changes shall not be approved.

== Bookmarks ==

* Bookmarks must be clearly labelled, and should link only to relevant content from the partner in question.

== Add-ons ==

''Effective as of Firefox 39''

All bundled add-ons to be included with a custom distribution must already be signed in accordance with Mozilla's add-on signing policy. This will require that all bundled add-ons have passed full review through the AMO review process, whether that add-on is or is not distributed on AMO itself.

The process for submitting add-ons that are not to be hosted on AMO will be announced in the near future, and should be live in May 2015. If an add-on is already hosted on AMO at that time, signing will happen automatically. Distribution partners will have priority for reviews, please contact Partner Support for more details.

== Revenue-impacting Changes ==

''Effective as of Firefox 38''

Firefox has a number of features that have revenue-bearing components, generally in the form of partnerships or paid placements. These features include Search, Tiles, and other potential features. Except where otherwise agreed under a formal custom distribution agreement, no changes shall be permitted that negatively impact the revenue potential of these features. This includes changes that would be otherwise permitted within the scope of an add-on under the AMO policy.

== Submitting Changes ==

=== Version Control ===
Mozilla keeps all of our partner repack configuration files under version control in [https://github.com/ GitHub].

When a partner build is created, you will be given access to a repository that corresponds to your repack.
=== Creating a patch ===
This section assumes that you are already familiar with the basics of GitHub.

Here is a generalized workflow:
* fork the repository
* create a patch
* submit a pull request

After a pull request has been merged, you can request a build on Bugzilla if the update is urgent, otherwise you should wait for the normal Mozilla build cycle.

To expedite the bug filing process, I've created a template that partners can use to quickly file bugs under the correct product & component:
* Product: Release Engineering, Component: "Releases: Custom Builds"
* Or use this convenient template: [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&attach_text=&blocked=&bug_file_loc=http%3A%2F%2F&bug_ignored=0&bug_severity=normal&bug_status=NEW&cc=mconnor%40mozilla.com&cf_blocking_b2g=---&cf_blocking_fennec=---&cf_crash_signature=&cf_status_b2g18=---&cf_status_b2g_1_1_hd=---&cf_status_b2g_1_2=---&cf_status_b2g_1_3=---&cf_status_b2g_1_4=---&cf_status_firefox26=---&cf_status_firefox27=---&cf_status_firefox28=---&cf_status_firefox29=---&cf_status_firefox_esr24=---&cf_tracking_b2g18=---&cf_tracking_b2g_v1_2=---&cf_tracking_b2g_v1_3=---&cf_tracking_firefox26=---&cf_tracking_firefox27=---&cf_tracking_firefox28=---&cf_tracking_firefox29=---&cf_tracking_firefox_esr24=---&cf_tracking_firefox_relnote=---&cf_tracking_relnote_b2g=---&comment=REMINDER%3A%20Please%20provide%20a%20summary%20of%20the%20changes%20contained%20in%20this%20diff.&component=Releases%3A%20Custom%20Builds&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&dependson=&description=&flag_type-4=X&flag_type-481=X&flag_type-607=X&flag_type-791=X&flag_type-800=X&flag_type-803=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=Release%20Engineering&qa_contact=bhearsum%40mozilla.com&rep_platform=All&requestee_type-4=&requestee_type-607=&requestee_type-791=&requestee_type-800=&short_desc=Partner%20repack%20changes%20for%20%24PARTNERNAME&status_whiteboard=%5Bpartners%5D&target_milestone=---&version=other Partner repack config change bug template]

Please remember to change $PARTNERNAME in the bug summary to reflect the partner you requesting a build for.

Installer:Command Line Arguments

2017-05-15T12:45:05Z

MikeKaply: Add TaskbarShortcut option

''Please comment in the Talk page (use the Discussion tab above)''

IMPORTANT: 
DO NOT MIX command line options from different lines below (e.g. don't mix /S with /INI, etc.) 
The account performing the installation will require administrative privileges to properly complete the installation. 
This page applies only to the full installer and not the stub installer. If you want to perform a silent install you cannot do so with the stub installer and you must use the full installer. Full installers for Firefox can be found at http://www.mozilla.org/firefox/all/ (or for Firefox [http://www.mozilla.org/firefox/organizations/ ESR] at http://www.mozilla.org/firefox/organizations/all/ ).

Silent install (always installs into the default location. Use the "Configuration ini file" option below to set the install location and other install options): 
<tt><path to setup executable> -ms</tt>

Silent uninstall: 
<tt><path to setup executable> /S</tt>

Configuration ini file: 
<tt><path to setup executable> [/INI=<full path to configuration ini file>]</tt>

When specifying a configuration ini file the installer will always run silently. When specifying a Configuration ini file other command line switches should not be specified and may have unexpected results

Configuration ini file syntax and available settings:
<pre>[Install]
;
; Remove the semicolon (;) to un-comment a line.
;
; The name of the directory where the application will be installed in the
; system's program files directory. The security
; context the installer is running in must have write access to the
; installation directory. Also, the directory must not exist or if it exists
; it must be a directory and not a file. If any of these conditions are not met
; the installer will abort the installation with an error level of 2. If this
; value is specified then InstallDirectoryPath will be ignored.
; InstallDirectoryName=Mozilla Firefox

; The full path to the directory to install the application. The security
; context the installer is running in must have write access to the
; installation directory. Also, the directory must not exist or if it exists
; it must be a directory and not a file. If any of these conditions are not met
; the installer will abort the installation with an error level of 2.
; InstallDirectoryPath=c:\firefox\

; By default all of the following shortcuts are created. To prevent the
; creation of a shortcut specify false for the shortcut you don't want created.

; Create a shortcut for the application in the current user's QuickLaunch
; directory.
; QuickLaunchShortcut=false

; Create a shortcut for the application on the taskbar.
; TaskbarShortcut=false

; Create a shortcut for the application on the desktop. This will create the
; shortcut in the All Users Desktop directory and if that fails this will
; attempt to create the shortcuts in the current user's Start Menu directory.
; DesktopShortcut=false

; Create shortcuts for the application in the Start Menu. This will create the
; shortcuts in the All Users Start Menu directory and if that fails this will
; attempt to create the shortcuts in the current user's Start Menu directory.
; StartMenuShortcuts=false

; The directory name to use for the StartMenu folder (not available with
; Firefox 4.0 and above - see note below).
; note: if StartMenuShortcuts=false is specified then this will be ignored.
; StartMenuDirectoryName=Mozilla Firefox

; The MozillaMaintenance service is used for silent updates and may be used
; for other maintenance related tasks. It is an optional component.
; This option can be used in Firefox 16 or later to skip installing the service.
; MaintenanceService=false</pre>

As of Firefox 4.0 StartMenuDirectoryName is ignored due to the removal of the start menu directory for Firefox and the creation of a start menu shortcut in the root of the start menu (see {{bug|598779}}).

MozWeek/SanFrancisco2017

2017-04-03T17:24:03Z

MikeKaply: Correct airport typo

WebExtensions/Applications

2017-03-22T16:06:42Z

MikeKaply: Correct typo

Status: '''draft'''

= tl;dr =

Let's enable the running of WebExtensions add-ons built for Chrome with zero modification in Firefox.

'''Update: a few things have changed and some people came up with a much better plan that does not involve using mozilla.json, this was updated to reflect this.'''

== Bugs, bugs ==

Bugzilla: {{Bugzilla|1255562}} nope, this was replaced with {{Bugzilla|1262005}}, {{Bugzilla|1255564}}
Github: https://github.com/mozilla/addons/issues/61

= Rationale =

Currently to run a Chrome WebExtension in Firefox you have to alter the manifest.json to include the [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/applications applications data] for example, this is the minimum you need to get an add-on working.

"applications": {
"gecko": {
"id": "drumpfinator-firefox@donaldjdrumpf.com"
}
}

The downside here is that we are creating work for every add-on and add-on developer in supporting Firefox. Secondly, the addition of any metadata outside of the scope that Chrome shows a warning.

The use of an application id is something we could avoid because everything has to come through AMO to be signed and we could create it for the add-on developer.

= Proposal =

Please note: all the following only applies to WebExtension add-ons, other add-ons will be unchanged.

Because now all add-ons, be them hosted on AMO or hosted on a developers site have to go through AMO and be signed we now have the option to help developers out and do this for them. In the past this wouldn't have been possible.

== Rename field ==

Rename the field to '''browser_specific_settings'''. If other browsers support this key, then we can hope Chrome will start to ignore this key and not raise a warning in Chrome.

Add-on developers could keep track of their add-on along with add-on if they so with, but it won't interfere with the basic operation of the add-on.

The field is optional, developers can use it if they want to specify their add-on id in advance (for example if they are upgrading an old add-on to WebExtensions). Otherwise they can ignore it.

== Submitting an add-on ==

When submitting a WebExtension we would go through something like the following:
* see if browser_specific_settings > id exists in manifest.json
** if an add-on id exists, use it for the add-on
** continue
* see if applications > id exists in the manifest.json (for legacy)
** if an add-on id exists, use it for the add-on
** continue
* generate a new add-on id, add it to the appropriate AMO table for that add-on

The add-on developer can find their add-on id by:
* by accessing AMO and finding out
* using the API?
* ... should we do more here?

=== Signing an add-on ===

Each time the add-on is signed (for each version), it will pull the add-on id out of the appropriate AMO table and sign it with that add-on id. The add-on id will be in the signature and be consistent for each version of that add-on.

== Loading in Firefox ==

When Firefox loads an add-on we would go through something like the following:
* see if browser_specific_settings > id exists in manifest.json
** if an add-on id exists, use it for the add-on
** continue on to the usual signing checks
* see if applications > id exists in the manifest.json (for legacy)
** if an add-on id exists, use it for the add-on
** continue on to the usual signing checks
* if the add-on is signed
** the add-on is contained in the signing in the CN field? (should check that) of the signature
** use that add-on id
** continue on to the usual signing checks
* if the add-on id is not found and the add-on is being temporarily loaded through about:debugging
** generate a random add-on id
** continue
* if the add-on id is not found and the add-on is not being temporarily loaded, raise an error

This last point (raising an error) isn't great. What could we do about nightly and dev editions where developers could turn off the signing and then load an add-on? Just fail loudly?

== API ==

The [http://addons-server.readthedocs.org/en/latest/topics/api/signing.html signing APIs] for addons.mozilla.org are currently keyed off the add-on id. Developers using the API would need to know the add-on id, or specify it in mozilla.json.

To fix this, we also propose changing the AMO signing API from

'''PUT /api/v3/addons/[string:addon-id]/versions/[string:version]/'''

to

'''PUT /api/v3/addons/'''

and having the server pull the addon-id and version out of the submitted XPI (or generate them if they're missing).
(We should also return that data as fields in the response, so that the calling script would know what they were going to be.)

Tools like web-ext could go through the same steps as AMO.

== Validator ==

We'd have to alter the validator to make '''applications''' and '''browser_specific_settings''' optional.

= Out of scope =

== Compatibility ==

Compatibility checks for Chrome Add-ons submitted to AMO and/or for signing would be required. Add-ons that use unsupported APIs should be flagged and/or rejected to avoid user confusion/consternation.

Please see [https://github.com/mozilla/addons-server/issues/1337 bug 1337].

Mobile/Distribution Files

2017-01-04T18:48:29Z

MikeKaply: Updated Android install instructions

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds)'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 45 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details) or add ''export MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER='' to mozconfig in Firefox 50 or later.
** For '''Firefox for Android 44 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
# mount -o rw,remount /system
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.firefox or org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.firefox/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

You can also do this from another Android application:
<pre>
Intent i = new Intent("com.android.vending.INSTALL_REFERRER");
i.setPackage("org.mozilla.firefox");
i.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
i.putExtra("referrer", "utm_source=mozilla&utm_content=testsigned&utm_campaign=distribution");
getContext().sendBroadcast(i);
</pre>

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Mobile/Distribution Files

2016-10-04T21:30:19Z

MikeKaply: Add new mozconfig option for Firefox 50

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds)'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 45 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details) or add ''export MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER='' to mozconfig in Firefox 50 or later.
** For '''Firefox for Android 44 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
** find the mount point for /system in the list of mounts (for example if you see a line that says <code>/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0</code> your mount point is <code>/dev/block/mmcblk0p20</code>
# mount -o remount,rw <mount point> /system # (replace <device> with your device ID)
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.firefox/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

You can also do this from another Android application:
<pre>
Intent i = new Intent("com.android.vending.INSTALL_REFERRER");
i.setPackage("org.mozilla.firefox");
i.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
i.putExtra("referrer", "utm_source=mozilla&utm_content=testsigned&utm_campaign=distribution");
getContext().sendBroadcast(i);
</pre>

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Mobile/Distribution Files

2016-08-24T19:53:56Z

MikeKaply: Correct version for distribution

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds)'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 45 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details).
** For '''Firefox for Android 44 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
** find the mount point for /system in the list of mounts (for example if you see a line that says <code>/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0</code> your mount point is <code>/dev/block/mmcblk0p20</code>
# mount -o remount,rw <mount point> /system # (replace <device> with your device ID)
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.firefox/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

You can also do this from another Android application:
<pre>
Intent i = new Intent("com.android.vending.INSTALL_REFERRER");
i.setPackage("org.mozilla.firefox");
i.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
i.putExtra("referrer", "utm_source=mozilla&utm_content=testsigned&utm_campaign=distribution");
getContext().sendBroadcast(i);
</pre>

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Mobile/Distribution Files

2016-08-24T19:52:09Z

MikeKaply: Wrong version for new Android packaging

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds)'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 47 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details).
** For '''Firefox for Android 44 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
** find the mount point for /system in the list of mounts (for example if you see a line that says <code>/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0</code> your mount point is <code>/dev/block/mmcblk0p20</code>
# mount -o remount,rw <mount point> /system # (replace <device> with your device ID)
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.firefox/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

You can also do this from another Android application:
<pre>
Intent i = new Intent("com.android.vending.INSTALL_REFERRER");
i.setPackage("org.mozilla.firefox");
i.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
i.putExtra("referrer", "utm_source=mozilla&utm_content=testsigned&utm_campaign=distribution");
getContext().sendBroadcast(i);
</pre>

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Mobile/Distribution Files

2016-08-08T19:17:01Z

MikeKaply: Add Android mechanism

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds)'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 47 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details).
** For '''Firefox for Android 46 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
** find the mount point for /system in the list of mounts (for example if you see a line that says <code>/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0</code> your mount point is <code>/dev/block/mmcblk0p20</code>
# mount -o remount,rw <mount point> /system # (replace <device> with your device ID)
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.firefox/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

You can also do this from another Android application:
<pre>
Intent i = new Intent("com.android.vending.INSTALL_REFERRER");
i.setPackage("org.mozilla.firefox");
i.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES);
i.putExtra("referrer", "utm_source=mozilla&utm_content=testsigned&utm_campaign=distribution");
getContext().sendBroadcast(i);
</pre>

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Mobile/Distribution Files

2016-08-08T18:06:55Z

MikeKaply: Correct am syntax

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds)'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 47 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details).
** For '''Firefox for Android 46 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
** find the mount point for /system in the list of mounts (for example if you see a line that says <code>/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0</code> your mount point is <code>/dev/block/mmcblk0p20</code>
# mount -o remount,rw <mount point> /system # (replace <device> with your device ID)
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.fennec/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla\&utm_content=testsigned\&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Mobile/Distribution Files

2016-08-04T18:37:22Z

MikeKaply: Adding flag to include stopped packages.

Like [https://wiki.mozilla.org/Distribution_INI_File desktop], mobile Firefox supplies a way for partners to repackage a set of customization files into a Firefox build without recompiling. We don't want to make custom binary builds that need to be QA'd extensively. The "distribution files" concept allows a small set of external files to be used to customize a standard Firefox build. Things that can be customized include:
* Default bookmarks
* Preferences
* Lightweight themes
* Search engines
* Add-ons
* Quickshare defaults
* Suggested sites

A sample distribution directory is available on [https://github.com/mozilla/fennec-distribution-sample github].

==Overview==
There are currently three ways distribution files can be ... distributed:
# '''<big>APK distributions</big>''': A folder of distribution files is repackaged into the Android APK. During the first run, those files are extracted from the APK and stored in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory.
# '''<big>System distributions</big>''': A folder of distribution files are shipped with the ROM image in <code>/system/org.mozilla.firefox/distribution/*</code> directory. Shipping in this way ensures the files are not easily overwritten or removed by an application update. Note, files found in the <code>/data/data/org.mozilla.firefox/distribution/*</code> directory will "win" in cases where both locations are used.
# '''<big>Over-the-air distributions</big>''': A distribution zip file is downloaded over-the-air as a result of a post-install referrer intent. See {{bug|1013024}}. This feature should ship with Firefox 33.

Distributions are processed asynchronously during first run. Frontend code can chain post-distribution tasks via <code>Distribution.addOnDistributionReadyCallback</code>.

Each type of data has its own nuances:
* Default bookmarks are read from the APK directly or from the "distribution" folder (if it already exists) any time a profile is created. These bookmarks are created prior to Firefox's default bookmarks.
* Preferences are set as "default" preferences on each run, since a "default" preference only lasts for the lifetime of the session. They are created as "default" preferences to allow "user" preferences to override them.
* Lightweight themes are actually just preferences. The data for the theme must live online somewhere. Typical places are the AMO theme or getpersonas.com sites.
* Search engine plugins and add-ons must follow a fixed folder layout.
* If distribution data is processed after the initial quickshare set is loaded, these options won't take effect until next run ({{bug|1021176}}).

==Bookmarks==
Default bookmarks are specified in '''/distribution/bookmarks.json'''. This file should contain an array of bookmark JSON objects with the following properties:
* '''title''': (required) string for the bookmark title
* '''url''': (required) string for the bookmark URL
* title.<locale>: (optional) title string for the given locale
* url.<locale>: (optional) URL string for the given locale
* icon: (optional) data URI for the bookmark favicon
* pinned: (optional) boolean for whether or not to pin this bookmark to the about:home top sites
** NOTE: If a bookmark is pinned, it is not visible in the Bookmarks list. Pinning only affects Tops Sites.

Here is an example bookmarks.json:
[
{
"title": "Queso",
"url": "http://queso.com/",
"title.en_US": "Cheese",
"url.en_US": "http://cheese.com",
"icon": "data:image/png;base64,..."
}
]

==Preferences==
Preferences are specified in '''/distribution/preferences.json'''. This file should contain a JSON object with the following properties:
* Global
** '''id''': (required) a short string unique to this distribution
** '''version''': (required) version of the distribution (not the version of Firefox)
** '''about''': (required) a short descriptive (ui-visible) string for this distribution
** about.<locale>: (optional) descriptive string for the given locale
* Preferences (optional)
** This sets default Gecko preferences for the profile (i.e. prefs that would appear in about:config)
* LocalizablePreferences (optional)
* LocalizablePreferences.<locale> (optional)
* AndroidPreferences (optional)
** This sets Android SharedPreferences for the profile

Here is an example preferences.json:
{
"Global": {
"id": "testpartner",
"version": 1.0,
"about": "Afiliado de Prueba",
"about.en-US": "Test Partner"
},
"Preferences": {
"distribution.test.string": "a string pref",
"distribution.test.boolean": true,
"distribution.test.int": 5
},
"LocalizablePreferences": {
"distribution.test.localizeable": "http://test.org/%LOCALE%/%LOCALE%/",
"distribution.test.localizeable-override": "http://test.org/%LOCALE%/%LOCALE%/"
},
"LocalizablePreferences.en-US": {
"distribution.test.localizeable-override": "http://cheese.com"
},
"AndroidPreferences": {
"homepage": "http://www.mozilla.com"
}
}

==Lightweight Themes==
Lightweight themes are specified in the "Preferences" section of /distribution/preferences.json. Here is an example of the lightweight theme preferences needed for this to work:

"Preferences": {
"lightweightThemes.isThemeSelected": true,
"lightweightThemes.persisted.footerURL": false,
"lightweightThemes.persisted.headerURL": false,
"lightweightThemes.usedThemes": "[{\"id\":\"491717\",\"name\":\"colored trees\",\"headerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees.png?1358076678\",\"footerURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/trees-base.png?1358076678\",\"textcolor\":\"#1d022b\",\"accentcolor\":\"#000000\",\"iconURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview_small.jpg?1358076678\",\"previewURL\":\"http://getpersonas-cdn.mozilla.net/static/1/7/491717/preview.jpg?1358076678\",\"author\":\"birdyann\",\"description\":\"trees arbres colored colors couleurs\",\"updateURL\":\"https://www.getpersonas.com/en-US/update_check/491717\",\"version\":\"1358076678\",\"updateDate\":1359579038207,\"installDate\":1359579038207}]"
}

==Search Plugins==
Include search plugins in a directory structure like the following, and they will be
automatically loaded:

* distribution/
* searchplugins/
* common/
* <plugin.xml>
* <plugin.xml>
* ...
* locale/
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...
* <locale>/
* <plugin.xml>
* <plugin.xml>
* ...

If a directory for the locale the browser is running in doesn't exist, Firefox will automatically try the 'default' locale, as defined by the <code>distribution.searchplugins.defaultLocale</code> preference.

To set a given search engine as the default, you need to use <code>LocalizablePreferences</code> to override the <code>browser.search.defaultenginename</code> preference. You should also override the <code>browser.search.order.1</code> preference to put the default engine in the right sort order. For example:

{
...
"LocalizablePreferences": {
"browser.search.defaultenginename": "<name-of-engine>",
"browser.search.order.1": "<name-of-engine>"
...
}
...
}

==Add-ons==
Include add-ons in an extensions directory as follows, and they will be
automatically loaded:

* distribution/
* extensions/
* someaddon@somedomain.com.xpi
* ...

Be sure to name the add-on XPI with the ID that's specified in the add-on's install.rdf.

'''Note:''' As of Firefox 41, we require all add-ons to be signed through AMO, so you should make sure this XPI is signed properly before shipping in a distribution.

==Quickshare defaults==
Add a file named <code>history.xml</code> under <code>distribution/quickshare</code>. Its contents should be something like:

<pre>
<historical-records>
<historical-record activity="com.android.mms/com.android.mms.ui.ConversationComposer"
time="0"
weight="1"/>
</historical-records>
</pre>

==Suggested sites==
Added by {{bug|1012462}} in Firefox 33.

Use a directory tree like the following. Locales are named via a locale code, such as <code>en-US</code>.

* distribution/
* suggestedsites/
* locales/
* <locale>/
* suggestedsites.json
* res/
* hdpi/
* <distro>.png
* xxhdpi/
* <distro>.png

The suggestedsites.json file should be a JSON array:

[
{
url: "<site-url>",
title: "<site-title>",
imageurl: "gecko.distribution://<image-dir>/<image-name>",
bgcolor: "<color-hex-code>", /* "#FF00FF" with leading '#' */
trackingid: <tiles-id> /* optional integer */
},
...
]

Where <code><image-dir></code> is the directory containing the density-specific image directories (<code>mdpi</code>, <code>hdpi</code>, etc) and <code><image-name></code> is the filename under the density-specific directories without the file extension. For example, <code>gecko.distribution://suggestedsites/res/distroimage</code> image URL will be translated to <code><distribution-root-dir>/suggestedsites/res/xhdpi/distroimage.png</code> on a XHDPI device.

The list of suggested sites from the distribution will be prepended to the default list of suggested sites that ships with Firefox.

=== Image Specs ===

When creating images for use in Suggested Sites, please use the following guidelines. Make sure you provide images for all the DPI levels or the thumbnail may not look good on some devices:

'''Images Sizes (Bounds)'''
* xxhdpi: 375x195
* xhdpi: 250x130
* hdpi: 188x98
* mdpi:125x65

== Testing a distribution locally ==
'''Note''': you need a clean install. If you have already run Firefox, go to settings and clear the app's data

=== APK distribution ===
* To create a repackaged distribution:
** For '''Firefox for Android 47 and later''':
*** Your distribution folder contents should be at:
***:<pre>/path/to/fennec-distribution-sample/assets/distribution</pre>
*** Add a line like the following to your mozconfig:
***:<pre>ac_add_options --with-android-distribution-directory=/path/to/fennec-distribution-sample</pre>
*** Make sure you have run <code>./mach configure</code> before building and packaging
*** See {{bug|1163082}} for details.
*** '''Note''': By default the distribution is going into the [https://gecko.readthedocs.io/en/latest/mobile/android/fennec/bouncer.html install bouncer APK]. To change that set ''MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER'' to ''False'' in ''mobile/android/moz.configure'' (See {{bug|1258372}} for details).
** For '''Firefox for Android 46 and earlier''':
*** Put your distribution folder at <code>objdir/dist/bin/distribution</code>
*** Run <code>./mach package</code> to package the app
** When the app is launched, the distribution files will be copied out to <code>/data/data/org.mozilla.fennec_yourname/distribution</code>, and they will override a ROM image distribution if it is present

=== System distribution ===
* To create a ROM image distribution, follow these steps with a rooted phone:
** Copy the distribution files to a writable location
adb shell mkdir /data/local/tmp/distribution
adb push distribution /data/local/tmp/distribution
** Run <code>adb shell</code> to get and adb shell
$ su
# mount
** find the mount point for /system in the list of mounts (for example if you see a line that says <code>/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0</code> your mount point is <code>/dev/block/mmcblk0p20</code>
# mount -o remount,rw <mount point> /system # (replace <device> with your device ID)
# cp -r /data/local/tmp/distribution /system/<package>/ # (replace <package> with the ID for the package you want to test, e.g. org.mozilla.fennec)

==Testing distribution download==
A distribution download is triggered when two things are true:

* This is the first run of Firefox (or Clear Data has been used).
* An <code>INSTALL_REFERRER</code> intent has been received prior to launch.

The Google Play app takes care of sending that intent. You can also manually send it via <code>adb shell</code>. Assuming you're testing Nightly:

<pre>
am broadcast -a com.android.vending.INSTALL_REFERRER \
-n org.mozilla.fennec/org.mozilla.gecko.distribution.ReferrerReceiver \
-f 32 \
--es "referrer" "utm_source=mozilla&utm_medium=testmedium&utm_term=testterm&utm_content=testsigned&utm_campaign=distribution"
</pre>

This will fetch the "testsigned.jar" distribution.

(The -f 32 flag makes sure this intent is sent to stopped packages.)

Telemetry will be recorded for the download: <code>FENNEC_DISTRIBUTION_DOWNLOAD_TIME_MS</code> records the download time in milliseconds, and <code>FENNEC_DISTRIBUTION_CODE_CATEGORY</code> records the result. The value will be one of these:

; 0: Unexpected HTTP status.
; 1: HTTP 1xx. Should not occur.
; 2: HTTP 2xx. The expected result.
; 3: HTTP 3xx. Should not occur.
; 4: HTTP 4xx. Should not occur.
; 5: HTTP 5xx. Should not occur.
; 6: The device was offline.
; 7: Generic fetch exception.
; 8: Failure during processing of downloaded zip.
; 9: Security exception: malformed, corrupted, or modified signatures.
; 10: Malformed distribution file.
; 11: Fetch: socket error.
; 12: Fetch: SSL error.
; 13: Fetch: non-success HTTP response.
; 14: Fetch: invalid Content-Type header received.

==Crafting a distribution referrer==

These are the fields exposed in a referrer URL to Play:

; <code>utm_content</code>: '''The distribution name'''. Must be unique. Identifies the distribution name.
; <code>utm_campaign</code>: '''The campaign name'''. Must be <code>distribution</code>.
; <code>utm_source</code>: Original referrer. Must be <code>mozilla</code> for both downloadable distributions and campaign tracking.
; <code>utm_medium</code>: Campaign medium. E.g., <code>email</code>. Not used by Firefox.
; <code>utm_term</code>: Search terms. E.g., <code>web+browser</code>. Not used by Firefox.

== Distribution bundles ==

Firefox for Android 46.0 introduced support for distribution bundles based on the '''MCC''' (mobile country code, [https://en.wikipedia.org/wiki/Mobile_country_code]) and '''MNC''' (mobile network code) codes of the inserted SIM card. Instead of the default distribution directory Firefox will search a distribution in the following sub directories first:
* (distribution directory)/''<MCC>''/''<MNC>'' - For bundled distributions for specific network providers
* (distribution directory)/''<MCC>'' - For bundled distributions for specific countries
* (distribution directory)/''default'' - For bundled distributions with no matching MCC/MNC

=== Example distribution bundle ===
distribution
├── 208 // 208 = Country code of France
│ └── bookmarks.json // Bookmarks just for users with a SIM card of a French operator
├── 262 // 262 = Country code of Germany
│ └── 01 // 01 = Network code of "Deutsche Telekom"
│ ├── bookmarks.json // Bookmarks..
│ └── preferences.json // ... and preferences just for users of a SIM card of "Deutsche Telekom"
└── default // Default folder
└── preferences.json // Preferences for all users with different SIM cards.

== Partner Content Providers ==

Android system images can ship with two content providers to customize installed browsers:
* content://com.android.partnerbookmarks - For partner bookmarks
* content://com.android.partnerbrowsercustomizations - For customizations (Details see below)

Firefox for Android supports reading data from both of those content providers (Starting with Firefox for Android 50.0) if this has been enabled by a distribution. If the following preferences are not written by a distribution then Firefox for Android will ignore the data from the partner content providers.

''/distribution/preferences.json:''
<pre>
[..]
"AndroidPreferences": {
"distribution.read_partner_bookmarks_provider": true,
"distribution.read_partner_customizations_provider": true
}
[..]
</pre>

=== Bookmarks Content Provider ===

Firefox for Android (>= 50.0) supports reading bookmarks and folders from the content provider. Reading icons from the content provider is currently not supported (See {{bug|1286203}}). Editing and deleting bookmarks/folders is not supported yet but planned.

An example implementation of the content provider can be found in the official Android source tree:
* https://android.googlesource.com/platform/packages/providers/PartnerBookmarksProvider/+/master/src/com/android/providers/partnerbookmarks/PartnerBookmarksProvider.java

=== Customizations Content Provider ===

Firefox for Android (>= 50.0) only supports reading the 'homepage' from the content provider. All other values are ignored.

content://com.android.partnerbrowsercustomizations

{| class="wikitable"
|-
! Path !! Column !! Supported
|-
| /homepage || homepage || Yes
|-
| /disableincognitomode || disableincognitomode || No
|-
| /disablebookmarksediting || disablebookmarksediting || No
|}

=== Testing ===

There's a test app with sample data available on GitHub:
* https://github.com/pocmo/BrowserPartner

The test app uses slightly different content provider authorities to allow being installed on devices that already ship with partner content providers:

* com.android.partnerbookmarks.'''''test'''''
* com.android.partnerbrowsercustomizations.'''''test'''''

A custom Firefox build is required to read from the test content providers.

Add-ons/Extension Signing

2016-08-04T15:07:06Z

MikeKaply: Fixing links to release builds

Mozilla now requires all extensions to be signed by Mozilla in order for them to be installable in Release and Beta versions of Firefox. Signing will be done through [http://addons.mozilla.org/ addons.mozilla.org (AMO)] and will be mandatory for all extensions, regardless of where they are hosted.

== Documentation ==
* [http://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/ Introducing Extension Signing], Add-ons Blog.
* [https://blog.mozilla.org/addons/2015/04/15/the-case-for-extension-signing/ The Case for Extension Signing], Add-ons Blog.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=signed-addons Main tracking bug].

== Timeline ==
Check the [[RapidRelease/Calendar|Firefox Release Calendar]] for specific dates. The following timelines are for Desktop:

* '''Firefox 40-42''': Firefox warns about signatures but doesn't enforce them.
* '''Firefox 43''': Firefox enforces the use of signatures by default, but has a preference that allows signature enforcement to be disabled (''xpinstall.signatures.required'' in about:config).
* '''Firefox 48''': (Pushed from Firefox 46). Release and Beta versions of Firefox for Desktop will not allow unsigned extensions to be installed, with no override. Firefox for Android will enforce add-on signing, and will retain a preference — which will be removed in a future release — to allow the user to disable signing enforcement.

The first ESR version to include signing support will be the Firefox ESR 52 release.

All Firefox extensions - for Desktop and Android - on AMO that have passed review are now signed.

For unlisted (non-AMO) add-ons, submission and signing is active through [https://addons.mozilla.org AMO], and there is a [https://blog.mozilla.org/addons/2015/11/20/signing-api-now-available/ Signing API available] for automated submission and retrieval of unlisted addons.

== Unbranded Builds ==

Unbranded builds are available from the continuous integration builds on archive.mozilla.org. Links to the latest beta and release builds, as well as the root directories for those treeherder builds are below, and subdirectories are named from the epoch timestamp of when the build was generated.

=== Latest Builds ===

'''Release builds'''

Latest release (Firefox 48) builds:

* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/1469543944/firefox-48.0.en-US.linux-x86_64-add-on-devel.tar.bz2 Linux Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/1469543944/ build directory])
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/1469543944/firefox-48.0.en-US.mac64-add-on-devel.dmg Mac OSX Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/1469543944/ build directory])
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/1469543944/firefox-48.0.en-US.win32-add-on-devel.installer.exe Windows 32-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/1469543944/ build directory)]
*[http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/1469543944/firefox-48.0.en-US.win64-add-on-devel.installer.exe Windows 64-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/1469543944/ build directory])

'''Beta builds'''

Latest beta (48b10) builds:
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/1469251868/firefox-48.0.en-US.linux-x86_64-add-on-devel.tar.bz2 Linux Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/1469251868/ build directory])
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/1469251868/firefox-48.0.en-US.mac64-add-on-devel.dmg Mac OSX Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/1469251868/ build directory])
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/1469251868/firefox-48.0.en-US.win32-add-on-devel.installer.exe Windows 32-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/1469251868/ build directory)]
*[http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/1469251868/firefox-48.0.en-US.win64-add-on-devel.installer.exe Windows 64-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/1469251868/ build directory])

=== Treeherder Root Directories ===

'''Release'''

* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/ Linux]
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/ Mac OSX]
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/ Windows 32-bit]
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/ Windows 64-bit]

'''Beta'''

* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/ Linux]
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/ OSX]
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/ Windows 32-bit]
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/ Windows 64-bit]

== FAQ ==
* Which add-on types will need to be signed?
** Only extensions ([https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#type type 2] in install.rdf). Themes, dictionaries, language packs, and plugins don't need to be signed.

* Will other applications like Thunderbird, Seamonkey, Palemoon, etc. require extensions to be signed?
** The leaders of each of those projects will decide if they want to enforce signing, keep it as a setting, or deactivate it by default. We haven't heard about any other applications planning to support this.

* Will signed extensions work on other applications or older versions of Firefox?
** Yes, the signature system is built on top of the [https://developer.mozilla.org/en-US/docs/Signing_a_XPI existing add-on signing feature], which has been supported in Firefox and other applications.

* Will there be a setting or other overrides to disable signature checks?
** Firefox Release and Beta versions will not have any way to disable signature checks. Signature checks can be disabled in other versions, as described in detail below.

* What are my options if I want to install unsigned extensions in Firefox?
** The [https://www.mozilla.org/firefox/developer/ Developer Edition] and [https://nightly.mozilla.org/ Nightly] versions of Firefox will have a setting to disable signature enforcement. There are also be special [https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds unbranded versions of Release and Beta] that will have this setting (see , so that add-on developers can work on their add-ons without having to sign every build. To disable signature checks, you will need to set the <code>xpinstall.signatures.required</code> preference to "false".
*** type <code>about:config</code> into the URL bar in Firefox
*** in the Search box type <code>xpinstall.signatures.required</code>
*** double-click the preference, or right-click and selected "Toggle", to set it to <code>false</code>.

* How will the [[Add-ons/Extension_Signing#Unbranded_Builds|unbranded versions of Firefox]] work?
** They work just like Firefox, with two differences: they will have a setting to disable mandatory signature checks, and they will not have the Firefox name and logo (instead using a generic name and logo). These builds are available in the en-US locale only.

* What about private add-ons used in enterprise environments?
** The ESR release will support signing starting with version 45-based releases. Signing enforcement will be enabled by default in these releases, and enforcement can be disabled using the <code>xpinstall.signatures.required</code> preference.

* How do I get my add-ons signed if they are hosted on addons.mozilla.org (AMO)?
** No action is required. We automatically signed reviewed versions of all add-ons currently hosted on AMO. All new versions will be signed automatically after they pass review.

* How do I get my add-ons signed if they are not hosted on addons.mozilla.org (AMO)?
** You will need to create an AMO account and submit your add-on. There will be an option where you indicate the add-on won't be listed on AMO, and you'll be able to submit your add-on files without having them published on the site. Please read the [https://developer.mozilla.org/en-US/Add-ons/Distribution Distribution Policy] for more details.
** You can also use the [https://developer.mozilla.org/en-US/Add-ons/SDK/Tools/jpm#jpm_sign jpm sign] command to generate a signed XPI that can be self-hosted.
** There is an [http://olympia.readthedocs.org/en/latest/topics/api/signing.html API you can use] for signing.

* How does the signing process work for unlisted add-ons?
** For unlisted add-ons, files submitted for signing will go through an automated review process. If they pass this review, they are automatically signed and a download link is sent back to the developer. This process should normally take seconds. If the file doesn't pass review, the developer will have the option to request a manual review, which should take less than two days. This is not the same process that currently applies to AMO add-ons, which has been typically slower.
** There is an [http://olympia.readthedocs.org/en/latest/topics/api/signing.html API you can use] for signing.

* What about [https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Maintenance#How_do_I_submit_a_Beta_add-on.3F Beta versions on AMO]? Will they be reviewed and signed?
** Yes. Beta versions will be treated like non-AMO add-ons. They will be automatically validated and signed if they pass validation.

* Will I need to sign the custom version of an existing add-on I created with my own code changes, locale additions, etc.?
** If you use it on Release or Beta, yes. You will also need to change the add-on ID in order to submit it for signing.

* Is this a way for Mozilla to censor add-ons they don't like, enforce copyright, government demands, etc.?
** No, the purpose of this is to protect users from malicious add-ons. We have [https://developer.mozilla.org/en-US/Add-ons/Add-on_guidelines clear guidelines] for when it is appropriate to blocklist an add-on and have refused multiple times to block for other reasons.

* Will there be an upload and signing API so I don't have to manually upload each new version of the add-on?
** Yes. The [http://olympia.readthedocs.org/en/latest/topics/api/signing.html signing API is documented here].

* Will this protect users against all forms of add-on malware?
** No, there is no perfect solution for this. Fighting malware requires defenses on many levels: operating system,, application, user, and even industry. Extension signing is a big step in protecting Firefox against malicious add-ons, but there is much more to do in other fronts to ensure the best experience for our users.

== Further discussion ==
The main discussion channel is the [https://groups.google.com/forum/#!forum/mozilla.addons.user-experience mozilla.addons.user-experience] newsgroup.

Distribution INI File

2016-02-23T15:35:15Z

MikeKaply: Remove unused _reset preference

# Partner Distribution Configuration File
# Author: Dan Mills <thunder@mozilla.com>

# id: short string unique to this distribution
# about: a short descriptive (ui-visible) string for this
# distribution
# version: version of the extra distribution pieces (not the version
# of Firefox)
# bookmarks.initialized.pref: (optional) name of a boolean pref used to determine if bookmarks should be created on startup. This option should not be used except to upgrade from previous customized distributions that did not use the distribution.ini method

[Global]
id=testpartner
version=1.0
about=Afiliado de Prueba
about.en-US=Test Partner
bookmarks.initialized.pref=cck.testpartner.initialized

# This section contains the global js prefs. You do should not list
# the localized preferences here (see below)

# Boolean preferences should be 'true' or 'false', w/o quotes. e.g.:
# my.bool.preference=true
#
# Integer preferences should be unquoted numbers. e.g.:
# my.int.preference=123
#
# String preferences should be in quotes. e.g.:
# my.string.preference="foo"

[Preferences]
mozilla.partner.id="testpartner"
app.distributor="testpartner"
app.distributor.channel=
browser.search.distributionID="com.testpartner"

# This section is used as a template for locale-specific properties
# files. They work similarly to the GlobalPrefs section, except that
# the %LOCALE% string gets substituted with the language string.
#
# This section should only be used for localized string preferences.
# Other preference types will not work.

[LocalizablePreferences]
browser.startup.homepage="http://sandmill.org/%LOCALE%/%LOCALE%/"

# This section is an example of an override for a particular locale.
# The override sections do not interpolate %LOCALE% into strings.
# Preferences set in override sections are *merged* with the
# localizable defaults. That is, if you want a pref in
# [LocalizablePreferences] to not be set in a particular locale,
# you'll need to unset it explicitly ("pref.name=" on a line of its
# own).

[LocalizablePreferences-en-US]
browser.foo="testpartner"
#browser.startup.homepage="http://cheese.com/"
#browser.startup.homepage="http://cheese.com/%LOCALE%/"

# Search Plugins

# Search plugins do no need to be listed in this ini file. Instead,
# create a directory structure like the following, and they will be
# automatically loaded:

# * distribution/
# * searchplugins/
# * common/
# * <plugin.xml>
# * <plugin.xml>
# * ...
# * locale/
# * <locale>/
# * <plugin.xml>
# * <plugin.xml>
# * ...
# * <locale>/
# * <plugin.xml>
# * <plugin.xml>
# * ...

# If a directory for the locale the browser is running in doesn't
# exist, Firefox will automatically try the 'default' locale, as defined
# by the distribution.searchplugins.defaultLocale preference.

# Bookmarks

# There are two "toplevel" sections, BookmarksToolbar and BookmarksMenu.
# These can reference other sections via the "folder" type item. These
# folder sections must be named "BookmarksFolder-<id>".

# Each section contains a list of numbered item settings, where each
# item represents a bookmark, livemark, separator, folder, or the default
# bookmarks in that container (if any). The default type is bookmark.
#
# Since Firefox 45, it's possible to set an optional keyword or favicon
# for a bookmark.

[BookmarksToolbar]
item.1.title=Queso
item.1.link=http://queso.com/
item.1.description=Quesos deliciosos!
item.1.title.en-US=Cheese
item.1.link.en-US=http://cheese.com/
item.1.description.en-US=Delicious cheeses!
item.1.title.ja-JP=チーズ
item.1.link.ja-JP=http://ja.wikipedia.org/wiki/%E3%83%81%E3%83%BC%E3%82%BA
item.1.description.ja-JP=美味しいチーズです！
item.2.type=default
item.3.type=separator
item.4.type=folder
item.4.title=Título de la Carpeta
item.4.title.en-US=Folder Title
item.4.folderId=1
item.5.title=Mozilla News
item.5.type=livemark
item.5.siteLink=http://blog.mozilla.com/
item.5.feedLink=http://blog.mozilla.com/feed/

[BookmarksMenu]
item.1.type=folder
item.1.title=Another Folder Title
item.1.folderId=2

[BookmarksFolder-1]
item.1.title=Example Bookmarklet
item.1.link=javascript: alert("hi");
item.2.title=Another Example Bookmark
item.2.link=http://example.com/foo
item.2.description=This is a sample site.
item.2.keyword=example
item.2.icon=<nowiki>http://example.org/favicon.png</nowiki>
item.2.iconData=data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAAAAAA6fptVAAAACklEQVQI12NgAAAAAgAB4iG8MwAAAABJRU5ErkJggg==

[BookmarksFolder-2]
item.1.title=Another Example Bookmarklet
item.1.link=javascript: alert("hello");

Partnering/Repacks/Script

2014-11-10T16:00:11Z

MikeKaply: Add troubleshooting info for downlevel Python

== Install ==

To use the repack script, you'll need a few things. They are:

* a Mac with OSX. Part of the repack process involves creating DMGs, and unfortunately hdiutil is OSX-only. There are alternative methods to creating DMGs, but any we've found so far have been sub-optimal. If hdiutil isn't installed on your Mac, you'll need to grab Apple's Xcode.

* [ http://www.python.org/ python 2.7.5] (needed for the subprocess module). It either needs to be the default python used on said mac, or you can run the script using "python partner-repacks.py ..."

* pkg-dmg must be in PATH. This tool can be found [http://hg.mozilla.org/mozilla-central/file/tip/build/package/mac_osx/pkg-dmg here].

* [http://www.7-zip.org/ 7-zip] (specifically 7za) must be in PATH. Can install this via port, brew or via dmg (p7zip). Using brew you can <code>brew install p7zip</code>

* [http://www.gnu.org/software/wget/ wget] must be in PATH. Again, install via port or whatever. Using brew, <code>brew install wget</code>

* upx must be in the PATH. Using brew, <code>brew install upx</code>

* A current pull of the partner repo.
** hg clone https://hg.mozilla.org/build/partner-repacks

== Building a local repack ==

cd partner-repacks/scripts
bash signing-server-setup.sh
export PYTHONPATH=$PWD/tools/lib/python
partner-repacks.py -v $VERSION -n $BUILD -d ../partners -p $PARTNERNAME \
--dmg-extract-script `pwd`/tools/release/common/unpack-diskimage.sh \
--pkg-dmg ~/moz/fx-team/build/package/mac_osx/pkg-dmg

== Example builds ==

Building a current release:

partner-repacks.py -v 33.0 -n 1 -d ../partners -p $PARTNERNAME \
--dmg-extract-script `pwd`/tools/release/common/unpack-diskimage.sh \
--pkg-dmg ~/moz/fx-team/build/package/mac_osx/pkg-dmg

Building a beta release:

partner-repacks.py -v 34.0b6 -n 1 -d ../partners -p $PARTNERNAME \
--dmg-extract-script `pwd`/tools/release/common/unpack-diskimage.sh \
--pkg-dmg ~/moz/fx-team/build/package/mac_osx/pkg-dmg \
--repo releases/mozilla-beta

== Build output ==

Your new builds will appear at <code>partner-repacks/scripts/repacked_builds/34.0b6/build1/unsigned/partner-repacks/$PARTNERNAME/</code>

== Troubleshooting ==

If you have the wrong level of python, you'll see this error:

Traceback (most recent call last):
File "./partner-repacks.py", line 10, in <module>
from util.retry import retry
ImportError: No module named util.retry

Grab the latest python from https://www.python.org/downloads/.

WeeklyUpdates/2014-05-19

2014-05-19T13:35:23Z

MikeKaply: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* Thanks to Bobby Holley [:bholley] for bringing back an important enterprise feature by fixing bug {{bug|995943 }} in time for the ESR.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
Today [https://wiki.mozilla.org/Engagement/Developer_Engagement Developer Relations] released [https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse/May2014 the latest edition] of DevPulse into the wild!

Our goal for [https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse DevPulse] is to create transparency around the various efforts at Mozilla to support mobile, web & app developers and offer specific ways for you to support these efforts. So, [https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse/May2014 check it out]!

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===

* Mozillians Town Hall (2014 Goals) '''Add Services to Product Lines''' - MTV & SF Commons + Air Mozilla https://air.mozilla.org/town-hall-2014-account-services/

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox Desktop ===
''Speaker Location:''

=== Firefox Mobile ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:'' Mountain View - Asa Dotzler

=== [https://webmaker.org/ Webmaker] ===
''Speaker Location:''

=== [https://openbadges.org/ Open Badges] ===
''Speaker Location:''

=== [https://mozillascience.org/ Mozilla Science Lab] ===
''Speaker Location:''

=== Mozilla Reps ===
''Speaker Location:''

=== Grow Mozilla ===
[https://blog.mozilla.org/community/2014/05/15/aboutmozilla-is-back/ about:Mozilla is back!] [[About_mozilla/contributions|Everyone submit their timely contribution opportunities here!]]

''Speaker Location:'' Jan Bambach, Germany, Jennie Rose Halperin, North Carolina

=== Cloud Services ===
''Speaker Location:''

=== Firefox Marketplace ===
''Speaker Location:''

=== IT ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Andreas Gal
| CTO
| Address the question - Speaking of third-party binary blobs, what is the status of Cisco's OpenH264 codec?
| San Francisco
| No
|
| https://moderator.paas.allizom.org/e/monday-internal-meeting-19-may
|-
| Denelle Dixon-Thayer
| Legal, Business Affairs, Policy
| Address the question - New revenue ideas (e.g. Directory Tiles) seem to be around Desktop/Android. What are we going to do with FxOS/Cloud Services?
| San Francisco
| No
|
| https://moderator.paas.allizom.org/e/monday-internal-meeting-19-may
|-
| Rainer Cvillink
| Video Production
| The final Australis video
| San Francisco
| No
|
| https://air.mozilla.org/australis-the-journey/
|-
| John Jensen
| Metrics
| Firefox usage
| Home space
| Yes
|
|
|-

|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where is the new person based?''
| ''What will the new person be doing?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== Marketplace & Apps ===
We have released [https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse/May2014 the latest edition] of DevPulse into the wild! It features some of the many things happening by and for developers across the Mozilla global community, and offers specific ways for you to support these efforts.

Our goal for [https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse DevPulse] is to create transparency around the various efforts at Mozilla to support mobile, web & app developers and facilitate greater collaboration.

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

==== Social Support ====