MozillaWiki - User contributions [en]

ReleaseEngineering/DisposableProjectRepositories

2025-09-11T18:30:15Z

Mardak: /* BOOKING SCHEDULE */ cypress ai prototypes

== What is a disposable project branch? ==
These are project branches that can be cloned fresh from any mozilla-central based repo with the full gamut of tests enabled. No l10n or
nightlies for now. Similar to [[ReleaseEngineering/TryServer|TryServer]] but for longer, and just for '''you'''. Unlike Try, the commit level on these branches is '''level_2 (and above) contributors only''' so please bear that in mind.

===Do you need a disposable branch?===
Ask yourself the following:

'''Does your project have an end date?'''

If your answer is '''No''' then you should follow the process at [https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning Project Branch Planning]

If your project is a temporary feature sprint that needs its own rapid test coverage but will eventually be merged into mozilla-central and no longer be on its own by all means, please go ahead and

===Book one of our fabulous "disposable" project branches===
'''''NOTE:''''' The number of disposable branches is limited by CI capacity. If there are no available branches, contact the owners of existing branches to see if you can "sub let".

* Sign up below in the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]]
* Make a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Services&component=Mercurial:%20hg.mozilla.org&short_desc=Requesting%20twig%20repo%20{booked_repo}%20be%20reset&comment=Please%20run%20the%20{script_name}%20and%20reset%20{booked_repo}%20to%20{url} request] (example: {{bug|1518167}}) to VCS to reset the repo for you. You can specify the source repository and target revision to use, or default to mozilla-central:tip. '''Ask that they run the `hgmo-reset-twig.yml` Ansible playbook found in version-control-tools to accomplish this'''.
* '''NOTE''': Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured.
* After Developer Services runs the reset, they will also notify the teams who operate the automation, so they can adjust their schedulers to recognize the reset. If you don't see the expected builds, check with the automation teams to ensure their reset occurred.
* Sit back and watch your builds and test results roll in (eg [https://treeherder.mozilla.org/#/jobs?repo=birch Birch], [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar], [https://treeherder.mozilla.org/#/jobs?repo=larch Larch], [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]).

<div id="unbook"></div>

===When you're done with one of our fabulous "disposable" project branches===

Simply clear your data (bug, contact, dates) from the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]] below. If someone is listed in the "Next in Line" column, please let them know you are done.

That's all there is to it!

== Using a custom mozconfig ==

The mozconfigs used for builds live in the same source tree as the main code, eg
* Firefox: <tt>browser/config/mozconfigs/<platform></tt>
* Mobile Native: <tt>mobile/android/config/mozconfigs/android</tt>
* Mobile XUL: <tt>mobile/xul/config/mozconfigs/android-xul</tt>

The 'nightly' file is used for optimised builds, 'debug' for debug. If you are unsure which file you need consult a build log to see which is used. You can adjust these as needed on your branch, and they will be carried over to mozilla-central when you merge back. Please take care with any mozconfig changes you merge back (eg exclude local conveniences).

==Enabling/Disabling of platforms, tests, nightly updates ==
If the specific builds/tests you want are not enabled, or if there are builds/tests which you do not need on your branch, ask RelEng to enable/disable them by filing a bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering here].

Nightly builds and updates are disabled by default but can be enabled on request.

== BOOKING SCHEDULE ==

{| class="data wikitable"
|-
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact
! Booking Dates
! Next in Line
|-
|
|
|
|
|
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=ash Ash]
| {{bug|1786042}}
| rob@thunderbird.net
| aleca, darktrojan
| 2022-08-19 - 2023-08-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cypress Cypress]
| {{bug|1988208}} ai prototypes
| elee@mozilla.com
| Mardak
| 2025-09-11 - 2026-03-30
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=elm Elm]
| {{bug|1728404}} libwebrtc update 2H2020
| na-g@nostrum.com
| chew@matrix.mozilla.org
| 2021-07-31 - 2025-12-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar]
| {{bug|1820001}} iOS prototyping
| jeevans@mozilla.com, csadilek@mozilla.com
| csadilek
| 2023-03-02 - 2024-03-31
|
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=fig Fig]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=gum Gum]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| [https://treeherder.mozilla.org/#/jobs?repo=holly Holly]
| {{bug|1599905}}
| jewilde@mozilla.com, tom@mozilla.com
| <-
| 2019-12-02 - 2020-04-02
| -
|-
| [https://treeherder.mozilla.org/#/jobs?repo=larch Larch]
| {{bug|1959717}}
| joschmidt@mozilla.com
| <-
| 2025-04-10 - 2025-09-30
| -
|-
| [https://treeherder.mozilla.org/#/jobs?repo=oak Oak]
| {{bug|1928509}} Moving application-services to mozilla-central.
| mhammond@mozilla.com
| mhammond
| 2024-11-01 - 2025-03-31
| -
|}

Be sure to keep a copy of anything you need from the repo prior to [[#unbook|unbooking]] it.

== Indefinite booking ==
See also [[ReleaseEngineering/SpecialBranches]] for more info on these branches.

{| class="data wikitable"
|-
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact
! Booking Dates
|-
| [https://treeherder.mozilla.org/#/jobs?repo=date Date]
| disabled
| disabled
| disabled
| DO NOT USE - https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectRepositories
|-
| [https://treeherder.mozilla.org/#/jobs?repo=jamun Jamun]
| {{bug|1666242}}
| rob@thunderbird.net
| comm-central as a branch
| 2020-10-21 - ?
|-
| [https://treeherder.mozilla.org/#/jobs?repo=birch Birch]
| {{bug|1426132}}
| -
| Unused
| 2023-07-20 - indefinite
|-
| [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]
| {{bug|1397773}}
| hneiva@mozilla.com releng@mozilla.com
| MacOS Signing Changes
| 2023-07-28 - indefinite
|-
| [https://treeherder.mozilla.org/#/jobs?repo=pine Pine]
| {{bug|1845368}}
| bytesized@mozilla.com
| Desktop Integrations Team
| 2023-07-27 - indefinite
| -
|}

ReleaseEngineering/DisposableProjectRepositories

2025-04-10T13:15:55Z

Mardak: /* BOOKING SCHEDULE */ sidebar/ai done with larch

== What is a disposable project branch? ==
These are project branches that can be cloned fresh from any mozilla-central based repo with the full gamut of tests enabled. No l10n or
nightlies for now. Similar to [[ReleaseEngineering/TryServer|TryServer]] but for longer, and just for '''you'''. Unlike Try, the commit level on these branches is '''level_2 (and above) contributors only''' so please bear that in mind.

===Do you need a disposable branch?===
Ask yourself the following:

'''Does your project have an end date?'''

If your answer is '''No''' then you should follow the process at [https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning Project Branch Planning]

If your project is a temporary feature sprint that needs its own rapid test coverage but will eventually be merged into mozilla-central and no longer be on its own by all means, please go ahead and

===Book one of our fabulous "disposable" project branches===
'''''NOTE:''''' The number of disposable branches is limited by CI capacity. If there are no available branches, contact the owners of existing branches to see if you can "sub let".

* Sign up below in the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]]
* Make a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Services&component=Mercurial:%20hg.mozilla.org&short_desc=Requesting%20twig%20repo%20{booked_repo}%20be%20reset&comment=Please%20run%20the%20{script_name}%20and%20reset%20{booked_repo}%20to%20{url} request] (example: {{bug|1518167}}) to VCS to reset the repo for you. You can specify the source repository and target revision to use, or default to mozilla-central:tip. '''Ask that they run the `hgmo-reset-twig.yml` Ansible playbook found in version-control-tools to accomplish this'''.
* '''NOTE''': Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured.
* After Developer Services runs the reset, they will also notify the teams who operate the automation, so they can adjust their schedulers to recognize the reset. If you don't see the expected builds, check with the automation teams to ensure their reset occurred.
* Sit back and watch your builds and test results roll in (eg [https://treeherder.mozilla.org/#/jobs?repo=birch Birch], [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar], [https://treeherder.mozilla.org/#/jobs?repo=larch Larch], [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]).

<div id="unbook"></div>

===When you're done with one of our fabulous "disposable" project branches===

Simply clear your data (bug, contact, dates) from the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]] below. If someone is listed in the "Next in Line" column, please let them know you are done.

That's all there is to it!

== Using a custom mozconfig ==

The mozconfigs used for builds live in the same source tree as the main code, eg
* Firefox: <tt>browser/config/mozconfigs/<platform></tt>
* Mobile Native: <tt>mobile/android/config/mozconfigs/android</tt>
* Mobile XUL: <tt>mobile/xul/config/mozconfigs/android-xul</tt>

The 'nightly' file is used for optimised builds, 'debug' for debug. If you are unsure which file you need consult a build log to see which is used. You can adjust these as needed on your branch, and they will be carried over to mozilla-central when you merge back. Please take care with any mozconfig changes you merge back (eg exclude local conveniences).

==Enabling/Disabling of platforms, tests, nightly updates ==
If the specific builds/tests you want are not enabled, or if there are builds/tests which you do not need on your branch, ask RelEng to enable/disable them by filing a bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering here].

Nightly builds and updates are disabled by default but can be enabled on request.

== BOOKING SCHEDULE ==

{| class="data wikitable"
|-
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact
! Booking Dates
! Next in Line
|-
|
|
|
|
|
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=ash Ash]
| {{bug|1786042}}
| rob@thunderbird.net
| aleca, darktrojan
| 2022-08-19 - 2023-08-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cypress Cypress]
| {{bug|1899403}}
| mfroman@mozilla.com
| mjf@matrix.mozilla.org
| 2024-01-09 - 2025-06-30
| bowen@mozilla.com
|-
| [https://treeherder.mozilla.org/#/jobs?repo=elm Elm]
| {{bug|1728404}} libwebrtc update 2H2020
| na-g@nostrum.com
| chew@matrix.mozilla.org
| 2021-07-31 - 2025-12-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar]
| {{bug|1820001}} iOS prototyping
| jeevans@mozilla.com, csadilek@mozilla.com
| csadilek
| 2023-03-02 - 2024-03-31
|
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=fig Fig]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=gum Gum]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| [https://treeherder.mozilla.org/#/jobs?repo=holly Holly]
| {{bug|1599905}}
| jewilde@mozilla.com, tom@mozilla.com
| <-
| 2019-12-02 - 2020-04-02
| -
|-
| [https://treeherder.mozilla.org/#/jobs?repo=larch Larch]
|
|
|
|
| credential management
|-
| [https://treeherder.mozilla.org/#/jobs?repo=oak Oak]
| {{bug|1928509}} Moving application-services to mozilla-central.
| mhammond@mozilla.com
| mhammond
| 2024-11-01 - 2025-03-31
| -
|}

Be sure to keep a copy of anything you need from the repo prior to [[#unbook|unbooking]] it.

== Indefinite booking ==
See also [[ReleaseEngineering/SpecialBranches]] for more info on these branches.

{| class="data wikitable"
|-
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact
! Booking Dates
|-
| [https://treeherder.mozilla.org/#/jobs?repo=date Date]
| disabled
| disabled
| disabled
| DO NOT USE - https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectRepositories
|-
| [https://treeherder.mozilla.org/#/jobs?repo=jamun Jamun]
| {{bug|1666242}}
| rob@thunderbird.net
| comm-central as a branch
| 2020-10-21 - ?
|-
| [https://treeherder.mozilla.org/#/jobs?repo=birch Birch]
| {{bug|1426132}}
| -
| Unused
| 2023-07-20 - indefinite
|-
| [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]
| {{bug|1397773}}
| hneiva@mozilla.com releng@mozilla.com
| MacOS Signing Changes
| 2023-07-28 - indefinite
|-
| [https://treeherder.mozilla.org/#/jobs?repo=pine Pine]
| {{bug|1845368}}
| bytesized@mozilla.com
| Desktop Integrations Team
| 2023-07-27 - indefinite
| -
|}

ReleaseEngineering/DisposableProjectRepositories

2024-01-16T19:53:14Z

Mardak: /* BOOKING SCHEDULE */ larch desktop sidebar booking

== What is a disposable project branch? ==
These are project branches that can be cloned fresh from any mozilla-central based repo with the full gamut of tests enabled. No l10n or
nightlies for now. Similar to [[ReleaseEngineering/TryServer|TryServer]] but for longer, and just for '''you'''. Unlike Try, the commit level on these branches is '''level_2 (and above) contributors only''' so please bear that in mind.

===Do you need a disposable branch?===
Ask yourself the following:

'''Does your project have an end date?'''

If your answer is '''No''' then you should follow the process at [https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning Project Branch Planning]

If your project is a temporary feature sprint that needs its own rapid test coverage but will eventually be merged into mozilla-central and no longer be on its own by all means, please go ahead and

===Book one of our fabulous "disposable" project branches===
'''''NOTE:''''' The number of disposable branches is limited by CI capacity. If there are no available branches, contact the owners of existing branches to see if you can "sub let".

* Sign up below in the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]]
* Make a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Services&component=Mercurial:%20hg.mozilla.org&short_desc=Requesting%20twig%20repo%20{booked_repo}%20be%20reset&comment=Please%20run%20the%20{script_name}%20and%20reset%20{booked_repo}%20to%20{url} request] (example: {{bug|1518167}}) to VCS to reset the repo for you. You can specify the source repository and target revision to use, or default to mozilla-central:tip. '''Ask that they run the `hgmo-reset-twig.yml` Ansible playbook found in version-control-tools to accomplish this'''.
* '''NOTE''': Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured.
* After Developer Services runs the reset, they will also notify the teams who operate the automation, so they can adjust their schedulers to recognize the reset. If you don't see the expected builds, check with the automation teams to ensure their reset occurred.
* Sit back and watch your builds and test results roll in (eg [https://treeherder.mozilla.org/#/jobs?repo=birch Birch], [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar], [https://treeherder.mozilla.org/#/jobs?repo=larch Larch], [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]).

<div id="unbook"></div>

===When you're done with one of our fabulous "disposable" project branches===

Simply clear your data (bug, contact, dates) from the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]] below. If someone is listed in the "Next in Line" column, please let them know you are done.

That's all there is to it!

== Using a custom mozconfig ==

The mozconfigs used for builds live in the same source tree as the main code, eg
* Firefox: <tt>browser/config/mozconfigs/<platform></tt>
* Mobile Native: <tt>mobile/android/config/mozconfigs/android</tt>
* Mobile XUL: <tt>mobile/xul/config/mozconfigs/android-xul</tt>

The 'nightly' file is used for optimised builds, 'debug' for debug. If you are unsure which file you need consult a build log to see which is used. You can adjust these as needed on your branch, and they will be carried over to mozilla-central when you merge back. Please take care with any mozconfig changes you merge back (eg exclude local conveniences).

==Enabling/Disabling of platforms, tests, nightly updates ==
If the specific builds/tests you want are not enabled, or if there are builds/tests which you do not need on your branch, ask RelEng to enable/disable them by filing a bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering here].

Nightly builds and updates are disabled by default but can be enabled on request.

== BOOKING SCHEDULE ==

{| class="data wikitable"
|-
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact
! Booking Dates
! Next in Line
|-
|
|
|
|
|
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=ash Ash]
| {{bug|1786042}}
| rob@thunderbird.net
| aleca, darktrojan
| 2022-08-19 - 2023-08-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cypress Cypress]
| {{bug|1171698}}
| mfroman@mozilla.com
| mjf@matrix.mozilla.org
| 2024-01-09 - 2024-12-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=elm Elm]
| {{bug|1728404}} libwebrtc update 2H2020
| na-g@nostrum.com
| chew@matrix.mozilla.org
| 2021-07-31 - 2024-12-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar]
| {{bug|1820001}} iOS prototyping
| jeevans@mozilla.com, csadilek@mozilla.com
| csadilek
| 2023-03-02 - 2024-03-31
|
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=fig Fig]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=gum Gum]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| [https://treeherder.mozilla.org/#/jobs?repo=holly Holly]
| {{bug|1599905}}
| jewilde@mozilla.com, tom@mozilla.com
| <-
| 2019-12-02 - 2020-04-02
| -
|-
| [https://treeherder.mozilla.org/#/jobs?repo=larch Larch]
| {{bug|1874491}} desktop sidebar
| elee@mozilla.com
| Mardak, tarek
| 2024-01-16 - 2025-01-16
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=oak Oak]
| {{bug|1819778}} Android Monorepo project: Prototyping move to M-C.
| csadilek@mozilla.com, jlorenzo@mozilla.com, gluong@mozilla.com
| csadilek, jlorenzo, gl
| 2023-03-02 - 2023-12-31
| -
|}

Be sure to keep a copy of anything you need from the repo prior to [[#unbook|unbooking]] it.

== Indefinite booking ==
See also [[ReleaseEngineering/SpecialBranches]] for more info on these branches.

{| class="data wikitable"
|-
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact
! Booking Dates
|-
| [https://treeherder.mozilla.org/#/jobs?repo=date Date]
| disabled
| disabled
| disabled
| DO NOT USE - https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectRepositories
|-
| [https://treeherder.mozilla.org/#/jobs?repo=jamun Jamun]
| {{bug|1666242}}
| rob@thunderbird.net
| comm-central as a branch
| 2020-10-21 - ?
|-
| [https://treeherder.mozilla.org/#/jobs?repo=birch Birch]
| {{bug|1426132}}
| -
| Unused
| 2023-07-20 - indefinite
|-
| [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]
| {{bug|1397773}}
| hneiva@mozilla.com releng@mozilla.com
| MacOS Signing Changes
| 2023-07-28 - indefinite
|-
| [https://treeherder.mozilla.org/#/jobs?repo=pine Pine]
| {{bug|1845368}}
| bytesized@mozilla.com
| Desktop Integrations Team
| 2023-07-27 - indefinite
| -
|}

ReleaseEngineering/DisposableProjectRepositories

2024-01-12T21:21:25Z

Mardak: /* BOOKING SCHEDULE */ desktop sidebar

== What is a disposable project branch? ==
These are project branches that can be cloned fresh from any mozilla-central based repo with the full gamut of tests enabled. No l10n or
nightlies for now. Similar to [[ReleaseEngineering/TryServer|TryServer]] but for longer, and just for '''you'''. Unlike Try, the commit level on these branches is '''level_2 (and above) contributors only''' so please bear that in mind.

===Do you need a disposable branch?===
Ask yourself the following:

'''Does your project have an end date?'''

If your answer is '''No''' then you should follow the process at [https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning Project Branch Planning]

If your project is a temporary feature sprint that needs its own rapid test coverage but will eventually be merged into mozilla-central and no longer be on its own by all means, please go ahead and

===Book one of our fabulous "disposable" project branches===
'''''NOTE:''''' The number of disposable branches is limited by CI capacity. If there are no available branches, contact the owners of existing branches to see if you can "sub let".

* Sign up below in the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]]
* Make a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Services&component=Mercurial:%20hg.mozilla.org&short_desc=Requesting%20twig%20repo%20{booked_repo}%20be%20reset&comment=Please%20run%20the%20{script_name}%20and%20reset%20{booked_repo}%20to%20{url} request] (example: {{bug|1518167}}) to VCS to reset the repo for you. You can specify the source repository and target revision to use, or default to mozilla-central:tip. '''Ask that they run the `hgmo-reset-twig.yml` Ansible playbook found in version-control-tools to accomplish this'''.
* '''NOTE''': Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured.
* After Developer Services runs the reset, they will also notify the teams who operate the automation, so they can adjust their schedulers to recognize the reset. If you don't see the expected builds, check with the automation teams to ensure their reset occurred.
* Sit back and watch your builds and test results roll in (eg [https://treeherder.mozilla.org/#/jobs?repo=birch Birch], [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar], [https://treeherder.mozilla.org/#/jobs?repo=larch Larch], [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]).

<div id="unbook"></div>

===When you're done with one of our fabulous "disposable" project branches===

Simply clear your data (bug, contact, dates) from the [[#BOOKING_SCHEDULE|BOOKING SCHEDULE]] below. If someone is listed in the "Next in Line" column, please let them know you are done.

That's all there is to it!

== Using a custom mozconfig ==

The mozconfigs used for builds live in the same source tree as the main code, eg
* Firefox: <tt>browser/config/mozconfigs/<platform></tt>
* Mobile Native: <tt>mobile/android/config/mozconfigs/android</tt>
* Mobile XUL: <tt>mobile/xul/config/mozconfigs/android-xul</tt>

The 'nightly' file is used for optimised builds, 'debug' for debug. If you are unsure which file you need consult a build log to see which is used. You can adjust these as needed on your branch, and they will be carried over to mozilla-central when you merge back. Please take care with any mozconfig changes you merge back (eg exclude local conveniences).

==Enabling/Disabling of platforms, tests, nightly updates ==
If the specific builds/tests you want are not enabled, or if there are builds/tests which you do not need on your branch, ask RelEng to enable/disable them by filing a bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering here].

Nightly builds and updates are disabled by default but can be enabled on request.

== BOOKING SCHEDULE ==

{| class="data wikitable"
|-
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact
! Booking Dates
! Next in Line
|-
|
|
|
|
|
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=ash Ash]
| {{bug|1786042}}
| rob@thunderbird.net
| aleca, darktrojan
| 2022-08-19 - 2023-08-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cypress Cypress]
| {{bug|1171698}}
| mfroman@mozilla.com
| mjf@matrix.mozilla.org
| 2024-01-09 - 2024-12-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=elm Elm]
| {{bug|1728404}} libwebrtc update 2H2020
| na-g@nostrum.com
| chew@matrix.mozilla.org
| 2021-07-31 - 2024-12-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar]
| {{bug|1820001}} iOS prototyping
| jeevans@mozilla.com, csadilek@mozilla.com
| csadilek
| 2023-03-02 - 2024-03-31
|
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=fig Fig]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=gum Gum]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| [https://treeherder.mozilla.org/#/jobs?repo=holly Holly]
| {{bug|1599905}}
| jewilde@mozilla.com, tom@mozilla.com
| <-
| 2019-12-02 - 2020-04-02
| -
|-
| [https://treeherder.mozilla.org/#/jobs?repo=larch Larch]
| {{bug|1322426}} socket process isolation
| hbambas@mozilla.com
| necko, :mayhemer
| 2018-08-20 - 2020-08-20
| {{bug|1874491}} desktop sidebar elee@mozilla.com
|-
| [https://treeherder.mozilla.org/#/jobs?repo=oak Oak]
| {{bug|1819778}} Android Monorepo project: Prototyping move to M-C.
| csadilek@mozilla.com, jlorenzo@mozilla.com, gluong@mozilla.com
| csadilek, jlorenzo, gl
| 2023-03-02 - 2023-12-31
| -
|}

Be sure to keep a copy of anything you need from the repo prior to [[#unbook|unbooking]] it.

== Indefinite booking ==
See also [[ReleaseEngineering/SpecialBranches]] for more info on these branches.

{| class="data wikitable"
|-
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact
! Booking Dates
|-
| [https://treeherder.mozilla.org/#/jobs?repo=date Date]
| disabled
| disabled
| disabled
| DO NOT USE - https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectRepositories
|-
| [https://treeherder.mozilla.org/#/jobs?repo=jamun Jamun]
| {{bug|1666242}}
| rob@thunderbird.net
| comm-central as a branch
| 2020-10-21 - ?
|-
| [https://treeherder.mozilla.org/#/jobs?repo=birch Birch]
| {{bug|1426132}}
| -
| Unused
| 2023-07-20 - indefinite
|-
| [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]
| {{bug|1397773}}
| hneiva@mozilla.com releng@mozilla.com
| MacOS Signing Changes
| 2023-07-28 - indefinite
|-
| [https://treeherder.mozilla.org/#/jobs?repo=pine Pine]
| {{bug|1845368}}
| bytesized@mozilla.com
| Desktop Integrations Team
| 2023-07-27 - indefinite
| -
|}

Modules/Desktop Firefox

2020-07-10T15:06:15Z

Mardak: /* Submodules */ add andreio as new tab page peer

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
Owners and peers of the Desktop Firefox module may review code anywhere in the browser and toolkit directories. Reviews should be sent to the more specific submodules below where possible.

{{Module
|name=Desktop Firefox
|description=Standalone Web Browser.
|owner=[mailto:dtownsend@mozilla.com Dave Townsend], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|fallbackpeers=[mailto:dao@mozilla.com Dão Gottwald], [mailto:jwein@mozilla.com Jared Wein], [mailto:jhofmann@mozilla.com Johann Hofmann], [mailto:lina@mozilla.com Lina Cambridge], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:MattN@mozilla.com Matthew Noorenberghe]
|ownersemeritus=
|peersemeritus=[mailto:netzen@gmail.com Brian Bondy], [mailto:lchang@mozilla.com Luke Chang], [mailto:rchien@mozilla.com Ricky Chien], [mailto:dolske@mozilla.com Justin Dolske], [mailto:georg.fritzsche@googlemail.com Georg Fritzsche], [mailto:felipc@gmail.com Felipe Gomes], [mailto:tchien@mozilla.com Tim Guan-tin Chien], [mailto:rexboy@mozilla.com KM Lee Rex], [mailto:gasolin@mozilla.com Fred Lin], [mailto:ralin@mozilla.com Ray Lin], [mailto:fliu@mozilla.com Fischer Liu], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:mark@moxienet.com Mark Mentovai], [mailto:ted.mielczarek@gmail.com Ted Mielczarek], [mailto:bnicholson@mozilla.com Brian Nicholson], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:mano@mozilla.com Asaf Romano], [mailto:msamuel@mozilla.com Marina Samuel], [mailto:jryans@gmail.com J Ryan Stinnett], [mailto:gps@mozilla.com Gregory Szorc], [mailto:ttaubert@mozilla.com Tim Taubert]
|group=firefox-dev
|source_dirs=browser/, toolkit/
|url=[[Firefox/Code_Review|Code Review Guidelines]]
|components=Firefox, Toolkit
}}

== Submodules ==

{{Module
|name=Add-ons Manager
|description=Extension management back-end.
|owner=[mailto:aswan@mozilla.com Andrew Swan], [mailto:kmaglione@mozilla.com Kris Maglione]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:jmathies@mozilla.com Jim Mathies], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/
|url=
|components=
}}

{{Module
|name=Add-ons Manager UI
|description=about:addons.
|owner=[mailto:aswan@mozilla.com Andrew Swan], [mailto:mstriemer@mozilla.com Mark Striemer]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/content/
|url=
|components=
}}

{{Module
|name=Application Update
|description=The application update services.
|owner=[mailto:mhowell@mozilla.com Molly Howell], [mailto:ksteuber@mozilla.com Kirk Steuber]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin]
|source_dirs=toolkit/mozapps/update/
|url=
|components=
}}

{{Module
|name=Bookmarks & History
|description=The bookmarks and history services (Places).
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:lina@mozilla.com Lina Cambridge], [mailto:standard8@mozilla.com Mark Banner], [mailto:adw@mozilla.com Drew Willcoxon]
|source_dirs=browser/components/places/, toolkit/components/places/
|url=
|components=
}}

{{Module
|name=Desktop Theme
|description=The style rules used in the desktop UI.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/themes/, toolkit/themes/
|url=
|components=Firefox::Theme, Toolkit::Themes
}}

{{Module
|name=Desktop UI
|description=The main browser UI except where covered by more specific submodules.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mconley@mozilla.com Mike Conley], [mailto:florian@queze.net Florian Quèze]
|source_dirs=browser/base/content/
|url=
|components=
}}

{{Module
|name=Download Manager
|description=The downloads UI and service.
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch]
|source_dirs=browser/components/downloads/, toolkit/mozapps/downloads/
|url=
|components=
}}

{{Module
|name=Enterprise Policies
|description=System policies for controlling Firefox.
|owner=[mailto:mkaply@mozilla.com Michael Kaply]
|peers=
|source_dirs=browser/components/enterprisepolicies/
|url=
|components=
}}

{{Module
|name=Form Autofill
|description=Form detection and autocomplete.
|owner=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|peers=
|source_dirs=browser/extensions/formautofill/, toolkit/components/satchel/
|url=
|components=
}}

{{Module
|name=In-product Messaging
|description=The system for delivering in-product messaging.
|owner=[mailto:khudson@mozilla.com Kate Hudson]
|peers=
|source_dirs=toolkit/components/messaging-system/
|url=
|components=Firefox::Messaging System
}}

{{Module
|name=Launcher Process
|description=Windows process for bootstrapping the browser process.
|owner=[mailto:aklotz@mozilla.com Aaron Klotz]
|peers=[mailto:mhowell@mozilla.com Molly Howell]
|source_dirs=browser/app/winlauncher
|url=
|components=Firefox::Launcher Process
}}

{{Module
|name=New Tab Page
|description=The new tab/home page.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:khudson@mozilla.com Kate Hudson], [mailto:aoprea@mozilla.com Andrei Oprea], [mailto:sdowne@getpocket.com Scott Downe]
|source_dirs=browser/components/newtab/
|url=
|components=Firefox::New Tab Page
}}

{{Module
|name=Normandy
|description=The experiments and off-train deployments system.
|owner=[mailto:mcooper@mozilla.com Michael Cooper]
|peers=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=toolkit/components/normandy/
|url=
|components=Firefox::Normandy
}}

{{Module
|name=Onboarding
|description=The onboarding experience including UI tours.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|source_dirs=browser/components/uitour/
|url=
|components=Firefox::Tours
}}

{{Module
|name=Password Manager
|description=Managing, saving and filling logins.
|owner=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|peers=[mailto:jwein@mozilla.com Jared Wein], [mailto:sfoster@mozilla.com Sam Foster]
|source_dirs=toolkit/components/passwordmgr/, browser/components/aboutlogins
|url=https://wiki.mozilla.org/Toolkit:Password_Manager
|components=Toolkit::Password Manager, Toolkit::Password Manager: Site Compatibility, Firefox::about:logins
}}

{{Module
|name=Preferences
|description=The front-end preferences system.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mstriemer@mozilla.com Mark Striemer], [mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=browser/components/preferences/, browser/themes/*/preferences, toolkit/mozapps/preferences
|url=
|components=
}}

{{Module
|name=Profile Migration
|description=Migrating data from other browsers.
|owner=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peers=[mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:MattN@mozilla.com Matthew Noorenberghe]
|source_dirs=browser/components/migration/
|url=
|components=
}}

{{Module
|name=Search and Address Bar
|description=The search service, address bar and address bar autocomplete.
|owner=[mailto:standard8@mozilla.com Mark Banner], [mailto:dwillcoxon@mozilla.com Drew Willcoxon]
|peers=[mailto:dharvey@mozilla.com Dale Harvey], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:dao@mozilla.com Dão Gottwald], [mailto:mdeboer@mozilla.com Mike de Boer]
|source_dirs=browser/components/search/, browser/components/urlbar/, toolkit/components/search/
|url=
|components=Firefox::Address Bar, Firefox::Search
}}

{{Module
|name=Security and Privacy UI
|description=The front-end to our security and privacy features, including Protections UI, Site Identity, Site Permissions and Certificate Errors
|owner=[mailto:jhofmann@mozilla.com Johann Hofmann]
|peers=[mailto:nhnt11@mozilla.com Nihanth Subramanya], [mailto:ewright@mozilla.com Erica Wright], [mailto:pbz@mozilla.com Paul Zühlcke], [mailto:prathiksha@mozilla.com Prathiksha]
|source_dirs=browser/components/protections/, browser/components/controlcenter/
|url=
|components=Firefox::Security, Firefox::Protections UI, Firefox::Site Identity, Firefox::Site Permissions
}}

{{Module
|name=Session Restore
|description=Restoring a user's session after starting Firefox.
|owner=[mailto:mdeboer@mozilla.com Michael de Boer]
|peers=
|source_dirs=browser/components/sessionstore/, toolkit/components/sessionstore/
|url=
|components=
}}

{{Module
|name=Tabbed Browser
|description=The UI component controlling browser tabs.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=
|source_dirs=browser/base/content/tabbrowser*, browser/modules/AsyncTabSwitcher.jsm
|url=
|components=Firefox::Tabbed Browser
}}

{{Module
|name=Windows Installer
|description=The installer for Windows.
|owner=[mailto:mhowell@mozilla.com Molly Howell]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin], [mailto:nalexander@mozilla.com Nick Alexander]
|source_dirs=browser/installer/, toolkit/mozapps/installer/
|url=
|components=Firefox::Installer
}}

Modules/Desktop Firefox

2020-07-09T22:25:26Z

Mardak: /* Submodules */ update onboarding/uitour

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
Owners and peers of the Desktop Firefox module may review code anywhere in the browser and toolkit directories. Reviews should be sent to the more specific submodules below where possible.

{{Module
|name=Desktop Firefox
|description=Standalone Web Browser.
|owner=[mailto:dtownsend@mozilla.com Dave Townsend], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|fallbackpeers=[mailto:dao@mozilla.com Dão Gottwald], [mailto:jwein@mozilla.com Jared Wein], [mailto:jhofmann@mozilla.com Johann Hofmann], [mailto:lina@mozilla.com Lina Cambridge], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:MattN@mozilla.com Matthew Noorenberghe]
|ownersemeritus=
|peersemeritus=[mailto:netzen@gmail.com Brian Bondy], [mailto:lchang@mozilla.com Luke Chang], [mailto:rchien@mozilla.com Ricky Chien], [mailto:dolske@mozilla.com Justin Dolske], [mailto:georg.fritzsche@googlemail.com Georg Fritzsche], [mailto:felipc@gmail.com Felipe Gomes], [mailto:tchien@mozilla.com Tim Guan-tin Chien], [mailto:rexboy@mozilla.com KM Lee Rex], [mailto:gasolin@mozilla.com Fred Lin], [mailto:ralin@mozilla.com Ray Lin], [mailto:fliu@mozilla.com Fischer Liu], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:mark@moxienet.com Mark Mentovai], [mailto:ted.mielczarek@gmail.com Ted Mielczarek], [mailto:bnicholson@mozilla.com Brian Nicholson], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:mano@mozilla.com Asaf Romano], [mailto:msamuel@mozilla.com Marina Samuel], [mailto:jryans@gmail.com J Ryan Stinnett], [mailto:gps@mozilla.com Gregory Szorc], [mailto:ttaubert@mozilla.com Tim Taubert]
|group=firefox-dev
|source_dirs=browser/, toolkit/
|url=[[Firefox/Code_Review|Code Review Guidelines]]
|components=Firefox, Toolkit
}}

== Submodules ==

{{Module
|name=Add-ons Manager
|description=Extension management back-end.
|owner=[mailto:aswan@mozilla.com Andrew Swan], [mailto:kmaglione@mozilla.com Kris Maglione]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:jmathies@mozilla.com Jim Mathies], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/
|url=
|components=
}}

{{Module
|name=Add-ons Manager UI
|description=about:addons.
|owner=[mailto:aswan@mozilla.com Andrew Swan], [mailto:mstriemer@mozilla.com Mark Striemer]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/content/
|url=
|components=
}}

{{Module
|name=Application Update
|description=The application update services.
|owner=[mailto:mhowell@mozilla.com Molly Howell], [mailto:ksteuber@mozilla.com Kirk Steuber]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin]
|source_dirs=toolkit/mozapps/update/
|url=
|components=
}}

{{Module
|name=Bookmarks & History
|description=The bookmarks and history services (Places).
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:lina@mozilla.com Lina Cambridge], [mailto:standard8@mozilla.com Mark Banner], [mailto:adw@mozilla.com Drew Willcoxon]
|source_dirs=browser/components/places/, toolkit/components/places/
|url=
|components=
}}

{{Module
|name=Desktop Theme
|description=The style rules used in the desktop UI.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/themes/, toolkit/themes/
|url=
|components=Firefox::Theme, Toolkit::Themes
}}

{{Module
|name=Desktop UI
|description=The main browser UI except where covered by more specific submodules.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mconley@mozilla.com Mike Conley], [mailto:florian@queze.net Florian Quèze]
|source_dirs=browser/base/content/
|url=
|components=
}}

{{Module
|name=Download Manager
|description=The downloads UI and service.
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch]
|source_dirs=browser/components/downloads/, toolkit/mozapps/downloads/
|url=
|components=
}}

{{Module
|name=Enterprise Policies
|description=System policies for controlling Firefox.
|owner=[mailto:mkaply@mozilla.com Michael Kaply]
|peers=
|source_dirs=browser/components/enterprisepolicies/
|url=
|components=
}}

{{Module
|name=Form Autofill
|description=Form detection and autocomplete.
|owner=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|peers=
|source_dirs=browser/extensions/formautofill/, toolkit/components/satchel/
|url=
|components=
}}

{{Module
|name=In-product Messaging
|description=The system for delivering in-product messaging.
|owner=[mailto:khudson@mozilla.com Kate Hudson]
|peers=
|source_dirs=toolkit/components/messaging-system/
|url=
|components=Firefox::Messaging System
}}

{{Module
|name=Launcher Process
|description=Windows process for bootstrapping the browser process.
|owner=[mailto:aklotz@mozilla.com Aaron Klotz]
|peers=[mailto:mhowell@mozilla.com Molly Howell]
|source_dirs=browser/app/winlauncher
|url=
|components=Firefox::Launcher Process
}}

{{Module
|name=New Tab Page
|description=The new tab/home page.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:khudson@mozilla.com Kate Hudson], [mailto:sdowne@getpocket.com Scott Downe]
|source_dirs=browser/components/newtab/
|url=
|components=Firefox::New Tab Page
}}

{{Module
|name=Normandy
|description=The experiments and off-train deployments system.
|owner=[mailto:mcooper@mozilla.com Michael Cooper]
|peers=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=toolkit/components/normandy/
|url=
|components=Firefox::Normandy
}}

{{Module
|name=Onboarding
|description=The onboarding experience including UI tours.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|source_dirs=browser/components/uitour/
|url=
|components=Firefox::Tours
}}

{{Module
|name=Password Manager
|description=Managing, saving and filling logins.
|owner=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|peers=[mailto:jwein@mozilla.com Jared Wein], [mailto:sfoster@mozilla.com Sam Foster]
|source_dirs=toolkit/components/passwordmgr/, browser/components/aboutlogins
|url=https://wiki.mozilla.org/Toolkit:Password_Manager
|components=Toolkit::Password Manager, Toolkit::Password Manager: Site Compatibility, Firefox::about:logins
}}

{{Module
|name=Preferences
|description=The front-end preferences system.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mstriemer@mozilla.com Mark Striemer], [mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=browser/components/preferences/, browser/themes/*/preferences, toolkit/mozapps/preferences
|url=
|components=
}}

{{Module
|name=Profile Migration
|description=Migrating data from other browsers.
|owner=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peers=[mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:MattN@mozilla.com Matthew Noorenberghe]
|source_dirs=browser/components/migration/
|url=
|components=
}}

{{Module
|name=Search and Address Bar
|description=The search service, address bar and address bar autocomplete.
|owner=[mailto:standard8@mozilla.com Mark Banner], [mailto:dwillcoxon@mozilla.com Drew Willcoxon]
|peers=[mailto:dharvey@mozilla.com Dale Harvey], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:dao@mozilla.com Dão Gottwald], [mailto:mdeboer@mozilla.com Mike de Boer]
|source_dirs=browser/components/search/, browser/components/urlbar/, toolkit/components/search/
|url=
|components=Firefox::Address Bar, Firefox::Search
}}

{{Module
|name=Security and Privacy UI
|description=The front-end to our security and privacy features, including Protections UI, Site Identity, Site Permissions and Certificate Errors
|owner=[mailto:jhofmann@mozilla.com Johann Hofmann]
|peers=[mailto:nhnt11@mozilla.com Nihanth Subramanya], [mailto:ewright@mozilla.com Erica Wright], [mailto:pbz@mozilla.com Paul Zühlcke], [mailto:prathiksha@mozilla.com Prathiksha]
|source_dirs=browser/components/protections/, browser/components/controlcenter/
|url=
|components=Firefox::Security, Firefox::Protections UI, Firefox::Site Identity, Firefox::Site Permissions
}}

{{Module
|name=Session Restore
|description=Restoring a user's session after starting Firefox.
|owner=[mailto:mdeboer@mozilla.com Michael de Boer]
|peers=
|source_dirs=browser/components/sessionstore/, toolkit/components/sessionstore/
|url=
|components=
}}

{{Module
|name=Tabbed Browser
|description=The UI component controlling browser tabs.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=
|source_dirs=browser/base/content/tabbrowser*, browser/modules/AsyncTabSwitcher.jsm
|url=
|components=Firefox::Tabbed Browser
}}

{{Module
|name=Windows Installer
|description=The installer for Windows.
|owner=[mailto:mhowell@mozilla.com Molly Howell]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin], [mailto:nalexander@mozilla.com Nick Alexander]
|source_dirs=browser/installer/, toolkit/mozapps/installer/
|url=
|components=Firefox::Installer
}}

Modules/Desktop Firefox

2020-07-09T18:48:50Z

Mardak: /* Submodules */ add messaging system source and component

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
Owners and peers of the Desktop Firefox module may review code anywhere in the browser and toolkit directories. Reviews should be sent to the more specific submodules below where possible.

{{Module
|name=Desktop Firefox
|description=Standalone Web Browser.
|owner=[mailto:dtownsend@mozilla.com Dave Townsend], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|fallbackpeers=[mailto:dao@mozilla.com Dão Gottwald], [mailto:jwein@mozilla.com Jared Wein], [mailto:jhofmann@mozilla.com Johann Hofmann], [mailto:lina@mozilla.com Lina Cambridge], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:MattN@mozilla.com Matthew Noorenberghe]
|ownersemeritus=
|peersemeritus=[mailto:netzen@gmail.com Brian Bondy], [mailto:lchang@mozilla.com Luke Chang], [mailto:rchien@mozilla.com Ricky Chien], [mailto:dolske@mozilla.com Justin Dolske], [mailto:georg.fritzsche@googlemail.com Georg Fritzsche], [mailto:felipc@gmail.com Felipe Gomes], [mailto:tchien@mozilla.com Tim Guan-tin Chien], [mailto:rexboy@mozilla.com KM Lee Rex], [mailto:gasolin@mozilla.com Fred Lin], [mailto:ralin@mozilla.com Ray Lin], [mailto:fliu@mozilla.com Fischer Liu], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:mark@moxienet.com Mark Mentovai], [mailto:ted.mielczarek@gmail.com Ted Mielczarek], [mailto:bnicholson@mozilla.com Brian Nicholson], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:mano@mozilla.com Asaf Romano], [mailto:msamuel@mozilla.com Marina Samuel], [mailto:jryans@gmail.com J Ryan Stinnett], [mailto:gps@mozilla.com Gregory Szorc], [mailto:ttaubert@mozilla.com Tim Taubert]
|group=firefox-dev
|source_dirs=browser/, toolkit/
|url=[[Firefox/Code_Review|Code Review Guidelines]]
|components=Firefox, Toolkit
}}

== Submodules ==

{{Module
|name=Add-ons Manager
|description=Extension management back-end.
|owner=[mailto:aswan@mozilla.com Andrew Swan], [mailto:kmaglione@mozilla.com Kris Maglione]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:jmathies@mozilla.com Jim Mathies], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/
|url=
|components=
}}

{{Module
|name=Add-ons Manager UI
|description=about:addons.
|owner=[mailto:aswan@mozilla.com Andrew Swan], [mailto:mstriemer@mozilla.com Mark Striemer]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/content/
|url=
|components=
}}

{{Module
|name=Application Update
|description=The application update services.
|owner=[mailto:mhowell@mozilla.com Molly Howell], [mailto:ksteuber@mozilla.com Kirk Steuber]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin]
|source_dirs=toolkit/mozapps/update/
|url=
|components=
}}

{{Module
|name=Bookmarks & History
|description=The bookmarks and history services (Places).
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:lina@mozilla.com Lina Cambridge], [mailto:standard8@mozilla.com Mark Banner], [mailto:adw@mozilla.com Drew Willcoxon]
|source_dirs=browser/components/places/, toolkit/components/places/
|url=
|components=
}}

{{Module
|name=Desktop Theme
|description=The style rules used in the desktop UI.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/themes/, toolkit/themes/
|url=
|components=Firefox::Theme, Toolkit::Themes
}}

{{Module
|name=Desktop UI
|description=The main browser UI except where covered by more specific submodules.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mconley@mozilla.com Mike Conley], [mailto:florian@queze.net Florian Quèze]
|source_dirs=browser/base/content/
|url=
|components=
}}

{{Module
|name=Download Manager
|description=The downloads UI and service.
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch]
|source_dirs=browser/components/downloads/, toolkit/mozapps/downloads/
|url=
|components=
}}

{{Module
|name=Enterprise Policies
|description=System policies for controlling Firefox.
|owner=[mailto:mkaply@mozilla.com Michael Kaply]
|peers=
|source_dirs=browser/components/enterprisepolicies/
|url=
|components=
}}

{{Module
|name=Form Autofill
|description=Form detection and autocomplete.
|owner=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|peers=
|source_dirs=browser/extensions/formautofill/, toolkit/components/satchel/
|url=
|components=
}}

{{Module
|name=In-product Messaging
|description=The system for delivering in-product messaging.
|owner=[mailto:khudson@mozilla.com Kate Hudson]
|peers=
|source_dirs=toolkit/components/messaging-system/
|url=
|components=Firefox::Messaging System
}}

{{Module
|name=Launcher Process
|description=Windows process for bootstrapping the browser process.
|owner=[mailto:aklotz@mozilla.com Aaron Klotz]
|peers=[mailto:mhowell@mozilla.com Molly Howell]
|source_dirs=browser/app/winlauncher
|url=
|components=Firefox::Launcher Process
}}

{{Module
|name=New Tab Page
|description=The new tab/home page.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:khudson@mozilla.com Kate Hudson], [mailto:sdowne@getpocket.com Scott Downe]
|source_dirs=browser/components/newtab/
|url=
|components=Firefox::New Tab Page
}}

{{Module
|name=Normandy
|description=The experiments and off-train deployments system.
|owner=[mailto:mcooper@mozilla.com Michael Cooper]
|peers=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=toolkit/components/normandy/
|url=
|components=Firefox::Normandy
}}

{{Module
|name=Onboarding
|description=The onboarding experience including UI tours.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=
|source_dirs=browser/components/uitour/
|url=
|components=
}}

{{Module
|name=Password Manager
|description=Managing, saving and filling logins.
|owner=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|peers=[mailto:jwein@mozilla.com Jared Wein], [mailto:sfoster@mozilla.com Sam Foster]
|source_dirs=toolkit/components/passwordmgr/, browser/components/aboutlogins
|url=https://wiki.mozilla.org/Toolkit:Password_Manager
|components=Toolkit::Password Manager, Toolkit::Password Manager: Site Compatibility, Firefox::about:logins
}}

{{Module
|name=Preferences
|description=The front-end preferences system.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mstriemer@mozilla.com Mark Striemer], [mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=browser/components/preferences/, browser/themes/*/preferences, toolkit/mozapps/preferences
|url=
|components=
}}

{{Module
|name=Profile Migration
|description=Migrating data from other browsers.
|owner=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peers=[mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:MattN@mozilla.com Matthew Noorenberghe]
|source_dirs=browser/components/migration/
|url=
|components=
}}

{{Module
|name=Search and Address Bar
|description=The search service, address bar and address bar autocomplete.
|owner=[mailto:standard8@mozilla.com Mark Banner], [mailto:dwillcoxon@mozilla.com Drew Willcoxon]
|peers=[mailto:dharvey@mozilla.com Dale Harvey], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:dao@mozilla.com Dão Gottwald], [mailto:mdeboer@mozilla.com Mike de Boer]
|source_dirs=browser/components/search/, browser/components/urlbar/, toolkit/components/search/
|url=
|components=Firefox::Address Bar, Firefox::Search
}}

{{Module
|name=Security and Privacy UI
|description=The front-end to our security and privacy features, including Protections UI, Site Identity, Site Permissions and Certificate Errors
|owner=[mailto:jhofmann@mozilla.com Johann Hofmann]
|peers=[mailto:nhnt11@mozilla.com Nihanth Subramanya], [mailto:ewright@mozilla.com Erica Wright], [mailto:pbz@mozilla.com Paul Zühlcke], [mailto:prathiksha@mozilla.com Prathiksha]
|source_dirs=browser/components/protections/, browser/components/controlcenter/
|url=
|components=Firefox::Security, Firefox::Protections UI, Firefox::Site Identity, Firefox::Site Permissions
}}

{{Module
|name=Session Restore
|description=Restoring a user's session after starting Firefox.
|owner=[mailto:mdeboer@mozilla.com Michael de Boer]
|peers=
|source_dirs=browser/components/sessionstore/, toolkit/components/sessionstore/
|url=
|components=
}}

{{Module
|name=Tabbed Browser
|description=The UI component controlling browser tabs.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=
|source_dirs=browser/base/content/tabbrowser*, browser/modules/AsyncTabSwitcher.jsm
|url=
|components=Firefox::Tabbed Browser
}}

{{Module
|name=Windows Installer
|description=The installer for Windows.
|owner=[mailto:mhowell@mozilla.com Molly Howell]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin], [mailto:nalexander@mozilla.com Nick Alexander]
|source_dirs=browser/installer/, toolkit/mozapps/installer/
|url=
|components=Firefox::Installer
}}

Modules/Desktop Firefox

2020-07-09T18:47:37Z

Mardak: /* Submodules */ add a couple new tab page peers

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
Owners and peers of the Desktop Firefox module may review code anywhere in the browser and toolkit directories. Reviews should be sent to the more specific submodules below where possible.

{{Module
|name=Desktop Firefox
|description=Standalone Web Browser.
|owner=[mailto:dtownsend@mozilla.com Dave Townsend], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|fallbackpeers=[mailto:dao@mozilla.com Dão Gottwald], [mailto:jwein@mozilla.com Jared Wein], [mailto:jhofmann@mozilla.com Johann Hofmann], [mailto:lina@mozilla.com Lina Cambridge], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:MattN@mozilla.com Matthew Noorenberghe]
|ownersemeritus=
|peersemeritus=[mailto:netzen@gmail.com Brian Bondy], [mailto:lchang@mozilla.com Luke Chang], [mailto:rchien@mozilla.com Ricky Chien], [mailto:dolske@mozilla.com Justin Dolske], [mailto:georg.fritzsche@googlemail.com Georg Fritzsche], [mailto:felipc@gmail.com Felipe Gomes], [mailto:tchien@mozilla.com Tim Guan-tin Chien], [mailto:rexboy@mozilla.com KM Lee Rex], [mailto:gasolin@mozilla.com Fred Lin], [mailto:ralin@mozilla.com Ray Lin], [mailto:fliu@mozilla.com Fischer Liu], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:mark@moxienet.com Mark Mentovai], [mailto:ted.mielczarek@gmail.com Ted Mielczarek], [mailto:bnicholson@mozilla.com Brian Nicholson], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:mano@mozilla.com Asaf Romano], [mailto:msamuel@mozilla.com Marina Samuel], [mailto:jryans@gmail.com J Ryan Stinnett], [mailto:gps@mozilla.com Gregory Szorc], [mailto:ttaubert@mozilla.com Tim Taubert]
|group=firefox-dev
|source_dirs=browser/, toolkit/
|url=[[Firefox/Code_Review|Code Review Guidelines]]
|components=Firefox, Toolkit
}}

== Submodules ==

{{Module
|name=Add-ons Manager
|description=Extension management back-end.
|owner=[mailto:aswan@mozilla.com Andrew Swan], [mailto:kmaglione@mozilla.com Kris Maglione]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:jmathies@mozilla.com Jim Mathies], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/
|url=
|components=
}}

{{Module
|name=Add-ons Manager UI
|description=about:addons.
|owner=[mailto:aswan@mozilla.com Andrew Swan], [mailto:mstriemer@mozilla.com Mark Striemer]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/content/
|url=
|components=
}}

{{Module
|name=Application Update
|description=The application update services.
|owner=[mailto:mhowell@mozilla.com Molly Howell], [mailto:ksteuber@mozilla.com Kirk Steuber]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin]
|source_dirs=toolkit/mozapps/update/
|url=
|components=
}}

{{Module
|name=Bookmarks & History
|description=The bookmarks and history services (Places).
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:lina@mozilla.com Lina Cambridge], [mailto:standard8@mozilla.com Mark Banner], [mailto:adw@mozilla.com Drew Willcoxon]
|source_dirs=browser/components/places/, toolkit/components/places/
|url=
|components=
}}

{{Module
|name=Desktop Theme
|description=The style rules used in the desktop UI.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/themes/, toolkit/themes/
|url=
|components=Firefox::Theme, Toolkit::Themes
}}

{{Module
|name=Desktop UI
|description=The main browser UI except where covered by more specific submodules.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mconley@mozilla.com Mike Conley], [mailto:florian@queze.net Florian Quèze]
|source_dirs=browser/base/content/
|url=
|components=
}}

{{Module
|name=Download Manager
|description=The downloads UI and service.
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch]
|source_dirs=browser/components/downloads/, toolkit/mozapps/downloads/
|url=
|components=
}}

{{Module
|name=Enterprise Policies
|description=System policies for controlling Firefox.
|owner=[mailto:mkaply@mozilla.com Michael Kaply]
|peers=
|source_dirs=browser/components/enterprisepolicies/
|url=
|components=
}}

{{Module
|name=Form Autofill
|description=Form detection and autocomplete.
|owner=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|peers=
|source_dirs=browser/extensions/formautofill/, toolkit/components/satchel/
|url=
|components=
}}

{{Module
|name=In-product Messaging
|description=The system for delivering in-product messaging.
|owner=[mailto:khudson@mozilla.com Kate Hudson]
|peers=
|source_dirs=
|url=
|components=
}}

{{Module
|name=Launcher Process
|description=Windows process for bootstrapping the browser process.
|owner=[mailto:aklotz@mozilla.com Aaron Klotz]
|peers=[mailto:mhowell@mozilla.com Molly Howell]
|source_dirs=browser/app/winlauncher
|url=
|components=Firefox::Launcher Process
}}

{{Module
|name=New Tab Page
|description=The new tab/home page.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:khudson@mozilla.com Kate Hudson], [mailto:sdowne@getpocket.com Scott Downe]
|source_dirs=browser/components/newtab/
|url=
|components=Firefox::New Tab Page
}}

{{Module
|name=Normandy
|description=The experiments and off-train deployments system.
|owner=[mailto:mcooper@mozilla.com Michael Cooper]
|peers=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=toolkit/components/normandy/
|url=
|components=Firefox::Normandy
}}

{{Module
|name=Onboarding
|description=The onboarding experience including UI tours.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=
|source_dirs=browser/components/uitour/
|url=
|components=
}}

{{Module
|name=Password Manager
|description=Managing, saving and filling logins.
|owner=[mailto:MattN@mozilla.com Matthew Noorenberghe]
|peers=[mailto:jwein@mozilla.com Jared Wein], [mailto:sfoster@mozilla.com Sam Foster]
|source_dirs=toolkit/components/passwordmgr/, browser/components/aboutlogins
|url=https://wiki.mozilla.org/Toolkit:Password_Manager
|components=Toolkit::Password Manager, Toolkit::Password Manager: Site Compatibility, Firefox::about:logins
}}

{{Module
|name=Preferences
|description=The front-end preferences system.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mstriemer@mozilla.com Mark Striemer], [mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=browser/components/preferences/, browser/themes/*/preferences, toolkit/mozapps/preferences
|url=
|components=
}}

{{Module
|name=Profile Migration
|description=Migrating data from other browsers.
|owner=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peers=[mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:MattN@mozilla.com Matthew Noorenberghe]
|source_dirs=browser/components/migration/
|url=
|components=
}}

{{Module
|name=Search and Address Bar
|description=The search service, address bar and address bar autocomplete.
|owner=[mailto:standard8@mozilla.com Mark Banner], [mailto:dwillcoxon@mozilla.com Drew Willcoxon]
|peers=[mailto:dharvey@mozilla.com Dale Harvey], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:dao@mozilla.com Dão Gottwald], [mailto:mdeboer@mozilla.com Mike de Boer]
|source_dirs=browser/components/search/, browser/components/urlbar/, toolkit/components/search/
|url=
|components=Firefox::Address Bar, Firefox::Search
}}

{{Module
|name=Security and Privacy UI
|description=The front-end to our security and privacy features, including Protections UI, Site Identity, Site Permissions and Certificate Errors
|owner=[mailto:jhofmann@mozilla.com Johann Hofmann]
|peers=[mailto:nhnt11@mozilla.com Nihanth Subramanya], [mailto:ewright@mozilla.com Erica Wright], [mailto:pbz@mozilla.com Paul Zühlcke], [mailto:prathiksha@mozilla.com Prathiksha]
|source_dirs=browser/components/protections/, browser/components/controlcenter/
|url=
|components=Firefox::Security, Firefox::Protections UI, Firefox::Site Identity, Firefox::Site Permissions
}}

{{Module
|name=Session Restore
|description=Restoring a user's session after starting Firefox.
|owner=[mailto:mdeboer@mozilla.com Michael de Boer]
|peers=
|source_dirs=browser/components/sessionstore/, toolkit/components/sessionstore/
|url=
|components=
}}

{{Module
|name=Tabbed Browser
|description=The UI component controlling browser tabs.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=
|source_dirs=browser/base/content/tabbrowser*, browser/modules/AsyncTabSwitcher.jsm
|url=
|components=Firefox::Tabbed Browser
}}

{{Module
|name=Windows Installer
|description=The installer for Windows.
|owner=[mailto:mhowell@mozilla.com Molly Howell]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin], [mailto:nalexander@mozilla.com Nick Alexander]
|source_dirs=browser/installer/, toolkit/mozapps/installer/
|url=
|components=Firefox::Installer
}}

Firefox/Iterative Hello Development

2015-10-05T15:29:30Z

Mardak: /* Key Bugzilla Queries */ make triaged link point to sorted named query

==Product Backlog==

 
===Key Bugzilla Queries===
* [http://mzl.la/1Q1c3W4 Bugzilla Ranked list]
**Add the "Rank" Column to your results and sort on Rank
***The option to "Change columns" is at bottom of search results
**Search is based on bugs which have the Ranked field
* [http://mzl.la/1JBkwev Un-triaged bugs]
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12373638&columnlist=cf_fx_iteration%2Ccf_fx_points%2Cassigned_to%2Cbug_status%2Cstatus_whiteboard%2Cshort_desc%2Cchangeddate%2Cpriority%2Cbug_severity%2Cresolution%2Ccomponent%2Creporter&o1=anywordssubstr&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=tech-debt&component=Client&component=General&product=Hello%20%28Loop%29 Tech-debt bugs] priority based on [https://etherpad.mozilla.org/brainstormtesthello etherpad discussion - though if you want one that's lower priority but impacting you - grab it]

 
The goals of the Prioritized Product Backlog and dynamic Planning are to:
*Simplify prioritization & planning so the team is always working on the most important features.
*Improve visibility to everyone to clear priorities - so we make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs). 

===Triage Guidelines===
The Product Backlog is continually maintained by the Hello Management team to ensure new priorities are available for each Sprint Planning meeting.
* Priorities: if you are filing a bug - based on your knowledge of the bug feel free to set a priority for consideration based on the following criteria:
** Priority 1 - Blocker, must-fix before shipping in the next release.
** Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping.
** Priority 3 - Average Bug. definitely a problem, but doesn't stop someone from using the product.
** Priority 4 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.
** Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability.

*RANK: Not needed when filing a bug, set during weekly Triage meetings. As priority buckets start to have a large amount of bugs in them, the Rank field can be used to call attention to higher or lower rank and provide a way to sort easily in bugzilla. To have some rhyme/reason to the order - Rank should relate to Priority. The "Ranking" number does not need to be unique. Unless there is a reason to for a bug to be considered before (or after) others in the Priority bucket - default to mid-range value.
** P1 Rank options=1-19, default 15
** P2 Rank options=20-29, default 25
** P3 Rank options=30-39, default 35
** P4 Rank options=40-49, default 45
** P5 Rank options=50-59, default 55
** any that we don't think we can get to in the next 6 months should be set to 100

 
*QE-Verify is a flag that developers should be setting on bugs they are working on. This is used for QE to filter which bugs they check
**"+" means that QE should look at the bug and it can be verified with human eyes
**"-" means QE should not look at
***Typically goes with in-testsuite set to "+", to show testing via another method.
*"Points" should be set when known (if nothing set - assumed a "1" or very small). Most relevant if taking a bigger bug so we know when bugs are large bits of work.
*"Iteration" should be updated when a bug is being worked on during a particular Sprint.

===Filing a bug===
** Open a bug under Product:"Loop" || Component: "General" or "Client"
** Hello team reviews for inclusion into a release backlog every 2 weeks, and will mark "firefox-blocking" accordingly
*We triage weekly - it helps if there is a priority as a starting point and a reason why the priority was set.
**Before it can be given a Rank it should:
*** be in an actionable state
*** for defects, the problem is ready for Engineering or UX: diagnosis, measurement, design, or fixing
*** for feature requests or enhancements, it means that there's a clear problem statement or suggestion
*** has a difficulty/user-impact ratio low enough that we can reasonably expect to spend time fixing the bug within the next 6 months
 

===Definition of Done===
 
* The [https://etherpad.mozilla.org/HsVyzOogAr Definition of Done] ensures a potentially shippable product increment is released at the conclusion of a release cycle.
 
* A potentially shippable product increment means compliance with the work's individual acceptance criteria and not the full story under development.
 

==Contribute to Hello Development==
 
===Good First Bugs===
 
These are tagged as [good first bug] in a bug's Whiteboard field. The challenge of a "good first bug" is only peripherally about the bug itself. The focus, for a new contributor, should be on getting your development environment set up and learning how to navigate Mozilla's contribution process. We are working on better documentation to help you get started with Hello (expect an update Q1 2015), and the #introduction IRC channel exists just to help people getting started as contributors.
 
* '''Hello Backlog Good First Bugs - [http://mzl.la/1zNfmeV View in Bugzilla]
 
==Objectives==
 
The Iterative Development Model implemented for Firefox Desktop aims to accomplish six key objectives:
* '''Transparent - '''Who is working on what, when, and why.
* '''Predictable and Repeatable - '''Know what to expect from the process.
* '''Inclusive - '''Include all key participants (Eng, UX, QA, Security, Product) and stakeholders in the process.
* '''Clear Direction and Decision Making - '''Know what we should do and who makes the call.
* '''Clear and Stable Priorities - '''Be clear on what is most important for each iterative cycle.
* '''Innovative - '''Provide flexibility to engage in experimental and original projects.
 

==Development Iterations (Sprints)==
 
*[https://wiki.mozilla.org/Release_Management/TeamWiki Firefox main release schedule] is the master location for the dates when each Firefox version goes to Aurora, Beta, & Release.
 
'''Firefox 40 Release'''
* '''Iteration 40.1:''' Tuesday March 31 - Monday April 13
* '''Iteration 40.2:''' Tuesday April 14 - Monday April 27
* '''Iteration 40.3:''' Tuesday April 28 - Monday May 11
 
'''Firefox 41 Release'''
* '''Iteration 41.1:''' Tuesday May 12 - Monday May 25
* '''Iteration 41.2:''' Tuesday May 26 - Monday June 8
* '''Iteration 41.3:''' Tuesday June 9 - Monday June 29
** ''Note: IT 41.3 is a 3-week iteration.''
 
'''Firefox 42 Release'''
* '''Iteration 42.1:''' Tuesday June 30 - Monday July 13
* '''Iteration 42.2:''' Tuesday July 14 - Monday July 27
* '''Iteration 42.3:''' Tuesday July 28 - Monday August 10
 
===Themes===
As we plan what's coming next, these are areas being discussed. This is not a commitment to the next projects - just our scratch area.
*finishing Context work (large change: server API changes, FxA and encryption design, client end UX and storage components, server storage/retrieval components, UX change across areas)
*market work
Things we want to do - but parking lot until the highest priorities are done:
*in-conversation chat [https://bugzilla.mozilla.org/show_bug.cgi?id=1108893 bug 1108893]
*Shareplane adjustments [https://bugzilla.mozilla.org/show_bug.cgi?id=1155603 bug 1155603]
*Moving faster: mark-up extraction
*Prevent Link-clickers from clicking on themselves [https://bugzilla.mozilla.org/show_bug.cgi?id=1154251 bug 1154251]
*Metrics [https://bugzilla.mozilla.org/show_bug.cgi?id=1148381 bug 1148381]
*e10s readiness for e10s patches (e10s in Beta in 41, releases in 42 - so MUST be in for 42)
*Starting Visual Refresh [https://bug1138445.bugzilla.mozilla.org/attachment.cgi?id=8587058 bug 8587058]
*Android experience improvements
*Link-Clicker gets desktop UI [https://bugzilla.mozilla.org/show_bug.cgi?id=1066019 bug 1066019]
*Continue quality focus
*WebRTC permission prompt optimization
Risks
*List out risks that we are working on or on our radar

===Current===

====Iteration 41.3 (through June 29)====

* Context preffed on and uplifted to 40. Only minor bug and one minor UX (favicon) this iteration. Looks good. Context metrics landing as well in 40.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1108892 Chat bug has UX attached]: main focus of this iteration. desktop portions landing, working on stand-alone. several bugs this iteration focused. med-risk for landing by June 29th - will update closer to time. Early demos looking good - so the risk would just be the last 20% as we get to it.
* CSS clean-up to enable moving faster is in clean-up this iteration. Landing to make chat work simpler.
* stretch goal of [https://bugzilla.mozilla.org/show_bug.cgi?id=1154251 Prevent link generators from clicking their own links] after Chat lands.

 
<bugzilla>
{
"product":["Loop"],
"include_fields":"id, summary, status, assigned_to, cf_fx_points",
"cf_fx_iteration":"41.3 - Jun 29"

}
</bugzilla>

 

===Past===
====Iteration 41.1 (through May 25)====
* Context work: All strings needed to uplift to Fx40 were landed in 40.3. The feature is preffed on and in aurora for testing to start. still more of the feature is landing (didn't land as one big chunk). some of new UI in nightly now - requesting uplift as the rest lands. thumbnails favicon stuff in nightly now.
**There's still a few big pieces to land - mike reviewed patch for encrypted rooms and Mark is working on landing changes. Editing patch should be landing. big stuff getting out of way this iteration - but some style and functionality bits coming in.
* Affiliate work: working on and ideally landing this iteration - barring unforseen surprises
* Chat: test of the SDK functionality was successful - UX not implemented to design.
* Functional test work broken down - and only top 2 items are 100% blockers to be addressed in 41.1
** If time, telemetry patches (marked Metrics in Backlog). They are low risk/small changes and vital to making informed decisions, we will be requesting uplift to 39 for those landing in this iteration.
* CSS clean-up to enable '''moving faster''' is in review this iteration. This landed as a big chunk of work and we are looking at ways we could potentially chunk up better in future or if the nature of it required bigger blocks.
* Adam and Martin met for couple of days and did initial theory design for IM persistent storage [shell link to early architecture]. Still several months out from implementation - but moving ball forward.
'''All bugs marked with this iteration'''
 
<bugzilla>
{
"product":["Loop"],
"include_fields":"id, summary, status, assigned_to, cf_fx_points",
"cf_fx_iteration":"41.1 - May 25"

}
</bugzilla>

 

====Firefox Release 40 Dev stage (ended May 11)====
* Context work:
** Server end: [https://etherpad.mozilla.org/loopcrossteam 0.17.4] has hit bumps with updated module causing failure and is currently diagnosing 503 errors before deploying.
** Client-end: Continues through at least this iteration. Discovered issue with encryption key generation that will require re-authentication after upgrade, working on UX change now.
* Quality focus this release on reviewing results of data gathered and identifying likely causes/implementing fixes.
* Shareplane landed and verified and uplifting to Fx39.
* Added more Google Analytic metrics for stand-alone client (link clicker)
* Continuing [https://bugzilla.mozilla.org/show_bug.cgi?id=1141296 CSS clean-up in SDK] and how that impacts Hello code. starting landing small pieces - as it's pretty tangled - and keep spinning off and landing more.
* Functional test work broken down - these are areas that help speed development and lower risk, making it simpler to catch errors and regressions sooner.

'''All bugs in this Release'''
 
<bugzilla>
{
"product":["Loop"],
"include_fields":"id, summary, status, assigned_to, cf_fx_points",
"target_milestone":"mozilla39"

}
</bugzilla>

 

====Firefox Release 39 (ended March 30)====
The Fx39 Release is only in Nightly for 5 weeks (normally 6) - ending on March 30th.
* Context work started in this release. This work required implementing a changes across many systems: client front-end code, Link clicker, UX changes in both, [https://bugzilla.mozilla.org/show_bug.cgi?id=1132293 FxA Server (Bug 1132293)], and [https://bugzilla.mozilla.org/show_bug.cgi?id=1141105 Server work (Bug 1141105)]. Changes that touch multiple systems add integration cost/risk and testing complexity.
**Preliminary design for encrypted room context came with this bug. This encryption work will enable future features.
* Tokbox made some changes in the SDK that gave an option to not take the SDK CSS rules. Today the app uses CSS and then TB applies CSS rules as well - making for complex development, testing, and sometime unpredictable results. There was a cost with every SDK upgrade that often UX that was working, stopped and required debugging because of CSS conflicts. Starting work on impact/changes needed for reduced SDK CSS - with the primary goal of FASTER DEVELOPMENT by simplifying.
* Fx36 released with marketing - we are watching/working on the high occurrence bugs from that higher input.
* Social Sharing, AKA SharePlane landed and was backed out - working to re-land during Fx40
* Continue to land telemetry improvements
* Fixing and uplifting Screen Sharing bugs
** Tab sharing work completed this sprint, uplifting to Fx38. Replace track fix coming early in iteration from webRTC team.
* Updated to new SDK with data channel support

 
<bugzilla>
{
"product":["Loop"],
"bug_status":"RESOLVED",
"include_fields":"id, summary, status, assigned_to, cf_fx_points",
"target_milestone":"mozilla39"

}
</bugzilla>

====Firefox Release 38 (ended Feb 23rd)====
* '''Firefox Release 38 Goal:'''
** Fx38 goal is to break down Screen Sharing - and work to implement. Pref-off version of screen sharing (loop.screenshare.enabled), with the Windows only sharing available early Feb. Tab sharing and Active Tab changing preparation work continued into Fx39 and was uplifted back to Fx38. Tokbox delivered an SDK change needed to enable Tab Sharing.
**Work on demos of Hello on Android for MWC took 25%+ of development resources.
**Progress made on CSS improvements (organically growing code has gotten complex to develop and test). Discussion with TB on simplification options, patched client code to better respect constraints and aspect ratios.
**Continuing to reduce tech-debt that has been accumulating over several iterations of quick feature additions is still a priority, especially to aid in QA coverage to avoid regressions as new features are added.

 
 
<bugzilla>
{
"product":["Loop"],
"bug_status":"RESOLVED",
"include_fields":"id, summary, status, assigned_to, cf_fx_points",
"target_milestone":"mozilla38"

}
</bugzilla>

 

====Release 37 (ended Jan 13th)====
* '''Firefox Release 37 Goal:'''
** Fx37 goal is to reduce tech-debt that has been accumulating over several iterations of quick feature additions. In Fx37 we ended up working on many uplifts to Fx35 Beta to complete the Room feature and the First Run Tours.

 
<bugzilla>
{
"product":["Loop"],
"bug_status":"RESOLVED",
"include_fields":"id, summary, status, assigned_to, cf_fx_points",
"target_milestone":"mozilla37"
}
</bugzilla>
 

==Cross-Team Project Calendar==
{{#widget:Widget:Google Calendar
|id=bW96aWxsYS5jb21fNTY0NW1uMWpnamQ5aG8zaXNodHRodnQybHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
}}

==Project Introduction==
 
* '''Team Mailing list:''' [[Firefox/dev-media]]
* '''Team IRC Channel:''' [irc://irc.mozilla.org/loop #loop]
 
===Links to Current info===
The [https://wiki.mozilla.org/Loop/wiki Loop/wiki page] is the central location for current focus, Roadmap, Metrics, UX, Marketing, tech-architecture, and more.

===Roles and Responsibilities===
The [https://wiki.mozilla.org/Loop/Contacts cross-team Loop/Contacts Page] has the Roles and Responsibilities for Hello, webRTC, partner teams, and external partners involved in this project.

===Meetings===
 
{| class="wikitable"
|-
! Meeting !! Day of week !! Pacific Time !! Eastern Time !! Central European Time !! Vidyo Room !! Notes
|-
| "Daily Stand-up" || Monday, Tuesday, Wednesday, Thursday || 8:00AM - 8:30AM || 11:00AM - 11:30PM || 5:00PM - 5:30PM || webRTC-Apps || ||]
|-
| "Retrospective" || Friday || 8:00AM - 9:00AM || 11:00AM - 12:00PM || 5:00PM - 6:00PM || webRTC-Apps || [https://etherpad.mozilla.org/loop-retrospectives etherpad]
|-
| "Cross team alignment" || Tuesday || 11:30AM - 12:00PM || 2:30AM - 3:00PM || || ||
|}

 
<gallery>
File:closedbugs.png
</gallery>

QA/Suggested Tiles/Test Plan

2015-05-28T03:21:35Z

Mardak: /* Context */ different types of bug fixes

= Suggested Tiles =
== Ownership ==
Developer contact: Ed Lee, :Mardak on IRC

QA Lead: [mailto:corne.ionce@softvision.ro Cornel Ionce], :cornel_ionce on IRC

== Status ==
===Overview===
'''[LANDED]''' Nightly 41: landed

'''[LANDED]''' Aurora 40: uplifted

'''[LANDED]''' Beta 39: partially uplifted

'''[BACKED OUT]''' Release 38: backed-out

'''[BACKED OUT]''' Release 38.0.5: backed-out

===Risk analysis===
{| class="wikitable"
|-
! Event !! Probability !! Impact !! Current situation !! Mitigation steps
|-
| TBD|| TBD|| TBD|| TBD || TBD
|}

== Summary ==
Suggested Tiles is a new feature on the new tab page where users who visit certain sites see additional content. There's new onboarding experiences for new as well as existing users that explains the feature and how to turn it off. There's various "business logic" that a server-provided json file can trigger to have suggestions be shown or not shown.

===Context===

There are 17 bugs to uplift from Aurora40 to Beta39:

Onboarding:
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1138818 1138818] - New tab user onboarding for sponsored suggested tiles
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1165430 1165430] - Switch unlocalizable "Example Title" to "mozilla.org"
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1165525 1165525] - Onboarding messaging poorly words how to turn off suggestions by implying blank is the only way

UI changes:
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1158853 1158853] - Replace history tile titles with base domains and include titles as part of tiles
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1158859 1158859] - Update newtab cog menu styling
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1138817 1138817] - Change [SPONSORED] tags to [SUGGESTED] and add [SUGGESTED] tags for suggested tiles
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1165386 1165386] - Always show SPONSORED for any type of sponsored tiles and SUGGESTED for other suggested
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1167805 1167805] - Not enough padding for page title causing pin icon to overlap

Business logic:
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1156549 1156549] - Allow ramp up time for campaigns with strict start/stop times
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1159571 1159571] - Use server provided frequency caps for daily and lifetime totals
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1139496 1139496] - Allow server provided explanation / ad group name to be displayed on Suggested Tiles
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1159884 1159884] - Implement inadjacency with a hardcoded list of hashed sites
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1145428 1145428] - Suggested Tiles pins (becomes a user history tile after end time)

Misc fixes:
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1045766 1045766] - Add telemetry of users who can see new tab Tile suggestions
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1160369 1160369] - Allow for sponsored suggested tiles
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1166552 1166552] - browser_newtab_reportLinkAction.js fails on timeout
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1167243 1167243] - Intermittent browser_newtab_enhanced.js | Suggested for {'Web Education'|'Technology'} enthusiasts

===Enabling the feature===

== References ==
* The UX planned for Suggested Tiles is available [https://bug1150228.bugzilla.mozilla.org/attachment.cgi?id=8592387 here].

== Test cases ==
===Overview===

===Targeted scenarios===

== Bug work ==
====== Tracking bugs ======
'''meta''': [https://bugzilla.mozilla.org/show_bug.cgi?id=1140185 Bug 1140185] - Suggested Tiles: v1.0 Sponsored Release (FX 39)
* blocks: [https://bugzilla.mozilla.org/buglist.cgi?f1=dependson&o1=equals&query_format=advanced&v1=1140185 bugzilla query]
* depends on: [https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&o1=equals&query_format=advanced&v1=1140185 bugzilla query]
'''meta''': [https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Bug 1120311] - Suggested tiles: Affiliate Release (FX 38)
* blocks: [https://bugzilla.mozilla.org/buglist.cgi?f1=dependson&o1=equals&query_format=advanced&v1=1120311 bugzilla query]
* depends on: [https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&list_id=1120311&o1=equals&query_format=advanced&v1=1120311 bugzilla query]
'''meta''': [https://bugzilla.mozilla.org/show_bug.cgi?id=1148859 Bug 1148859] - Uplift to 38 Suggested tiles: Affiliate Release
* blocks: [https://bugzilla.mozilla.org/buglist.cgi?f1=dependson&o1=equals&query_format=advanced&v1=1148859 bugzilla query]
* depends on: [https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&list_id=1148859&o1=equals&query_format=advanced&v1=1148859 bugzilla query]
'''Back-out bug''': [https://bugzilla.mozilla.org/show_bug.cgi?id=1156921 Bug 1156921] - Backout Suggested Tiles (bug 1120311) from 38.0
* Keep Suggested Tiles for 38.0.5/38.1 [https://bugzilla.mozilla.org/show_bug.cgi?id=1157309 (bug 1120311) ]
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
====== Bug triage +/- for verification ======
<div class="mw-collapsible-content">
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1105360 Bug 1105360] - Only enhance tiles that are explicitly enhanceable 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126186 Bug 1126186] - Allow users to turn off recommendations 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126188 Bug 1126188] - Show explanation text for a suggested tile with appropriate styling 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1140496 Bug 1140496] - Only show a suggested tile url for some number of times or until clicked 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1143797 Bug 1143797] - Allow clicking on suggested explanation text to see overlay explaining the suggested tile 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1146146 Bug 1146146] - Maximize the number of rows of tiles by reducing the suggested explanation maximum line count to 2 instead of 3 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1146249 Bug 1146249] - Tiles on the newtab page don't wrap properly 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126182 Bug 1126182] - Extract related tiles data from links json and store for later selection 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126183 Bug 1126183] - Provide a way to check if a site is part of the top 100 PlacesProvider links 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126184 Bug 1126184] - Select a single related tile to show as the first unpinned tile 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1136208 Bug 1136208] - Rename various references of related in Firefox 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1143745 Bug 1143745] - Update the way Firefox reads directoryLinks.json sent from the server for the tiles v3 endpoint 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1149021 Bug 1149021] - Suggested tile with just an image shows a thumbnail instead 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1149680 Bug 1149680] - Include Firefox channel in tiles fetch 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1149682 Bug 1149682] - Filter suggested tiles to only allow non-sponsored content 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1152145 Bug 1152145] - Filter for specific suggested tiles adgroups/buckets/frecent_sites lists with display name for 38 

</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">

====== Bug fix verification ======
<div class="mw-collapsible-content">
'''[VERI]''' [https://bugzilla.mozilla.org/show_bug.cgi?id= Bug ] - title

</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">

====== Logged bugs ======
<div class="mw-collapsible-content">
[https://bugzilla.mozilla.org/show_bug.cgi?id= Bug ] - Title

</div>
</div>

== Sign off ==
===Criteria===
* All the blocker, critical, major bugs have been fixed.

===Results===

'''Merge to Beta Sign-off'''
* {{ok|}} Beta 38 ''(date)''.

'''Merge to Release Sign-off'''
* {{ok|}} RC 38.0 ''(date)''.

QA/Suggested Tiles/Test Plan

2015-05-28T03:15:50Z

Mardak: /* Suggested Tiles */ updating for sponsored suggested

= Suggested Tiles =
== Ownership ==
Developer contact: Ed Lee, :Mardak on IRC

QA Lead: [mailto:corne.ionce@softvision.ro Cornel Ionce], :cornel_ionce on IRC

== Status ==
===Overview===
'''[LANDED]''' Nightly 41: landed

'''[LANDED]''' Aurora 40: uplifted

'''[LANDED]''' Beta 39: partially uplifted

'''[BACKED OUT]''' Release 38: backed-out

'''[BACKED OUT]''' Release 38.0.5: backed-out

===Risk analysis===
{| class="wikitable"
|-
! Event !! Probability !! Impact !! Current situation !! Mitigation steps
|-
| TBD|| TBD|| TBD|| TBD || TBD
|}

== Summary ==
Suggested Tiles is a new feature on the new tab page where users who visit certain sites see additional content. There's new onboarding experiences for new as well as existing users that explains the feature and how to turn it off. There's various "business logic" that a server-provided json file can trigger to have suggestions be shown or not shown.

===Context===

There are 17 bugs to uplift from Aurora40 to Beta39:

===Enabling the feature===

== References ==
* The UX planned for Suggested Tiles is available [https://bug1150228.bugzilla.mozilla.org/attachment.cgi?id=8592387 here].

== Test cases ==
===Overview===

===Targeted scenarios===

== Bug work ==
====== Tracking bugs ======
'''meta''': [https://bugzilla.mozilla.org/show_bug.cgi?id=1140185 Bug 1140185] - Suggested Tiles: v1.0 Sponsored Release (FX 39)
* blocks: [https://bugzilla.mozilla.org/buglist.cgi?f1=dependson&o1=equals&query_format=advanced&v1=1140185 bugzilla query]
* depends on: [https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&o1=equals&query_format=advanced&v1=1140185 bugzilla query]
'''meta''': [https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Bug 1120311] - Suggested tiles: Affiliate Release (FX 38)
* blocks: [https://bugzilla.mozilla.org/buglist.cgi?f1=dependson&o1=equals&query_format=advanced&v1=1120311 bugzilla query]
* depends on: [https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&list_id=1120311&o1=equals&query_format=advanced&v1=1120311 bugzilla query]
'''meta''': [https://bugzilla.mozilla.org/show_bug.cgi?id=1148859 Bug 1148859] - Uplift to 38 Suggested tiles: Affiliate Release
* blocks: [https://bugzilla.mozilla.org/buglist.cgi?f1=dependson&o1=equals&query_format=advanced&v1=1148859 bugzilla query]
* depends on: [https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&list_id=1148859&o1=equals&query_format=advanced&v1=1148859 bugzilla query]
'''Back-out bug''': [https://bugzilla.mozilla.org/show_bug.cgi?id=1156921 Bug 1156921] - Backout Suggested Tiles (bug 1120311) from 38.0
* Keep Suggested Tiles for 38.0.5/38.1 [https://bugzilla.mozilla.org/show_bug.cgi?id=1157309 (bug 1120311) ]
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
====== Bug triage +/- for verification ======
<div class="mw-collapsible-content">
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1105360 Bug 1105360] - Only enhance tiles that are explicitly enhanceable 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126186 Bug 1126186] - Allow users to turn off recommendations 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126188 Bug 1126188] - Show explanation text for a suggested tile with appropriate styling 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1140496 Bug 1140496] - Only show a suggested tile url for some number of times or until clicked 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1143797 Bug 1143797] - Allow clicking on suggested explanation text to see overlay explaining the suggested tile 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1146146 Bug 1146146] - Maximize the number of rows of tiles by reducing the suggested explanation maximum line count to 2 instead of 3 
'''[QE-VERIFY+]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1146249 Bug 1146249] - Tiles on the newtab page don't wrap properly 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126182 Bug 1126182] - Extract related tiles data from links json and store for later selection 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126183 Bug 1126183] - Provide a way to check if a site is part of the top 100 PlacesProvider links 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1126184 Bug 1126184] - Select a single related tile to show as the first unpinned tile 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1136208 Bug 1136208] - Rename various references of related in Firefox 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1143745 Bug 1143745] - Update the way Firefox reads directoryLinks.json sent from the server for the tiles v3 endpoint 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1149021 Bug 1149021] - Suggested tile with just an image shows a thumbnail instead 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1149680 Bug 1149680] - Include Firefox channel in tiles fetch 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1149682 Bug 1149682] - Filter suggested tiles to only allow non-sponsored content 
'''[QE-VERIFY-]''' [https://bugzilla.mozilla.org/show_bug.cgi?id=1152145 Bug 1152145] - Filter for specific suggested tiles adgroups/buckets/frecent_sites lists with display name for 38 

</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">

====== Bug fix verification ======
<div class="mw-collapsible-content">
'''[VERI]''' [https://bugzilla.mozilla.org/show_bug.cgi?id= Bug ] - title

</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">

====== Logged bugs ======
<div class="mw-collapsible-content">
[https://bugzilla.mozilla.org/show_bug.cgi?id= Bug ] - Title

</div>
</div>

== Sign off ==
===Criteria===
* All the blocker, critical, major bugs have been fixed.

===Results===

'''Merge to Beta Sign-off'''
* {{ok|}} Beta 38 ''(date)''.

'''Merge to Release Sign-off'''
* {{ok|}} RC 38.0 ''(date)''.

QA/Suggested Tiles/Test Plan

2015-05-28T02:56:40Z

Mardak: /* Overview */ update for suggested in 39

Tiles

2015-05-12T22:40:13Z

Mardak: /* Technical Details */ data collection covered by in tree docs

== Tiles ==

Every time a user opens up a new tab in Firefox, the browser displays a number of boxes, or Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. What appears in Tiles is currently based on “frecency” (an algorithm that combines your recency of visiting a site and your frequency of visiting a site). Sites that have been visited with the most recency and frequency appear in a user’s Tile.

Default tiles and Enhanced tiles have been running for all current versions of Firefox and pre-release versions where Enhanced tiles are only visible to users who would have seen a history tile for that site in the new tab page. Suggested tiles are available to en-US Firefox 38 users and all Firefox 39 users where suggestions are shown if the user's top sites match a list of sites.

'''NOTE''': ''Information about the progress and plans for Tiles can be found in the [[Content services]] page.''

=== History Tile ===

History Tiles are chosen based on the most-visited sites for a user. Only one tile from each domain is shown.

=== Default Tiles ===

[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail|Default Tiles]]

New users to Firefox are given a set of tiles, default tiles, as suggestions for sites of interest until they generate their own history tiles based off their browsing experience. The list of default tiles given to new users is built from popular tiles and other tiles Mozilla chooses.

Firefox periodically downloads a list of tiles to use as default tiles, based on basic information such as the user locale and geographic location (determined by IP address). As the user gains browsing history, the default tiles will be mixed and replaced by History Tiles. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=972913 Feature bug and dependent code changes]''

=== Suggested Tiles ===

For users with certain top sites in their new tab page, Firefox may suggest a new tile for users to visit. The suggestion will explain why it's being shown, e.g., "Suggested for wiki.mozilla.org visitors." These suggestions will only be shown a fixed number of times before they're automatically removed. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Feature bug and dependent code changes]''

=== Enhanced Tiles ===

For users with existing tiles (history tiles) in their new tab page, Firefox may substitute a better image for the screenshot generated by default. The enhanced tile would not be displayed to a user unless that website would already have appeared on their new tab page, based on their browsing history. The improved image is supplied by the site or partner and can include a logo plus a rollover image. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1030832 Feature bug and dependent code changes]''

=== How to control Tiles? ===

Mozilla has support pages if you're looking to [https://support.mozilla.org/en-US/kb/new-tab-page-show-hide-and-customize-top-sites customize the new tab page], as well as a page that explains [https://support.mozilla.org/en-US/kb/how-do-sponsored-tiles-work how tiles work].

=== Technical Details ===

* [http://gecko.readthedocs.org/en/latest/browser/browser/DirectoryLinksProvider.html In-Tree Technical Documentation]
* [https://github.com/oyiptong/onyx/blob/master/README.md Payload Schema Documentation]
* [[/Testing Notes|Testing notes on Tiles]]

==== Source Code ====

* '''Firefox''' code related to the new tab page that powers Tiles.
**https://mxr.mozilla.org/mozilla-central/source/browser/base/content/newtab/
**https://mxr.mozilla.org/mozilla-central/source/browser/modules/DirectoryLinksProvider.jsm
**https://mxr.mozilla.org/mozilla-central/source/toolkit/modules/NewTabUtils.jsm

* '''Onyx''' is a link server and engagement metrics aggregator for Firefox Tiles handling the delivery and receiving the metrics of Tiles via 3 data endpoints.
** https://github.com/mozilla/onyx

* '''Infernyx''' contains the rules to extract the metrics data and handles the immediate data processing of raw received data into aggregate data.
** https://github.com/mozilla/infernyx

* '''Splice''' is our ingestion, validation, and authoring tool that makes sure tiles are processed, then published to the correct locale and country for Firefox users. It also contains the schemas for the metrics data.
** https://github.com/mozilla/splice

[[Category:Content Services]]

Tiles/Data Collection

2015-05-12T22:39:52Z

Mardak: redirect to intree doc

#REDIRECT [[Tiles#Technical_Details]]

Tiles

2015-05-12T22:38:57Z

Mardak: /* Technical Details */ specify in tree

== Tiles ==

Every time a user opens up a new tab in Firefox, the browser displays a number of boxes, or Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. What appears in Tiles is currently based on “frecency” (an algorithm that combines your recency of visiting a site and your frequency of visiting a site). Sites that have been visited with the most recency and frequency appear in a user’s Tile.

Default tiles and Enhanced tiles have been running for all current versions of Firefox and pre-release versions where Enhanced tiles are only visible to users who would have seen a history tile for that site in the new tab page. Suggested tiles are available to en-US Firefox 38 users and all Firefox 39 users where suggestions are shown if the user's top sites match a list of sites.

'''NOTE''': ''Information about the progress and plans for Tiles can be found in the [[Content services]] page.''

=== History Tile ===

History Tiles are chosen based on the most-visited sites for a user. Only one tile from each domain is shown.

=== Default Tiles ===

[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail|Default Tiles]]

New users to Firefox are given a set of tiles, default tiles, as suggestions for sites of interest until they generate their own history tiles based off their browsing experience. The list of default tiles given to new users is built from popular tiles and other tiles Mozilla chooses.

Firefox periodically downloads a list of tiles to use as default tiles, based on basic information such as the user locale and geographic location (determined by IP address). As the user gains browsing history, the default tiles will be mixed and replaced by History Tiles. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=972913 Feature bug and dependent code changes]''

=== Suggested Tiles ===

For users with certain top sites in their new tab page, Firefox may suggest a new tile for users to visit. The suggestion will explain why it's being shown, e.g., "Suggested for wiki.mozilla.org visitors." These suggestions will only be shown a fixed number of times before they're automatically removed. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Feature bug and dependent code changes]''

=== Enhanced Tiles ===

For users with existing tiles (history tiles) in their new tab page, Firefox may substitute a better image for the screenshot generated by default. The enhanced tile would not be displayed to a user unless that website would already have appeared on their new tab page, based on their browsing history. The improved image is supplied by the site or partner and can include a logo plus a rollover image. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1030832 Feature bug and dependent code changes]''

=== How to control Tiles? ===

Mozilla has support pages if you're looking to [https://support.mozilla.org/en-US/kb/new-tab-page-show-hide-and-customize-top-sites customize the new tab page], as well as a page that explains [https://support.mozilla.org/en-US/kb/how-do-sponsored-tiles-work how tiles work].

=== Technical Details ===

* [[Tiles/Data Collection|Tiles Data Collection]]
* [http://gecko.readthedocs.org/en/latest/browser/browser/DirectoryLinksProvider.html In-Tree Technical Documentation]
* [https://github.com/oyiptong/onyx/blob/master/README.md Payload Schema Documentation]
* [[/Testing Notes|Testing notes on Tiles]]

==== Source Code ====

* '''Firefox''' code related to the new tab page that powers Tiles.
**https://mxr.mozilla.org/mozilla-central/source/browser/base/content/newtab/
**https://mxr.mozilla.org/mozilla-central/source/browser/modules/DirectoryLinksProvider.jsm
**https://mxr.mozilla.org/mozilla-central/source/toolkit/modules/NewTabUtils.jsm

* '''Onyx''' is a link server and engagement metrics aggregator for Firefox Tiles handling the delivery and receiving the metrics of Tiles via 3 data endpoints.
** https://github.com/mozilla/onyx

* '''Infernyx''' contains the rules to extract the metrics data and handles the immediate data processing of raw received data into aggregate data.
** https://github.com/mozilla/infernyx

* '''Splice''' is our ingestion, validation, and authoring tool that makes sure tiles are processed, then published to the correct locale and country for Firefox users. It also contains the schemas for the metrics data.
** https://github.com/mozilla/splice

[[Category:Content Services]]

Tiles/Technical Documentation

2015-05-12T22:38:15Z

Mardak: change to redirect

#REDIRECT [[Tiles#Technical_Details]]

Tiles

2015-05-12T22:35:04Z

Mardak: add source code

== Tiles ==

Every time a user opens up a new tab in Firefox, the browser displays a number of boxes, or Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. What appears in Tiles is currently based on “frecency” (an algorithm that combines your recency of visiting a site and your frequency of visiting a site). Sites that have been visited with the most recency and frequency appear in a user’s Tile.

Default tiles and Enhanced tiles have been running for all current versions of Firefox and pre-release versions where Enhanced tiles are only visible to users who would have seen a history tile for that site in the new tab page. Suggested tiles are available to en-US Firefox 38 users and all Firefox 39 users where suggestions are shown if the user's top sites match a list of sites.

'''NOTE''': ''Information about the progress and plans for Tiles can be found in the [[Content services]] page.''

=== History Tile ===

History Tiles are chosen based on the most-visited sites for a user. Only one tile from each domain is shown.

=== Default Tiles ===

[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail|Default Tiles]]

New users to Firefox are given a set of tiles, default tiles, as suggestions for sites of interest until they generate their own history tiles based off their browsing experience. The list of default tiles given to new users is built from popular tiles and other tiles Mozilla chooses.

Firefox periodically downloads a list of tiles to use as default tiles, based on basic information such as the user locale and geographic location (determined by IP address). As the user gains browsing history, the default tiles will be mixed and replaced by History Tiles. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=972913 Feature bug and dependent code changes]''

=== Suggested Tiles ===

For users with certain top sites in their new tab page, Firefox may suggest a new tile for users to visit. The suggestion will explain why it's being shown, e.g., "Suggested for wiki.mozilla.org visitors." These suggestions will only be shown a fixed number of times before they're automatically removed. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Feature bug and dependent code changes]''

=== Enhanced Tiles ===

For users with existing tiles (history tiles) in their new tab page, Firefox may substitute a better image for the screenshot generated by default. The enhanced tile would not be displayed to a user unless that website would already have appeared on their new tab page, based on their browsing history. The improved image is supplied by the site or partner and can include a logo plus a rollover image. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1030832 Feature bug and dependent code changes]''

=== How to control Tiles? ===

Mozilla has support pages if you're looking to [https://support.mozilla.org/en-US/kb/new-tab-page-show-hide-and-customize-top-sites customize the new tab page], as well as a page that explains [https://support.mozilla.org/en-US/kb/how-do-sponsored-tiles-work how tiles work].

=== Technical Details ===

* [[Tiles/Data Collection|Tiles Data Collection]]
* [http://gecko.readthedocs.org/en/latest/browser/browser/DirectoryLinksProvider.html Technical Documentation]
* [https://github.com/oyiptong/onyx/blob/master/README.md Payload Schema Documentation]
* [[/Testing Notes|Testing notes on Tiles]]

==== Source Code ====

* '''Firefox''' code related to the new tab page that powers Tiles.
**https://mxr.mozilla.org/mozilla-central/source/browser/base/content/newtab/
**https://mxr.mozilla.org/mozilla-central/source/browser/modules/DirectoryLinksProvider.jsm
**https://mxr.mozilla.org/mozilla-central/source/toolkit/modules/NewTabUtils.jsm

* '''Onyx''' is a link server and engagement metrics aggregator for Firefox Tiles handling the delivery and receiving the metrics of Tiles via 3 data endpoints.
** https://github.com/mozilla/onyx

* '''Infernyx''' contains the rules to extract the metrics data and handles the immediate data processing of raw received data into aggregate data.
** https://github.com/mozilla/infernyx

* '''Splice''' is our ingestion, validation, and authoring tool that makes sure tiles are processed, then published to the correct locale and country for Firefox users. It also contains the schemas for the metrics data.
** https://github.com/mozilla/splice

[[Category:Content Services]]

Tiles

2015-05-12T22:33:14Z

Mardak: /* Technical Details */ update link syntax

== Tiles ==

Every time a user opens up a new tab in Firefox, the browser displays a number of boxes, or Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. What appears in Tiles is currently based on “frecency” (an algorithm that combines your recency of visiting a site and your frequency of visiting a site). Sites that have been visited with the most recency and frequency appear in a user’s Tile.

Default tiles and Enhanced tiles have been running for all current versions of Firefox and pre-release versions where Enhanced tiles are only visible to users who would have seen a history tile for that site in the new tab page. Suggested tiles are available to en-US Firefox 38 users and all Firefox 39 users where suggestions are shown if the user's top sites match a list of sites.

'''NOTE''': ''Information about the progress and plans for Tiles can be found in the [[Content services]] page.''

=== History Tile ===

History Tiles are chosen based on the most-visited sites for a user. Only one tile from each domain is shown.

=== Default Tiles ===

[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail|Default Tiles]]

New users to Firefox are given a set of tiles, default tiles, as suggestions for sites of interest until they generate their own history tiles based off their browsing experience. The list of default tiles given to new users is built from popular tiles and other tiles Mozilla chooses.

Firefox periodically downloads a list of tiles to use as default tiles, based on basic information such as the user locale and geographic location (determined by IP address). As the user gains browsing history, the default tiles will be mixed and replaced by History Tiles. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=972913 Feature bug and dependent code changes]''

=== Suggested Tiles ===

For users with certain top sites in their new tab page, Firefox may suggest a new tile for users to visit. The suggestion will explain why it's being shown, e.g., "Suggested for wiki.mozilla.org visitors." These suggestions will only be shown a fixed number of times before they're automatically removed. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Feature bug and dependent code changes]''

=== Enhanced Tiles ===

For users with existing tiles (history tiles) in their new tab page, Firefox may substitute a better image for the screenshot generated by default. The enhanced tile would not be displayed to a user unless that website would already have appeared on their new tab page, based on their browsing history. The improved image is supplied by the site or partner and can include a logo plus a rollover image. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1030832 Feature bug and dependent code changes]''

=== How to control Tiles? ===

Mozilla has support pages if you're looking to [https://support.mozilla.org/en-US/kb/new-tab-page-show-hide-and-customize-top-sites customize the new tab page], as well as a page that explains [https://support.mozilla.org/en-US/kb/how-do-sponsored-tiles-work how tiles work].

=== Technical Details ===

* [[Tiles/Data Collection|Tiles Data Collection]]
* [http://gecko.readthedocs.org/en/latest/browser/browser/DirectoryLinksProvider.html Technical Documentation]
* [https://github.com/oyiptong/onyx/blob/master/README.md Payload Schema Documentation]
* [[/Testing Notes|Testing notes on Tiles]]

[[Category:Content Services]]

Tiles

2015-05-12T22:32:56Z

Mardak: /* Technical Details */ fix link

== Tiles ==

Every time a user opens up a new tab in Firefox, the browser displays a number of boxes, or Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. What appears in Tiles is currently based on “frecency” (an algorithm that combines your recency of visiting a site and your frequency of visiting a site). Sites that have been visited with the most recency and frequency appear in a user’s Tile.

Default tiles and Enhanced tiles have been running for all current versions of Firefox and pre-release versions where Enhanced tiles are only visible to users who would have seen a history tile for that site in the new tab page. Suggested tiles are available to en-US Firefox 38 users and all Firefox 39 users where suggestions are shown if the user's top sites match a list of sites.

'''NOTE''': ''Information about the progress and plans for Tiles can be found in the [[Content services]] page.''

=== History Tile ===

History Tiles are chosen based on the most-visited sites for a user. Only one tile from each domain is shown.

=== Default Tiles ===

[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail|Default Tiles]]

New users to Firefox are given a set of tiles, default tiles, as suggestions for sites of interest until they generate their own history tiles based off their browsing experience. The list of default tiles given to new users is built from popular tiles and other tiles Mozilla chooses.

Firefox periodically downloads a list of tiles to use as default tiles, based on basic information such as the user locale and geographic location (determined by IP address). As the user gains browsing history, the default tiles will be mixed and replaced by History Tiles. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=972913 Feature bug and dependent code changes]''

=== Suggested Tiles ===

For users with certain top sites in their new tab page, Firefox may suggest a new tile for users to visit. The suggestion will explain why it's being shown, e.g., "Suggested for wiki.mozilla.org visitors." These suggestions will only be shown a fixed number of times before they're automatically removed. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Feature bug and dependent code changes]''

=== Enhanced Tiles ===

For users with existing tiles (history tiles) in their new tab page, Firefox may substitute a better image for the screenshot generated by default. The enhanced tile would not be displayed to a user unless that website would already have appeared on their new tab page, based on their browsing history. The improved image is supplied by the site or partner and can include a logo plus a rollover image. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1030832 Feature bug and dependent code changes]''

=== How to control Tiles? ===

Mozilla has support pages if you're looking to [https://support.mozilla.org/en-US/kb/new-tab-page-show-hide-and-customize-top-sites customize the new tab page], as well as a page that explains [https://support.mozilla.org/en-US/kb/how-do-sponsored-tiles-work how tiles work].

=== Technical Details ===

* [[Tiles/Data Collection|Tiles Data Collection]]
* [http://gecko.readthedocs.org/en/latest/browser/browser/DirectoryLinksProvider.html|Technical Documentation]
* [https://github.com/oyiptong/onyx/blob/master/README.md Payload Schema Documentation]
* [[/Testing Notes|Testing notes on Tiles]]

[[Category:Content Services]]

Tiles

2015-05-12T22:32:35Z

Mardak: /* Technical Details */ use in tree docs

== Tiles ==

Every time a user opens up a new tab in Firefox, the browser displays a number of boxes, or Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. What appears in Tiles is currently based on “frecency” (an algorithm that combines your recency of visiting a site and your frequency of visiting a site). Sites that have been visited with the most recency and frequency appear in a user’s Tile.

Default tiles and Enhanced tiles have been running for all current versions of Firefox and pre-release versions where Enhanced tiles are only visible to users who would have seen a history tile for that site in the new tab page. Suggested tiles are available to en-US Firefox 38 users and all Firefox 39 users where suggestions are shown if the user's top sites match a list of sites.

'''NOTE''': ''Information about the progress and plans for Tiles can be found in the [[Content services]] page.''

=== History Tile ===

History Tiles are chosen based on the most-visited sites for a user. Only one tile from each domain is shown.

=== Default Tiles ===

[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail|Default Tiles]]

New users to Firefox are given a set of tiles, default tiles, as suggestions for sites of interest until they generate their own history tiles based off their browsing experience. The list of default tiles given to new users is built from popular tiles and other tiles Mozilla chooses.

Firefox periodically downloads a list of tiles to use as default tiles, based on basic information such as the user locale and geographic location (determined by IP address). As the user gains browsing history, the default tiles will be mixed and replaced by History Tiles. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=972913 Feature bug and dependent code changes]''

=== Suggested Tiles ===

For users with certain top sites in their new tab page, Firefox may suggest a new tile for users to visit. The suggestion will explain why it's being shown, e.g., "Suggested for wiki.mozilla.org visitors." These suggestions will only be shown a fixed number of times before they're automatically removed. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Feature bug and dependent code changes]''

=== Enhanced Tiles ===

For users with existing tiles (history tiles) in their new tab page, Firefox may substitute a better image for the screenshot generated by default. The enhanced tile would not be displayed to a user unless that website would already have appeared on their new tab page, based on their browsing history. The improved image is supplied by the site or partner and can include a logo plus a rollover image. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1030832 Feature bug and dependent code changes]''

=== How to control Tiles? ===

Mozilla has support pages if you're looking to [https://support.mozilla.org/en-US/kb/new-tab-page-show-hide-and-customize-top-sites customize the new tab page], as well as a page that explains [https://support.mozilla.org/en-US/kb/how-do-sponsored-tiles-work how tiles work].

=== Technical Details ===

* [[Tiles/Data Collection|Tiles Data Collection]]
* [[http://gecko.readthedocs.org/en/latest/browser/browser/DirectoryLinksProvider.html|Technical Documentation]]
* [https://github.com/oyiptong/onyx/blob/master/README.md Payload Schema Documentation]
* [[/Testing Notes|Testing notes on Tiles]]

[[Category:Content Services]]

Tiles

2015-05-06T16:01:27Z

Mardak: /* Tiles */ reverting to "frecency" and clarifying

== Tiles ==

Every time a user opens up a new tab in Firefox, the browser displays a number of boxes, or Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. What appears in Tiles is currently based on “frecency” (an algorithm that combines your recency of visiting a site and your frequency of visiting a site). Sites that have been visited with the most recency and frequency appear in a user’s Tile.

Default tiles and Enhanced tiles have been running for all current versions of Firefox and pre-release versions where Enhanced tiles are only visible to users who would have seen a history tile for that site in the new tab page. Suggested tiles are available to en-US Firefox 38 users and all Firefox 39 users where suggestions are shown if the user's top sites match a list of sites.

'''NOTE''': ''Information about the progress and plans for Tiles can be found in the [[Content services]] page.''

=== History Tile ===

History Tiles are chosen based on the most-visited sites for a user. Only one tile from each domain is shown.

=== Default Tiles ===

[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail|Default Tiles]]

New users to Firefox are given a set of tiles, default tiles, as suggestions for sites of interest until they generate their own history tiles based off their browsing experience. The list of default tiles given to new users is built from popular tiles and other tiles Mozilla chooses.

Firefox periodically downloads a list of tiles to use as default tiles, based on basic information such as the user locale and geographic location (determined by IP address). As the user gains browsing history, the default tiles will be mixed and replaced by History Tiles. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=972913 Feature bug and dependent code changes]''

=== Suggested Tiles ===

For users with certain top sites in their new tab page, Firefox may suggest a new tile for users to visit. The suggestion will explain why it's being shown, e.g., "Suggested for wiki.mozilla.org visitors." These suggestions will only be shown a fixed number of times before they're automatically removed. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Feature bug and dependent code changes]''

=== Enhanced Tiles ===

For users with existing tiles (history tiles) in their new tab page, Firefox may substitute a better image for the screenshot generated by default. The enhanced tile would not be displayed to a user unless that website would already have appeared on their new tab page, based on their browsing history. The improved image is supplied by the site or partner and can include a logo plus a rollover image. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1030832 Feature bug and dependent code changes]''

=== How to control Tiles? ===

Mozilla has support pages if you're looking to [https://support.mozilla.org/en-US/kb/new-tab-page-show-hide-and-customize-top-sites customize the new tab page], as well as a page that explains [https://support.mozilla.org/en-US/kb/how-do-sponsored-tiles-work how tiles work].

=== Technical Details ===

* [[Tiles/Data Collection|Tiles Data Collection]]
* [[Tiles/Technical Documentation|Technical Documentation]]
* [https://github.com/oyiptong/onyx/blob/master/README.md Payload Schema Documentation]
* [[/Testing Notes|Testing notes on Tiles]]

[[Category:Content Services]]

Content services

2015-04-29T09:09:24Z

Mardak: /* Product Guidelines */ user choice controls

= Content Services Overview =

The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.

The team works to make the web economically and socially sustainable. We want to sustain it economically, to ensure that the Web remains a place of economic opportunity for content creators. And we wish to make is socially sustainable, meaning that we wish to address the "maladies" that the advertising-supported content ecosystem has engendered on the Web, including:
* poor user experience
* widespread use of proprietary technology on the Web
* ad fraud
* lack of user control over data resulting in a loss of privacy

Our current mission is to provide in-browser promoted content experiences for advertisers who want better, higher-quality relationships with their audience and who choose Mozilla Content Services in order to have a future-facing, ethical partner with scale.

== Product Guidelines ==

To achieve our mission, we build products that rely on users trusting Mozilla including code that is in Firefox and add-ons as well as our services. We want to earn trust by being transparent with our policies, processes, and open source code. While not a strict requirement for releasing a new product, we will try to build trust into code so that users do not have to rely on Mozilla services operating according to policy. If our services need to collect data, we intend to only use the minimal amount of data necessary to answer specific questions, and we will document the behaviors and communicate to users/community that this is happening. We will also build controls into the products to provide better user choice as well as an easy mechanism to turn things off.

== Product Roadmaps==

===[https://wiki.mozilla.org/Tiles Directory Tiles]===
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we began tests in market (first in pre-release channels) in 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This began testing in 2014 Q2/3. The successes here led to work on additional Tile enhancements outside of First-Run.

===[https://wiki.mozilla.org/Tiles Suggested Tiles]===
:For existing users with browsing history, we want to provide users valuable content of new places to visit. We provide Firefox with additional data that it uses to decide if a suggestion should be made on the New Tab page. For example, if a user tends to visit web development sites, we can make a suggestion to visit "Mozilla Developer Network."

===[https://intranet.mozilla.org/UP UP/Intent Engine]===
:[https://intranet.mozilla.org/UP UP] is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads). Within UP, we have a particular focus around Intentcasting and VRM.

== Content Services Resources==

Doc Searls' [http://www.amazon.com/The-Intention-Economy-Customers-Charge/dp/1422158527 Intention Economy Book.]

Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]

Join our Interest mailing list [https://mail.mozilla.org/listinfo/contentservices-distro ContentServices Distro]

Reach out on email to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]

Find us on IRC #mozcontent

Content services

2015-04-29T09:07:32Z

Mardak: /* Product Guidelines */ collecting data not just from Firefox

= Content Services Overview =

The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.

The team works to make the web economically and socially sustainable. We want to sustain it economically, to ensure that the Web remains a place of economic opportunity for content creators. And we wish to make is socially sustainable, meaning that we wish to address the "maladies" that the advertising-supported content ecosystem has engendered on the Web, including:
* poor user experience
* widespread use of proprietary technology on the Web
* ad fraud
* lack of user control over data resulting in a loss of privacy

Our current mission is to provide in-browser promoted content experiences for advertisers who want better, higher-quality relationships with their audience and who choose Mozilla Content Services in order to have a future-facing, ethical partner with scale.

== Product Guidelines ==

To achieve our mission, we build products that rely on users trusting Mozilla including code that is in Firefox and add-ons as well as our services. We want to earn trust by being transparent with our policies, processes, and open source code. While not a strict requirement for releasing a new product, we will try to build trust into code so that users do not have to rely on Mozilla services operating according to policy. If our services need to collect data, we intend to only use the minimal amount of data necessary to answer specific questions, and we will document the behaviors and communicate to users/community that this is happening.

== Product Roadmaps==

===[https://wiki.mozilla.org/Tiles Directory Tiles]===
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we began tests in market (first in pre-release channels) in 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This began testing in 2014 Q2/3. The successes here led to work on additional Tile enhancements outside of First-Run.

===[https://wiki.mozilla.org/Tiles Suggested Tiles]===
:For existing users with browsing history, we want to provide users valuable content of new places to visit. We provide Firefox with additional data that it uses to decide if a suggestion should be made on the New Tab page. For example, if a user tends to visit web development sites, we can make a suggestion to visit "Mozilla Developer Network."

===[https://intranet.mozilla.org/UP UP/Intent Engine]===
:[https://intranet.mozilla.org/UP UP] is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads). Within UP, we have a particular focus around Intentcasting and VRM.

== Content Services Resources==

Doc Searls' [http://www.amazon.com/The-Intention-Economy-Customers-Charge/dp/1422158527 Intention Economy Book.]

Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]

Join our Interest mailing list [https://mail.mozilla.org/listinfo/contentservices-distro ContentServices Distro]

Reach out on email to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]

Find us on IRC #mozcontent

Content services

2015-04-29T09:06:19Z

Mardak: /* Product Guidelines */ requirement for releasing

= Content Services Overview =

The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.

The team works to make the web economically and socially sustainable. We want to sustain it economically, to ensure that the Web remains a place of economic opportunity for content creators. And we wish to make is socially sustainable, meaning that we wish to address the "maladies" that the advertising-supported content ecosystem has engendered on the Web, including:
* poor user experience
* widespread use of proprietary technology on the Web
* ad fraud
* lack of user control over data resulting in a loss of privacy

Our current mission is to provide in-browser promoted content experiences for advertisers who want better, higher-quality relationships with their audience and who choose Mozilla Content Services in order to have a future-facing, ethical partner with scale.

== Product Guidelines ==

To achieve our mission, we build products that rely on users trusting Mozilla including code that is in Firefox and add-ons as well as our services. We want to earn trust by being transparent with our policies, processes, and open source code. While not a strict requirement for releasing a new product, we will try to build trust into code so that users do not have to rely on Mozilla services operating according to policy. If our services need to collect data from Firefox, we intend to only use the minimal amount of data necessary to answer specific questions, and we will document the behaviors and communicate to users/community that this is happening.

== Product Roadmaps==

===[https://wiki.mozilla.org/Tiles Directory Tiles]===
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we began tests in market (first in pre-release channels) in 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This began testing in 2014 Q2/3. The successes here led to work on additional Tile enhancements outside of First-Run.

===[https://wiki.mozilla.org/Tiles Suggested Tiles]===
:For existing users with browsing history, we want to provide users valuable content of new places to visit. We provide Firefox with additional data that it uses to decide if a suggestion should be made on the New Tab page. For example, if a user tends to visit web development sites, we can make a suggestion to visit "Mozilla Developer Network."

===[https://intranet.mozilla.org/UP UP/Intent Engine]===
:[https://intranet.mozilla.org/UP UP] is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads). Within UP, we have a particular focus around Intentcasting and VRM.

== Content Services Resources==

Doc Searls' [http://www.amazon.com/The-Intention-Economy-Customers-Charge/dp/1422158527 Intention Economy Book.]

Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]

Join our Interest mailing list [https://mail.mozilla.org/listinfo/contentservices-distro ContentServices Distro]

Reach out on email to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]

Find us on IRC #mozcontent

Content services

2015-04-29T09:02:42Z

Mardak: /* Product Roadmaps */ suggested tiles

= Content Services Overview =

The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.

The team works to make the web economically and socially sustainable. We want to sustain it economically, to ensure that the Web remains a place of economic opportunity for content creators. And we wish to make is socially sustainable, meaning that we wish to address the "maladies" that the advertising-supported content ecosystem has engendered on the Web, including:
* poor user experience
* widespread use of proprietary technology on the Web
* ad fraud
* lack of user control over data resulting in a loss of privacy

Our current mission is to provide in-browser promoted content experiences for advertisers who want better, higher-quality relationships with their audience and who choose Mozilla Content Services in order to have a future-facing, ethical partner with scale.

== Product Guidelines ==

To achieve our mission, we build products that rely on users trusting Mozilla including code that is in Firefox and add-ons as well as our services. We want to earn trust by being transparent with our policies, processes, and open source code. While not a strict requirement, we will try to build trust into code so that users do not have to rely on Mozilla services operating according to policy. If our services need to collect data from Firefox, we intend to only use the minimal amount of data necessary to answer specific questions, and we will document the behaviors and communicate to users/community that this is happening.

== Product Roadmaps==

===[https://wiki.mozilla.org/Tiles Directory Tiles]===
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we began tests in market (first in pre-release channels) in 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This began testing in 2014 Q2/3. The successes here led to work on additional Tile enhancements outside of First-Run.

===[https://wiki.mozilla.org/Tiles Suggested Tiles]===
:For existing users with browsing history, we want to provide users valuable content of new places to visit. We provide Firefox with additional data that it uses to decide if a suggestion should be made on the New Tab page. For example, if a user tends to visit web development sites, we can make a suggestion to visit "Mozilla Developer Network."

===[https://intranet.mozilla.org/UP UP/Intent Engine]===
:[https://intranet.mozilla.org/UP UP] is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads). Within UP, we have a particular focus around Intentcasting and VRM.

== Content Services Resources==

Doc Searls' [http://www.amazon.com/The-Intention-Economy-Customers-Charge/dp/1422158527 Intention Economy Book.]

Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]

Join our Interest mailing list [https://mail.mozilla.org/listinfo/contentservices-distro ContentServices Distro]

Reach out on email to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]

Find us on IRC #mozcontent

Content services

2015-04-29T08:58:15Z

Mardak: /* Directory Tiles */ directory tiles past

= Content Services Overview =

The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.

The team works to make the web economically and socially sustainable. We want to sustain it economically, to ensure that the Web remains a place of economic opportunity for content creators. And we wish to make is socially sustainable, meaning that we wish to address the "maladies" that the advertising-supported content ecosystem has engendered on the Web, including:
* poor user experience
* widespread use of proprietary technology on the Web
* ad fraud
* lack of user control over data resulting in a loss of privacy

Our current mission is to provide in-browser promoted content experiences for advertisers who want better, higher-quality relationships with their audience and who choose Mozilla Content Services in order to have a future-facing, ethical partner with scale.

== Product Guidelines ==

To achieve our mission, we build products that rely on users trusting Mozilla including code that is in Firefox and add-ons as well as our services. We want to earn trust by being transparent with our policies, processes, and open source code. While not a strict requirement, we will try to build trust into code so that users do not have to rely on Mozilla services operating according to policy. If our services need to collect data from Firefox, we intend to only use the minimal amount of data necessary to answer specific questions, and we will document the behaviors and communicate to users/community that this is happening.

== Product Roadmaps==

===Directory Tiles===
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we began tests in market (first in pre-release channels) in 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This began testing in 2014 Q2/3. The successes here led to work on additional Tile enhancements outside of First-Run.

===[https://intranet.mozilla.org/UP UP/Intent Engine]===
:[https://intranet.mozilla.org/UP UP] is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads). Within UP, we have a particular focus around Intentcasting and VRM.

== Content Services Resources==

Doc Searls' [http://www.amazon.com/The-Intention-Economy-Customers-Charge/dp/1422158527 Intention Economy Book.]

Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]

Join our Interest mailing list [https://mail.mozilla.org/listinfo/contentservices-distro ContentServices Distro]

Reach out on email to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]

Find us on IRC #mozcontent

Content services

2015-04-29T08:55:57Z

Mardak: /* Content Services Overview */ product guidelines

= Content Services Overview =

The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.

The team works to make the web economically and socially sustainable. We want to sustain it economically, to ensure that the Web remains a place of economic opportunity for content creators. And we wish to make is socially sustainable, meaning that we wish to address the "maladies" that the advertising-supported content ecosystem has engendered on the Web, including:
* poor user experience
* widespread use of proprietary technology on the Web
* ad fraud
* lack of user control over data resulting in a loss of privacy

Our current mission is to provide in-browser promoted content experiences for advertisers who want better, higher-quality relationships with their audience and who choose Mozilla Content Services in order to have a future-facing, ethical partner with scale.

== Product Guidelines ==

To achieve our mission, we build products that rely on users trusting Mozilla including code that is in Firefox and add-ons as well as our services. We want to earn trust by being transparent with our policies, processes, and open source code. While not a strict requirement, we will try to build trust into code so that users do not have to rely on Mozilla services operating according to policy. If our services need to collect data from Firefox, we intend to only use the minimal amount of data necessary to answer specific questions, and we will document the behaviors and communicate to users/community that this is happening.

== Product Roadmaps==

===Directory Tiles===
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we will test in market (first in pre-release channels) within 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This should begin testing in Q2/3 and we will then work on additional Tile enhancements outside of First-Run.

===[https://intranet.mozilla.org/UP UP/Intent Engine]===
:[https://intranet.mozilla.org/UP UP] is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads). Within UP, we have a particular focus around Intentcasting and VRM.

== Content Services Resources==

Doc Searls' [http://www.amazon.com/The-Intention-Economy-Customers-Charge/dp/1422158527 Intention Economy Book.]

Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]

Join our Interest mailing list [https://mail.mozilla.org/listinfo/contentservices-distro ContentServices Distro]

Reach out on email to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]

Find us on IRC #mozcontent

Tiles/Technical Documentation

2015-04-03T17:58:51Z

Mardak: /* Tiles Technical Documentation */ high level, suggested object

== Tiles Technical Documentation ==

For information about the ''progress and plans'' for [[Tiles]] see the [[Content services]] page.

For general information about Tiles and the New Tab page see the [[Tiles]] page.

This is technical information for advanced users or enterprise implementers on how Tiles are stored locally and fetched remotely and how you can change it.

=== High Level ===

To potentially show any of Default, Suggested, or Enhanced Tiles, Firefox fetches/downloads -- at most once a day -- a JSON file containing lists of tiles with data to determine if a tile should be shown and what to be shown. Firefox caches that file and decides 1) if there aren't enough history tiles being shown to fill in with Default Tiles 2) if the user's top sites match any of the triggering criteria for Suggested Tiles 3) if a visible history tile should be replaced by an Enhanced Tile. Firefox also sends cookieless pings to measure in aggregate which Tiles are useful or not.

=== Preferences ===

There are two main preferences for Tiles that control fetching and metrics.

==== Source ====

This preference tells Firefox where to fetch Tiles from:

browser.newtabpage.directory.source = https://tiles.services.mozilla.com/v2/links/fetch

This preference can be set to anything that returns JSON, setting this to an empty JSON object will disable Tiles from showing and fetching new Tiles. With the change below a new user would only see empty Tiles and Firefox could no longer fetch new Tiles.

browser.newtabpage.directory.source = data:application/json,{}

==== Ping ====

This preference tells Firefox where Tiles metrics are reported:

browser.newtabpage.directory.ping = https://tiles.services.mozilla.com/v2/links/

Changing or disabling this pref may prevent Firefox from being able to report metrics on Tiles. Do not set this to alternate URLs, setting this to nothing will disable the ping.

=== Customizing Tiles ===

If you wanted to have a custom set of Default Tiles, for example in an Enterprise deployment, you could set the source preference to a custom set of local Tiles.

Here's an example of a custom default tiles ''source'' preference:

data:application/json,{
"directory": [
{
"url" : "http://www.mozilla.org/",
"bgColor" : "%234d4e54",
"type": "custom",
"imageURI": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAALQAAABWCAQAAADMSHQwAAAFWklEQVR4AezBgQAAAACAoP2pF6kCAAAAAAAAAABgdu0sNqoyDOP4C1WWgCylKgqKoNRCqaxCiyx2bBGNAVrCJkRkUYFAMEGNVUjYRIIIuAYlBqKAUSBcWEUIBlDCBRU6pKINCAUU0CibbSyL9e%2FNmTdvpudMF2ZGj5nfc%2FcwyZCH6Xd6DlMXTGUbe1jEjYhJMgEK2M5WGiDYZDCJ1QTJRWId4f%2BTDwkpoanT5bKXcgDgEqJpyFrKCJmWGLr2ycNa4rQzQf1OY0RzFdTziaFrn41Yh%2FQTjSqnBaLZA2puYujaZy3Wt06bBepPkhFNIaj5iaFrn4FY0522F3boNohmE6gFiaHrkvmEbNQuw3PoDYlPdP0zmOWsYoRpunkOvT4xdDTj%2F6FpS3vESTo5ZNMBwaYBGeQQIBWJmNsZRB7DybJD1DvN6EE%2BraM0dGdyGct4HiMj3kM3pzdz%2BIzLnEIQ5lJKyC6ynVfdxFJOEPKd52%2Bqk9jNNUIq2MYYBJtxlNSQxc4%2F64t8ykEuAJB63UNns5ojWMdZRqv4DV0IahL7CTcN4UHOEO5rkhBsulOEm13Yn40CalKIICRhdbiOoZOYQRHufqFvvIZeTkgV7t7F3TLEpD%2FeLtIRcTKLmqxz5vk5KkM%2FQxmRXCU5PkPnUF%2BXzGf6VqqI5FeaOK98mer%2BxiqM6tDvUJMV8Rm6J%2BH28T5bwKXfQDHWPYiTHVgvkEZXXsLarJejMdiMJkAp1uyoDi2UgSpiDSvYjPV9fIZOw%2FqS3k6%2FAmunnmU%2Fgsp0uj5YeYiT8Vg9ENf0ohLUbiTKQ%2Fd1Xr2ENO2mgDpHo3gM3RnUAdMPAPWx6T8CNdDlAVAQMTkC9ux1STusq7SK%2BtDCVnbQLqyrJKSClvEYOhXUF6bPBDXd9B9UGzqJS56XyJWgziIuOYyVh8RgaLecJKQ8%2FkPvMn0WqHkeT9UGuJzyTyMm07A6IWFZhbUFifHQN9OF%2B%2BlPFmcJuUCzf3Po%2Fh5Dr6s29ONYwxCTfKyHEGyGYl0gKYZDj2U9pVRS3W808cfQz2IFIkyZj5i0oBJrEBKjoUdxFG9nuMEfQxdEmGsI1mjEZC%2FW60iMhp5HZKdo4I%2Bh50Q4Hh7Bsg88n8MqRWI0dIBwFfzECXOTdBzxx9ATI5zRo7AGYx%2FgWx1jNvRhrJX0ozUNSeEKIUf9MvQDWFMQk5lYd2h%2FGmsWEqOhO2EtNteHKkIO%2B2XoplwGtQgxeRvUSW0%2FwdqH1GvoSlI8hl6g7QisttrfBeqQX4YWPgf1FWJyDNR7TvckVhUpdRg6HdQ1bvG4Y12o7QSslq73oyX%2BGXoIVlePL8F0QxDuxKrkPqQOQ9%2BLlezx93rV4xqRqX17UBf9M7QQBHWeCbSmBeO4Uu3pXXNKsUrIYlhYRpLkOXQbz7vQt0Ad1LYb1iHnVO%2FFfqxh%2Fhk6FbAq%2BAPrvPPtueGA9RfVnaah59DCMaydPOz0U7FKWOt62T3PJnYQ7hyZfhlayMfbZdJqfpWagUQYugALtjl9S8I47zmO2gjGfuh0FD%2BYPtvjrq0QRQ5iEqAMN0G6mCcONWvlDG3dbb43egBcT%2BqJWPCafd4Y8b%2Foyuka%2B6E7UOwkyBrTdze9PQsXEtQ%2F6YnY0IjZFNmDgW94CjEZTHHEBHlTB91u%2BtsQM%2FUbVJj36Gt%2BqoIo1ms%2Fi9NYUEw%2FhNkAQIY%2Fv0DTiVzGMJps2iExSgqPMpknCJBCEmLSh%2FFMZgTpNDJtY%2FJZyga2spFXGKr9SIoYhfwXh%2F6nHToQAQAAAADkb73IbXCjR49u9OhGjx7d6NGNHj260aMbPXp0o0c3evToRo8OZGoOg%2BFHUXQAAAAASUVORK5CYII%3D",
"title": "Mozilla%20Foundation"
}
]
}

=== JSON Format ===

The Tile JSON format is a simple object, the top level keys group together the different types of Tiles.

At a high level the data object looks like this:

{ "directory" : [ ARRAY OF DEFAULT TILE OBJECTS ], "suggested" : [ ARRAY OF SUGGESTED TILE OBJECTS ], "enhanced" : [ ARRAY OF ENHANCED TILE OBJECTS ]}

Each Default Tile object requires a few attributes, most of which are self explanatory.

{
"url" : "http://www.mozilla.org/",
"bgColor" : "#4d4e54",
"type": "custom",
"imageURI": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAALQAAABWCAQAAADMSHQwAAAFWklEQVR4AezBgQAAAACAoP2pF6kCAAAAAAAAAABgdu0sNqoyDOP4C1WWgCylKgqKoNRCqaxCiyx2bBGNAVrCJkRkUYFAMEGNVUjYRIIIuAYlBqKAUSBcWEUIBlDCBRU6pKINCAUU0CibbSyL9e%2FNmTdvpudMF2ZGj5nfc%2FcwyZCH6Xd6DlMXTGUbe1jEjYhJMgEK2M5WGiDYZDCJ1QTJRWId4f%2BTDwkpoanT5bKXcgDgEqJpyFrKCJmWGLr2ycNa4rQzQf1OY0RzFdTziaFrn41Yh%2FQTjSqnBaLZA2puYujaZy3Wt06bBepPkhFNIaj5iaFrn4FY0522F3boNohmE6gFiaHrkvmEbNQuw3PoDYlPdP0zmOWsYoRpunkOvT4xdDTj%2F6FpS3vESTo5ZNMBwaYBGeQQIBWJmNsZRB7DybJD1DvN6EE%2BraM0dGdyGct4HiMj3kM3pzdz%2BIzLnEIQ5lJKyC6ynVfdxFJOEPKd52%2Bqk9jNNUIq2MYYBJtxlNSQxc4%2F64t8ykEuAJB63UNns5ojWMdZRqv4DV0IahL7CTcN4UHOEO5rkhBsulOEm13Yn40CalKIICRhdbiOoZOYQRHufqFvvIZeTkgV7t7F3TLEpD%2FeLtIRcTKLmqxz5vk5KkM%2FQxmRXCU5PkPnUF%2BXzGf6VqqI5FeaOK98mer%2BxiqM6tDvUJMV8Rm6J%2BH28T5bwKXfQDHWPYiTHVgvkEZXXsLarJejMdiMJkAp1uyoDi2UgSpiDSvYjPV9fIZOw%2FqS3k6%2FAmunnmU%2Fgsp0uj5YeYiT8Vg9ENf0ohLUbiTKQ%2Fd1Xr2ENO2mgDpHo3gM3RnUAdMPAPWx6T8CNdDlAVAQMTkC9ux1STusq7SK%2BtDCVnbQLqyrJKSClvEYOhXUF6bPBDXd9B9UGzqJS56XyJWgziIuOYyVh8RgaLecJKQ8%2FkPvMn0WqHkeT9UGuJzyTyMm07A6IWFZhbUFifHQN9OF%2B%2BlPFmcJuUCzf3Po%2Fh5Dr6s29ONYwxCTfKyHEGyGYl0gKYZDj2U9pVRS3W808cfQz2IFIkyZj5i0oBJrEBKjoUdxFG9nuMEfQxdEmGsI1mjEZC%2FW60iMhp5HZKdo4I%2Bh50Q4Hh7Bsg88n8MqRWI0dIBwFfzECXOTdBzxx9ATI5zRo7AGYx%2FgWx1jNvRhrJX0ozUNSeEKIUf9MvQDWFMQk5lYd2h%2FGmsWEqOhO2EtNteHKkIO%2B2XoplwGtQgxeRvUSW0%2FwdqH1GvoSlI8hl6g7QisttrfBeqQX4YWPgf1FWJyDNR7TvckVhUpdRg6HdQ1bvG4Y12o7QSslq73oyX%2BGXoIVlePL8F0QxDuxKrkPqQOQ9%2BLlezx93rV4xqRqX17UBf9M7QQBHWeCbSmBeO4Uu3pXXNKsUrIYlhYRpLkOXQbz7vQt0Ad1LYb1iHnVO%2FFfqxh%2Fhk6FbAq%2BAPrvPPtueGA9RfVnaah59DCMaydPOz0U7FKWOt62T3PJnYQ7hyZfhlayMfbZdJqfpWagUQYugALtjl9S8I47zmO2gjGfuh0FD%2BYPtvjrq0QRQ5iEqAMN0G6mCcONWvlDG3dbb43egBcT%2BqJWPCafd4Y8b%2Foyuka%2B6E7UOwkyBrTdze9PQsXEtQ%2F6YnY0IjZFNmDgW94CjEZTHHEBHlTB91u%2BtsQM%2FUbVJj36Gt%2BqoIo1ms%2Fi9NYUEw%2FhNkAQIY%2Fv0DTiVzGMJps2iExSgqPMpknCJBCEmLSh%2FFMZgTpNDJtY%2FJZyga2spFXGKr9SIoYhfwXh%2F6nHToQAQAAAADkb73IbXCjR49u9OhGjx7d6NGNHj260aMbPXp0o0c3evToRo8OZGoOg%2BFHUXQAAAAASUVORK5CYII%3D",
"title": "Mozilla%20Foundation"
}

'''NOTE''': You need to URL escape all the text, in the bgColor you'll see the # is replaced with %23 and the spaces are replaced with %20 in the title.

''Default and Enhanced Tiles Object Attributes''

* '''url''' is the URL you want the Tile to link to
* '''bgColor''' provides a background fill color in case the image doesn't fill the space
* '''type''' isn't needed for custom tiles so please use the 'custom' attribute
* '''imageURI''' provides the full URL to the image you want centered. Images need to be properly sized for the Tiles.
* '''title''' provides the display text that will appear below the Tile and for the link title attribute.
* '''enhancedImageURI''' provides the full URL to the roll over image you want centered. Images need to be properly sized for the Tiles. If included a "Roll Over" image will be the image seen until a user mouses over the Tile, on mouse over the imageURI is then shown.

''Suggested Tiles Object Attributes''

* Same as the Default Tiles Object with the additions below
* '''frecent_sites''' array of domain strings to match against the user's top sites

==== Source Code ====

* '''Firefox''' code related to the new tab page that powers Tiles.
**https://mxr.mozilla.org/mozilla-central/source/browser/base/content/newtab/
**https://mxr.mozilla.org/mozilla-central/source/browser/modules/DirectoryLinksProvider.jsm
**https://mxr.mozilla.org/mozilla-central/source/toolkit/modules/NewTabUtils.jsm

* '''Onyx''' is a link server and engagement metrics aggregator for Firefox Tiles handling the delivery and receiving the metrics of Tiles via 3 data endpoints.
** https://github.com/mozilla/onyx

* '''Infernyx''' contains the rules to extract the metrics data and handles the immediate data processing of raw received data into aggregate data.
** https://github.com/mozilla/infernyx

* '''Splice''' is our ingestion, validation, and authoring tool that makes sure tiles are processed, then published to the correct locale and country for Firefox users. It also contains the schemas for the metrics data.
** https://github.com/mozilla/splice

Tiles

2015-04-03T17:47:33Z

Mardak: /* Tiles */ update intro for suggested

== Tiles ==

Every time a user opens up a new tab in Firefox, the browser displays a number of boxes, or Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. What appears in Tiles is currently based on a “frecency” algorithm: your recency of visiting a site and your frequency of visiting a site. Sites that have been visited with the most recency and frequency appear in a user’s Tile.

Default tiles and Enhanced tiles have been running for all current versions of Firefox and pre-release versions where Enhanced tiles are only visible to users who would have seen a history tile for that site in the new tab page. Suggested tiles are available to en-US Firefox 38 users and all Firefox 39 users where suggestions are shown if the user's top sites match a list of sites.

'''NOTE''': ''Information about the progress and plans for Tiles can be found in the [[Content services]] page.''

=== History Tile ===

History Tiles are chosen based on the most-visited sites for a user. Only one tile from each domain is shown.

=== Default Tiles ===

[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail|Default Tiles]]

New users to Firefox are given a set of tiles, default tiles, as suggestions for sites of interest until they generate their own history tiles based off their browsing experience. The list of default tiles given to new users is built from popular tiles and other tiles Mozilla chooses.

Firefox periodically downloads a list of tiles to use as default tiles, based on basic information such as the user locale and geographic location (determined by IP address). As the user gains browsing history, the default tiles will be mixed and replaced by History Tiles. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=972913 Feature bug and dependent code changes]''

=== Suggested Tiles ===

For users with certain top sites in their new tab page, Firefox may suggest a new tile for users to visit. The suggestion will explain why it's being shown, e.g., "Suggested for wiki.mozilla.org visitors." These suggestions will only be shown a fixed number of times before they're automatically removed. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Feature bug and dependent code changes]''

=== Enhanced Tiles ===

For users with existing tiles (history tiles) in their new tab page, Firefox may substitute a better image for the screenshot generated by default. The enhanced tile would not be displayed to a user unless that website would already have appeared on their new tab page, based on their browsing history. The improved image is supplied by the site or partner and can include a logo plus a rollover image. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1030832 Feature bug and dependent code changes]''

=== How to control Tiles? ===

Mozilla has support pages if you're looking to [https://support.mozilla.org/en-US/kb/new-tab-page-show-hide-and-customize-top-sites customize the new tab page], as well as a page that explains [https://support.mozilla.org/en-US/kb/how-do-sponsored-tiles-work how tiles work].

=== Technical Details ===

* [[Tiles/Data Collection|Tiles Data Collection]]
* [[Tiles/Technical Documentation|Technical Documentation]]
* [https://github.com/oyiptong/onyx/blob/master/README.md Payload Schema Documentation]
* [[/Testing Notes|Testing notes on Tiles]]

[[Category:Content Services]]

Tiles/Data Collection

2015-04-03T17:41:27Z

Mardak: /* Other Details */ remove older version note from 6 months ago

== Current Status ==

Firefox sends the following information about [[Tiles|tiles]] to Mozilla:

On viewing the new-tab page, blocking a tile, moving, clicking a tile or an associated sponsored link, pinning or unpinning a tile, the following information is sent:

=== History tiles ===
* Position of the tile (ex: 0-8 for a user with 8 visible tiles )
* Pin status of the tile (ex: pinned = true )
* Tile frecency factor (ex: int(Frecency/1000))
* '''No''' tile ID or URL information is sent for history tiles

=== Directory, Suggested, Enhanced tiles ===

The information for History tiles, plus:

* The tile ID (which encodes the tile destination)
* A signal (empty string; no URL) if the tile is enhanced

=== Other Details ===

The data is sent via a SSL connection with Key-pinning (as of {{bug|1030135}}) to mozilla cloud services. No extra tracking cookies are set by the server for this ping.

When the data is received, the IP address is geo-encoded: the IP address is not stored on Mozilla’s servers.

Descriptions for the payload schemas for the pings can be found [https://github.com/oyiptong/onyx/blob/master/README.md here]

== Prospecting Future Tile Partners ==

In addition to continuous data collection required for partners, we also want to collect information about current user history tiles, to provide business guidance about which sites are most valuable to our users for picking both Directory and Enhanced Tiles.

Proposal:
* Run a limited-time experiment in the beta channel to collect information about the top history site information.
* Rather than sending any URLs, prepare in advance a potential list of top sites or partners as a whitelist of sites. Only send information about tiles on this whitelist, and only send the TLD+2, not the full URL. This will avoid sending many kinds of personal URLs.

This prospecting experiment is tracked in {{bug|1062708}}

Tiles/Data Collection

2015-04-03T17:40:39Z

Mardak: /* Directory and Enhanced tiles */ suggested also has same data as directory

== Current Status ==

Firefox sends the following information about [[Tiles|tiles]] to Mozilla:

On viewing the new-tab page, blocking a tile, moving, clicking a tile or an associated sponsored link, pinning or unpinning a tile, the following information is sent:

=== History tiles ===
* Position of the tile (ex: 0-8 for a user with 8 visible tiles )
* Pin status of the tile (ex: pinned = true )
* Tile frecency factor (ex: int(Frecency/1000))
* '''No''' tile ID or URL information is sent for history tiles

=== Directory, Suggested, Enhanced tiles ===

The information for History tiles, plus:

* The tile ID (which encodes the tile destination)
* A signal (empty string; no URL) if the tile is enhanced

=== Other Details ===

A previous version of these patches would send the full URL for enhanced tiles. This URL submission has been removed.

The data is sent via a SSL connection with Key-pinning (as of {{bug|1030135}}) to mozilla cloud services. No extra tracking cookies are set by the server for this ping.

When the data is received, the IP address is geo-encoded: the IP address is not stored on Mozilla’s servers.

Descriptions for the payload schemas for the pings can be found [https://github.com/oyiptong/onyx/blob/master/README.md here]

== Prospecting Future Tile Partners ==

In addition to continuous data collection required for partners, we also want to collect information about current user history tiles, to provide business guidance about which sites are most valuable to our users for picking both Directory and Enhanced Tiles.

Proposal:
* Run a limited-time experiment in the beta channel to collect information about the top history site information.
* Rather than sending any URLs, prepare in advance a potential list of top sites or partners as a whitelist of sites. Only send information about tiles on this whitelist, and only send the TLD+2, not the full URL. This will avoid sending many kinds of personal URLs.

This prospecting experiment is tracked in {{bug|1062708}}

Tiles

2015-03-31T19:18:24Z

Mardak: add suggested tiles, links to bugs

== Tiles ==

Every time a user opens up a new tab in Firefox, the browser displays a number of boxes, or Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. What appears in Tiles is currently based on a “frecency” algorithm: your recency of visiting a site and your frequency of visiting a site. Sites that have been visited with the most recency and frequency appear in a user’s Tile.

Default tiles (previously known as Directory Tiles) have been running for new users in Nightly, Aurora, and Beta but not yet in production. Enhanced tiles are now available to users on the en-US versions of Firefox Nightly, Aurora and Beta, and will be visible only to users who frequently and recently visit the site of participating partners.

'''NOTE''': ''Information about the progress and plans for Tiles can be found in the [[Content services]] page.''

=== History Tile ===

History Tiles are chosen based on the most-visited sites for a user. Only one tile from each domain is shown.

=== Default Tiles ===

[[File:Directory-tiles-new-tab-page-screenshot.png|thumbnail|Default Tiles]]

New users to Firefox are given a set of tiles, default tiles, as suggestions for sites of interest until they generate their own history tiles based off their browsing experience. The list of default tiles given to new users is built from popular tiles and other tiles Mozilla chooses.

Firefox periodically downloads a list of tiles to use as default tiles, based on basic information such as the user locale and geographic location (determined by IP address). As the user gains browsing history, the default tiles will be mixed and replaced by History Tiles. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=972913 Feature bug and dependent code changes]''

=== Suggested Tiles ===

For users with certain top sites in their new tab page, Firefox may suggest a new tile for users to visit. The suggestion will explain why it's being shown, e.g., "Suggested for wiki.mozilla.org visitors." These suggestions will only be shown a fixed number of times before they're automatically removed. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1120311 Feature bug and dependent code changes]''

=== Enhanced Tiles ===

For users with existing tiles (history tiles) in their new tab page, Firefox may substitute a better image for the screenshot generated by default. The enhanced tile would not be displayed to a user unless that website would already have appeared on their new tab page, based on their browsing history. The improved image is supplied by the site or partner and can include a logo plus a rollover image. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1030832 Feature bug and dependent code changes]''

=== How to control Tiles? ===

Mozilla has support pages if you're looking to [https://support.mozilla.org/en-US/kb/new-tab-page-show-hide-and-customize-top-sites customize the new tab page], as well as a page that explains [https://support.mozilla.org/en-US/kb/how-do-sponsored-tiles-work how tiles work].

=== Technical Details ===

* [[Tiles/Data Collection|Tiles Data Collection]]
* [[Tiles/Technical Documentation|Technical Documentation]]
* [https://github.com/oyiptong/onyx/blob/master/README.md Payload Schema Documentation]
* [[/Testing Notes|Testing notes on Tiles]]

[[Category:Content Services]]

Tiles/Technical Documentation

2014-12-10T02:33:51Z

Mardak: /* Source Code */ add directory links provider link

== Tiles Technical Documentation ==

For information about the ''progress and plans'' for [[Tiles]] see the [[Content services]] page.

For general information about Tiles and the New Tab page see the [[Tiles]] page.

This is technical information for advanced users or enterprise implementers on how Tiles are stored locally and fetched remotely and how you can change it.

=== Previously ===

Default Tiles were originally built into Desktop Firefox for en-US builds in the ''chrome://global/content/directoryLinks.json'' location. This file no longer exists in Firefox as Tiles are now downloaded from a web service. Additionally the preference ( ''browser.newtabpage.directorySource'' ) for Tiles has changed, the current details are listed below.

=== Preferences ===

There are two main preferences for Tiles that control fetching and metrics.

==== Source ====

This preference tells Firefox where to fetch Tiles from:

browser.newtabpage.directory.source = https://tiles.services.mozilla.com/v2/links/fetch

This preference can be set to anything that returns JSON, setting this to an empty JSON object will disable Tiles from showing and fetching new Tiles. With the change below a new user would only see empty Tiles and Firefox could no longer fetch new Tiles.

browser.newtabpage.directory.source = data:application/json,{}

==== Ping ====

This preference tells Firefox where Tiles metrics are reported:

browser.newtabpage.directory.ping = https://tiles.services.mozilla.com/v2/links/

Changing or disabling this pref may prevent Firefox from being able to report metrics on Tiles. Do not set this to alternate URLs, setting this to nothing will disable the ping.

=== Customizing Tiles ===

If you wanted to have a custom set of Default Tiles, for example in an Enterprise deployment, you could set the source preference to a custom set of local Tiles.

Here's an example of a custom default tiles ''source'' preference:

data:application/json,{
"en-US": [
{
"url" : "http://www.mozilla.org/",
"bgColor" : "%234d4e54",
"type": "custom",
"imageURI": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAALQAAABWCAQAAADMSHQwAAAFWklEQVR4AezBgQAAAACAoP2pF6kCAAAAAAAAAABgdu0sNqoyDOP4C1WWgCylKgqKoNRCqaxCiyx2bBGNAVrCJkRkUYFAMEGNVUjYRIIIuAYlBqKAUSBcWEUIBlDCBRU6pKINCAUU0CibbSyL9e%2FNmTdvpudMF2ZGj5nfc%2FcwyZCH6Xd6DlMXTGUbe1jEjYhJMgEK2M5WGiDYZDCJ1QTJRWId4f%2BTDwkpoanT5bKXcgDgEqJpyFrKCJmWGLr2ycNa4rQzQf1OY0RzFdTziaFrn41Yh%2FQTjSqnBaLZA2puYujaZy3Wt06bBepPkhFNIaj5iaFrn4FY0522F3boNohmE6gFiaHrkvmEbNQuw3PoDYlPdP0zmOWsYoRpunkOvT4xdDTj%2F6FpS3vESTo5ZNMBwaYBGeQQIBWJmNsZRB7DybJD1DvN6EE%2BraM0dGdyGct4HiMj3kM3pzdz%2BIzLnEIQ5lJKyC6ynVfdxFJOEPKd52%2Bqk9jNNUIq2MYYBJtxlNSQxc4%2F64t8ykEuAJB63UNns5ojWMdZRqv4DV0IahL7CTcN4UHOEO5rkhBsulOEm13Yn40CalKIICRhdbiOoZOYQRHufqFvvIZeTkgV7t7F3TLEpD%2FeLtIRcTKLmqxz5vk5KkM%2FQxmRXCU5PkPnUF%2BXzGf6VqqI5FeaOK98mer%2BxiqM6tDvUJMV8Rm6J%2BH28T5bwKXfQDHWPYiTHVgvkEZXXsLarJejMdiMJkAp1uyoDi2UgSpiDSvYjPV9fIZOw%2FqS3k6%2FAmunnmU%2Fgsp0uj5YeYiT8Vg9ENf0ohLUbiTKQ%2Fd1Xr2ENO2mgDpHo3gM3RnUAdMPAPWx6T8CNdDlAVAQMTkC9ux1STusq7SK%2BtDCVnbQLqyrJKSClvEYOhXUF6bPBDXd9B9UGzqJS56XyJWgziIuOYyVh8RgaLecJKQ8%2FkPvMn0WqHkeT9UGuJzyTyMm07A6IWFZhbUFifHQN9OF%2B%2BlPFmcJuUCzf3Po%2Fh5Dr6s29ONYwxCTfKyHEGyGYl0gKYZDj2U9pVRS3W808cfQz2IFIkyZj5i0oBJrEBKjoUdxFG9nuMEfQxdEmGsI1mjEZC%2FW60iMhp5HZKdo4I%2Bh50Q4Hh7Bsg88n8MqRWI0dIBwFfzECXOTdBzxx9ATI5zRo7AGYx%2FgWx1jNvRhrJX0ozUNSeEKIUf9MvQDWFMQk5lYd2h%2FGmsWEqOhO2EtNteHKkIO%2B2XoplwGtQgxeRvUSW0%2FwdqH1GvoSlI8hl6g7QisttrfBeqQX4YWPgf1FWJyDNR7TvckVhUpdRg6HdQ1bvG4Y12o7QSslq73oyX%2BGXoIVlePL8F0QxDuxKrkPqQOQ9%2BLlezx93rV4xqRqX17UBf9M7QQBHWeCbSmBeO4Uu3pXXNKsUrIYlhYRpLkOXQbz7vQt0Ad1LYb1iHnVO%2FFfqxh%2Fhk6FbAq%2BAPrvPPtueGA9RfVnaah59DCMaydPOz0U7FKWOt62T3PJnYQ7hyZfhlayMfbZdJqfpWagUQYugALtjl9S8I47zmO2gjGfuh0FD%2BYPtvjrq0QRQ5iEqAMN0G6mCcONWvlDG3dbb43egBcT%2BqJWPCafd4Y8b%2Foyuka%2B6E7UOwkyBrTdze9PQsXEtQ%2F6YnY0IjZFNmDgW94CjEZTHHEBHlTB91u%2BtsQM%2FUbVJj36Gt%2BqoIo1ms%2Fi9NYUEw%2FhNkAQIY%2Fv0DTiVzGMJps2iExSgqPMpknCJBCEmLSh%2FFMZgTpNDJtY%2FJZyga2spFXGKr9SIoYhfwXh%2F6nHToQAQAAAADkb73IbXCjR49u9OhGjx7d6NGNHj260aMbPXp0o0c3evToRo8OZGoOg%2BFHUXQAAAAASUVORK5CYII%3D",
"title": "Mozilla%20Foundation"
}
]
}

=== JSON Format ===

The Tile JSON format is a simple object, the top level needs to be a locale that Firefox understands. This object allows you to offer multiple locales in a single JSON file.

At a high level the data object looks like this:

{ "LOCALE" : [ ARRAY OF DEFAULT TILE OBJECTS ] }

You can have many locales in the Tiles dictionary object to support multiple languages.

For example:

{ "en-US" : [ ARRAY OF US DEFAULT TILES ], "en-CA" : [ ARRAY OF CA DEFAULT TILES ] }

Each Default Tile object requires a few attributes, most of which are self explanatory.

{
"url" : "http://www.mozilla.org/",
"bgColor" : "%234d4e54",
"type": "custom",
"imageURI": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAALQAAABWCAQAAADMSHQwAAAFWklEQVR4AezBgQAAAACAoP2pF6kCAAAAAAAAAABgdu0sNqoyDOP4C1WWgCylKgqKoNRCqaxCiyx2bBGNAVrCJkRkUYFAMEGNVUjYRIIIuAYlBqKAUSBcWEUIBlDCBRU6pKINCAUU0CibbSyL9e%2FNmTdvpudMF2ZGj5nfc%2FcwyZCH6Xd6DlMXTGUbe1jEjYhJMgEK2M5WGiDYZDCJ1QTJRWId4f%2BTDwkpoanT5bKXcgDgEqJpyFrKCJmWGLr2ycNa4rQzQf1OY0RzFdTziaFrn41Yh%2FQTjSqnBaLZA2puYujaZy3Wt06bBepPkhFNIaj5iaFrn4FY0522F3boNohmE6gFiaHrkvmEbNQuw3PoDYlPdP0zmOWsYoRpunkOvT4xdDTj%2F6FpS3vESTo5ZNMBwaYBGeQQIBWJmNsZRB7DybJD1DvN6EE%2BraM0dGdyGct4HiMj3kM3pzdz%2BIzLnEIQ5lJKyC6ynVfdxFJOEPKd52%2Bqk9jNNUIq2MYYBJtxlNSQxc4%2F64t8ykEuAJB63UNns5ojWMdZRqv4DV0IahL7CTcN4UHOEO5rkhBsulOEm13Yn40CalKIICRhdbiOoZOYQRHufqFvvIZeTkgV7t7F3TLEpD%2FeLtIRcTKLmqxz5vk5KkM%2FQxmRXCU5PkPnUF%2BXzGf6VqqI5FeaOK98mer%2BxiqM6tDvUJMV8Rm6J%2BH28T5bwKXfQDHWPYiTHVgvkEZXXsLarJejMdiMJkAp1uyoDi2UgSpiDSvYjPV9fIZOw%2FqS3k6%2FAmunnmU%2Fgsp0uj5YeYiT8Vg9ENf0ohLUbiTKQ%2Fd1Xr2ENO2mgDpHo3gM3RnUAdMPAPWx6T8CNdDlAVAQMTkC9ux1STusq7SK%2BtDCVnbQLqyrJKSClvEYOhXUF6bPBDXd9B9UGzqJS56XyJWgziIuOYyVh8RgaLecJKQ8%2FkPvMn0WqHkeT9UGuJzyTyMm07A6IWFZhbUFifHQN9OF%2B%2BlPFmcJuUCzf3Po%2Fh5Dr6s29ONYwxCTfKyHEGyGYl0gKYZDj2U9pVRS3W808cfQz2IFIkyZj5i0oBJrEBKjoUdxFG9nuMEfQxdEmGsI1mjEZC%2FW60iMhp5HZKdo4I%2Bh50Q4Hh7Bsg88n8MqRWI0dIBwFfzECXOTdBzxx9ATI5zRo7AGYx%2FgWx1jNvRhrJX0ozUNSeEKIUf9MvQDWFMQk5lYd2h%2FGmsWEqOhO2EtNteHKkIO%2B2XoplwGtQgxeRvUSW0%2FwdqH1GvoSlI8hl6g7QisttrfBeqQX4YWPgf1FWJyDNR7TvckVhUpdRg6HdQ1bvG4Y12o7QSslq73oyX%2BGXoIVlePL8F0QxDuxKrkPqQOQ9%2BLlezx93rV4xqRqX17UBf9M7QQBHWeCbSmBeO4Uu3pXXNKsUrIYlhYRpLkOXQbz7vQt0Ad1LYb1iHnVO%2FFfqxh%2Fhk6FbAq%2BAPrvPPtueGA9RfVnaah59DCMaydPOz0U7FKWOt62T3PJnYQ7hyZfhlayMfbZdJqfpWagUQYugALtjl9S8I47zmO2gjGfuh0FD%2BYPtvjrq0QRQ5iEqAMN0G6mCcONWvlDG3dbb43egBcT%2BqJWPCafd4Y8b%2Foyuka%2B6E7UOwkyBrTdze9PQsXEtQ%2F6YnY0IjZFNmDgW94CjEZTHHEBHlTB91u%2BtsQM%2FUbVJj36Gt%2BqoIo1ms%2Fi9NYUEw%2FhNkAQIY%2Fv0DTiVzGMJps2iExSgqPMpknCJBCEmLSh%2FFMZgTpNDJtY%2FJZyga2spFXGKr9SIoYhfwXh%2F6nHToQAQAAAADkb73IbXCjR49u9OhGjx7d6NGNHj260aMbPXp0o0c3evToRo8OZGoOg%2BFHUXQAAAAASUVORK5CYII%3D",
"title": "Mozilla%20Foundation"
}

'''NOTE''': You need to URL escape all the text, in the bgColor you'll see the # is replaced with %23 and the spaces are replaced with %20 in the title.

''Default Tiles Object Attributes''

* '''url''' is the URL you want the Tile to link to
* '''bgColor''' provides a background fill color in case the image doesn't fill the space
* '''type''' isn't needed for custom tiles so please use the 'custom' attribute
* '''imageURI''' provides the full URL to the image you want centered. Images need to be properly sized for the Tiles.
* '''title''' provides the display text that will appear below the Tile and for the link title attribute.
* '''enhancedImageURI''' provides the full URL to the roll over image you want centered. Images need to be properly sized for the Tiles. If included a "Roll Over" image will be the image seen until a user mouses over the Tile, on mouse over the imageURI is then shown.

==== Source Code ====

* '''Firefox''' code related to the new tab page that powers Tiles.
**https://mxr.mozilla.org/mozilla-central/source/browser/base/content/newtab/
**https://mxr.mozilla.org/mozilla-central/source/browser/modules/DirectoryLinksProvider.jsm
**https://mxr.mozilla.org/mozilla-central/source/toolkit/modules/NewTabUtils.jsm

* '''Onyx''' is a link server and engagement metrics aggregator for Firefox Tiles handling the delivery and receiving the metrics of Tiles via 3 data endpoints.
** https://github.com/mozilla/onyx

* '''Infernyx''' contains the rules to extract the metrics data and handles the immediate data processing of raw received data into aggregate data.
** https://github.com/mozilla/infernyx

* '''Splice''' is our ingestion, validation, and authoring tool that makes sure tiles are processed, then published to the correct locale and country for Firefox users. It also contains the schemas for the metrics data.
** https://github.com/mozilla/splice

QA/Firefox/Alder Dogfooding

2014-10-22T18:52:43Z

Mardak: /* Getting the Builds */ explicitly labeling en-US builds

Welcome to our Simple How-To Guide for obtaining, installing, and configuring FxDecade preliminary builds. In this text (and in the browser that you'll download) the builds are named "Alder Nightly Builds" so we will use that name in this document. These are the preliminary versions of what will be the official 33.1 Firefox Decade release build during the week of November 10. Anything you can do to help test these builds is extremely appreciated.

It's important to get as wide of an audience on these builds as possible, and we appreciate your contribution. It is also important to test these builds using a new profile, so this short guide will help you do that, and will have a way for you to get help if you need it.

We are going to assume that you already have a Firefox build installed, so the instructions will take that into account.

== Getting the Builds ==
* Browse to the FTP server for [ftp://ftp.mozilla.org/pub/firefox/nightly/latest-alder/ en-US builds] or [ftp://ftp.mozilla.org/pub/firefox/nightly/latest-alder-l10n/ l10n builds]
* Download the en-US build you want:
** [ftp://ftp.mozilla.org/pub/firefox/nightly/latest-alder/firefox-33.0.en-US.win32.installer.exe Windows en-US]
** [ftp://ftp.mozilla.org/pub/firefox/nightly/latest-alder/firefox-33.0.en-US.mac.dmg Mac en-US]
** [ftp://ftp.mozilla.org/pub/firefox/nightly/latest-alder/firefox-33.0.en-US.linux-i686.tar.bz2 Linux 32 bit en-US]
** [ftp://ftp.mozilla.org/pub/firefox/nightly/latest-alder/firefox-33.0.en-US.linux-x86_64.tar.bz2 Linux 64 bit en-US]

== Install it ==
=== Windows ===
* Run the executable installer
* Click through the prompts until you get to the "Setup Type" screen. You must choose either "Typical" or "Custom" Choose '''Custom'''
* On the next screen, the installer will ask where to put the files, use a different path than the one suggested. One easy mechanism is to replace the last element of the path with the word "alder". You'll want to remember this path for future steps
* Uncheck the options to create icons on the next panel. We will create those later.
* Finish the install

=== Mac ===
* Open Finder
* Go to Applications
* Make a new directory called Alder
* Open the dmg file that you downloaded
* Drag the "nightly" icon into the Alder directory

=== Linux ===
* Uncompress the archive into any directory you'd like to use
<pre>
$> mkdir ~/alder
$> cd alder
$> tar -jxf <filename_you_downloaded>
</pre>

== Creating a Profile For It ==
You need to create a new profile for this. Creating a new profile does not harm your existing data in any way.
Now, you have the build downloaded. The build will ask to update each day. It is recommended that you keep the build up to date. If you don't see an update prompt, you can always force updates by going to the Help menu inside the Alder Nightly browser and select "About Nightly"

There are several helpful pages on MDN and SUMO for starting Firefox builds in new profiles. These pages will certainly help you quite a bit if you're unfamiliar with the process. You will need to find the firefox executable which is in the folder that you installed Alder to up in the installation instructions, so keep that in mind when you are following these steps. Note that the SUMO and MDN articles cover the same content, so use whichever is easier for you. Additionally, I recommend using 'alder' (no quotes) as the name of the profile in the steps below, choose the one for your OS:
* [https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles General Profile Management Instructions from Sumo]
* [https://developer.mozilla.org/en-US/docs/Mozilla/Multiple_Firefox_Profiles General Profile Management Instructions from MDN]
* [https://developer.mozilla.org/en-US/docs/Mozilla/Multiple_Firefox_Profiles#Windows Steps for Windows Profile]
* [http://sonnygill.net/mac/mac-multiple-firefox-profiles/ Steps for Mac Profile]
* [https://developer.mozilla.org/en-US/docs/Mozilla/Multiple_Firefox_Profiles#Linux Steps for Linux Profile]

== Congrats! ==
Now you are an official Alder Nightly tester! We will be sending out specific assignments for you to try out with this build. In between assignments, feel free to use this build and report anything that seems wrong to our mailing list: tilesfeedback@mozilla.com

The Alder Nightly build will automatically prompt you for updates each day when you start it up. If it does not you can force it to check for updates:
* Start Alder Nightly
* Go to the Help Menu, choose About Nightly
* Click the "Check for Updates" button or the "Apply Updates" button.
* If you don't see a button, you might see "already up to date" in which case you're fine! :-)

We ask that you make sure the build is up to date before trying any of the assignments that we'll be sending out.

Note that when you are running the Alder Nightly Browser, you ''won't'' have access to your history or your saved passwords, or addons or themes. That's because you're running in a different profile from the one you normally use with your Firefox. This also means that anything you do in Alder does not affect your normal Firefox. 

== Have Trouble? ==
If you have trouble with any of the steps above, feel free to ping the folks at support@mozilla.com to get a hand.

== Found an Issue? ==
Think you've found a bug? Feel free to write it up and send to fxdecade@mozilla.com. We will look over it and let you know. You're also welcome to stop by in #qa and chat with someone there (good candidates are ctalbert, tracy, kbrosnan, kairo, juanb, or mschifer).

We look forward to working with you to make Alder something we will all be proud of.

Tiles/Data Collection

2014-09-09T16:56:48Z

Mardak: /* Directory and Enhanced tiles */

== Current Status ==

In the current Firefox 33 and later prerelease builds, the following information is sent to Mozilla about [[Tiles|tiles]]:

On viewing the new-tab page, blocking a tile, clicking a tile or an associated sponsored link, pinning or unpinning a tile, the following information is sent:
=== History tiles ===
* the position of the tile
* the pin status of the tile
* the tile frecency
* No tile ID or URL information is sent for history tiles

=== Directory and Enhanced tiles ===

the information for history tiles, plus
* The tile ID (which encodes the tile destination)
* A signal (empty string; no URL) if the tile is enhanced

=== Other Details ===

A previous version of these patches would send the full URL for enhanced tiles. This URL submission has been removed.

The data is sent via a SSL connection. Key-pinning this connection is tracked by {{bug|1030135}}. No extra tracking cookies are set by the server for this ping.

When the data is received, the IP address is geo-encoded: the IP address is not stored on Mozilla’s servers.

Descriptions for the payload schemas for the pings can be found [https://github.com/oyiptong/onyx/blob/master/README.md here]

== Prospecting Future Tile Partners ==

In addition to continuous data collection required for partners, we also want to collect information about current user history tiles, to provide business guidance about which sites are most valuable to our users for picking both Directory and Enhanced Tiles.

Proposal:
* Run a limited-time experiment in the beta channel to collect information about the top history site information.
* Rather than sending any URLs, prepare in advance a potential list of top sites or partners as a whitelist of sites. Only send information about tiles on this whitelist, and only send the TLD+2, not the full URL. This will avoid sending many kinds of personal URLs.

This prospecting experiment is tracked in {{bug|1062708}}

Tiles/Data Collection

2014-09-09T16:56:09Z

Mardak: /* Directory and Enhanced tiles */ enhanced signal

== Current Status ==

In the current Firefox 33 and later prerelease builds, the following information is sent to Mozilla about [[Tiles|tiles]]:

On viewing the new-tab page, blocking a tile, clicking a tile or an associated sponsored link, pinning or unpinning a tile, the following information is sent:
=== History tiles ===
* the position of the tile
* the pin status of the tile
* the tile frecency
* No tile ID or URL information is sent for history tiles

=== Directory and Enhanced tiles ===

the information for history tiles, plus
* The tile ID (which encodes the tile destination)
* A signal (empty string; no url) that the tile is enhanced

=== Other Details ===

A previous version of these patches would send the full URL for enhanced tiles. This URL submission has been removed.

The data is sent via a SSL connection. Key-pinning this connection is tracked by {{bug|1030135}}. No extra tracking cookies are set by the server for this ping.

When the data is received, the IP address is geo-encoded: the IP address is not stored on Mozilla’s servers.

Descriptions for the payload schemas for the pings can be found [https://github.com/oyiptong/onyx/blob/master/README.md here]

== Prospecting Future Tile Partners ==

In addition to continuous data collection required for partners, we also want to collect information about current user history tiles, to provide business guidance about which sites are most valuable to our users for picking both Directory and Enhanced Tiles.

Proposal:
* Run a limited-time experiment in the beta channel to collect information about the top history site information.
* Rather than sending any URLs, prepare in advance a potential list of top sites or partners as a whitelist of sites. Only send information about tiles on this whitelist, and only send the TLD+2, not the full URL. This will avoid sending many kinds of personal URLs.

This prospecting experiment is tracked in {{bug|1062708}}

Tiles/Data Collection

2014-09-09T16:52:40Z

Mardak: /* History tiles */ explicit mentioning of no tile id for history

== Current Status ==

In the current Firefox 33 and later prerelease builds, the following information is sent to Mozilla about [[Tiles|tiles]]:

On viewing the new-tab page, blocking a tile, clicking a tile or an associated sponsored link, pinning or unpinning a tile, the following information is sent:
=== History tiles ===
* the position of the tile
* the pin status of the tile
* the tile frecency
* No tile ID or URL information is sent for history tiles

=== Directory and Enhanced tiles ===

the information for history tiles, plus
* The tile ID (which encodes the tile destination)

=== Other Details ===

A previous version of these patches would send the full URL for enhanced tiles. This URL submission has been removed.

The data is sent via a SSL connection. Key-pinning this connection is tracked by {{bug|1030135}}. No extra tracking cookies are set by the server for this ping.

When the data is received, the IP address is geo-encoded: the IP address is not stored on Mozilla’s servers.

Descriptions for the payload schemas for the pings can be found [https://github.com/oyiptong/onyx/blob/master/README.md here]

== Prospecting Future Tile Partners ==

In addition to continuous data collection required for partners, we also want to collect information about current user history tiles, to provide business guidance about which sites are most valuable to our users for picking both Directory and Enhanced Tiles.

Proposal:
* Run a limited-time experiment in the beta channel to collect information about the top history site information.
* Rather than sending any URLs, prepare in advance a potential list of top sites or partners as a whitelist of sites. Only send information about tiles on this whitelist, and only send the TLD+2, not the full URL. This will avoid sending many kinds of personal URLs.

This prospecting experiment is tracked in {{bug|1062708}}

WeeklyUpdates/2014-06-02

2014-06-02T17:03:03Z

Mardak: /* Introducing New Hires */ tim spurway new hire

{{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]] ==

* Big thanks to [https://mozillians.org/u/rctgamer3/ rctgamer] for identifying and sending us hundreds of spam accounts on AMO.
* Thanks to the newest member of the volunteer app review team, [https://mozillians.org/u/jaipradeesh/ Jaipradeesh], who has reviewed nearly 350 apps since joining three weeks ago.
* Thanks to add-on reviewers [https://mozillians.org/u/diegocr/ Diego] and [https://mozillians.org/u/TheOne/ Andreas], who reviewed hundreds of add-ons last week, making a huge dent in the queue.

== Upcoming Events ==

=== This Week ===

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

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
* Mozillians Town Hall - 2014 Goals - Invest in Sustainability - https://wiki.mozilla.org/2014#Invest_in_Sustainability 9:00am - 10:00am PT on Air Mozilla or live in SF/MV.

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

* [https://etherpad.mozilla.org/b2g-qa-bug-bash-06052014 Firefox OS 2.0 Bug Bash] - Try out new 2.0 features!
** Time: 4pm - 7pm PST
** IRC: #fxosqa
** Vidyo: [https://v.mozilla.com/flex.html?roomdirect.html&key=nL4PESn1IaVh QA]
** Dial In: 1-800-707-2533, pass: 369, room: x9245

* Mozilla Recruiting is hosting a virtual Skills Lab on "How to make your Referrals successful" and will be around to answer your questions on all things Recruiting. no sign up required, just join vidyo room Mozilla_Recruiting or the irc channel #recruiting
** Time: 8:30am PDT-10:00am PDT

=== 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:''

=== [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 ===
''Speaker Location: Mountain View''

One of Mozilla’s goals for this year is to [[2014#Enable_Communities_that_have_Impact|increase the number of active contributors by 10x]]. That means that many new people will be joining the community and we want to make sure they have a positive experience.

To help new contributors understand more about what they’re getting involved with, we’ve posted [https://groups.google.com/forum/#!topic/mozilla.governance/yN4V-lYJH8c draft text of a new volunteer agreement to Governance]. I wanted to share the discussion to get feedback and input.

Before reading through it, I’d like to be clear about a couple of points:

* This is not intended to be a document that people will sign

* This is not something that applies to existing contributors, just to new people who are joining the community

=== 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"
|-
! [https://mozillians.org/u/USERNAME 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
|-
| David Boswell
| Community Building on the People Team
| @mozilla.org email addresses for volunteers
| San Francisco
| No
| No
| https://groups.google.com/forum/#!topic/mozilla.governance/UsgIRmdv9Kk
|-
| Sean Rich
| Make IT awesome
| Removing roadblocks to productivity --> Broken Communication Channels
| San Francisco
| No
| No
| https://etherpad.mozilla.org/1i8Z0jT7Zk
|-
| Erica Jostedt
| The PR Team
| Who we are, how we can help you, how you can help us
| San Francisco
| Yes
| Yes
|
|-
| Mardi Douglass
| Communications
| Mozillians and World Cup madness
| Remote
| No
| No
|
|-
| Darren Herman
| Content Services
| Tiles experiment in Nightly
| San Francisco if his flight arrives on time (if it doesn't, Johnath will take this)
| No
| No
|
|-
| Jim Cook
| Finance
| Q1 2014 Product Activity Survey
| Mountain View
| No
| No
| https://wiki.mozilla.org/Productactivitysurvey
|
|}

= 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?''
|-

|-
| Chris Manchester
| Jonathan Griffin
| Toronto
| Remote - NYC
| Adding structured logging to our test harnesses
|-
| Aaron Thornburgh
| Madhava Enros
| Toronto
| SF
| Firefox User-Experience, focused on Content Services
|-
| Tim Spurway
| Olivier Yiptong (for Ed Lee)
| Toronto
| Toronto
| Firefox Engineering + UP Research, focused on Content Services
|-
| MJ Kelly
| Winston Bowden
| San Francisco
| Seattle
| Digital content strategy for owned media (social media, email engagement, snippets)
|-
|}

== 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?''
|-

| Vladislav Filippov
| Zach Carter
| San Francisco
| San Francisco
| Identity/Services Engineering
|-
| Gregory A. Norcie
| Chris Karlof
| San Francisco
| San Francisco
| Identity/Services Engineering
|-
| Andrew Greenfield
| Winnie Aoieong
| San Francisco
| San Francisco
| Finance
|-
| Nathan Braswell
| Sean Stangl
| Mountain View
| Mountain View
| JavaScript Engine
|-
| Guptha Rajagopal
| Jeff Walden
| Mountain View
| Mountain View
| Javascript Engine
|-
| Kate Glazko
| Marcia Knous
| Mountain View
| Mountain View
| Mobile QA
|-
| Jeremy Poulin
| Nick Hurley
| Mountain View
| Mountain View
| Networking
|-
| Jonathan Morton
| Kyle Huey
| San Francisco
| San Francisco
| Platform Engineering
|-
| Susanna Bowen
| Daniel Holbert
| San Francisco
| San Francisco
| Platform Engineering - Layout
|-
| Benjamin Brittian
| Eric Rescorla
| Mountain View
| Mountain View
| Platform Engineering: WebRTC
|-
| Ian Connolly
| Hal Wine
| San Francisco
| San Francisco
| Release Engineering
|-
| Carlos Diaz-Padron
| Jed Parsons
| San Francisco
| San Francisco
| Services Engineering
|-
| Dylan Wong
| Raymond Etornam Agbeame
| Mountain View
| Mountain View
| Web QA
|-
| Sathyanarayanan Gunasekaran
| Nick Desaulniers
| Mountain View
| Mountain View
| Emscripten
|-
| Basar Koc
| Tim Terriberry
| Mountain View
| Mountain View
| Research
|-
| Catalin Badea
| John Schoenick
| Mountain View
| Mountain View
| Platform Engineering: DOM
|-
| Eli Kariv
| Jean Collings
| Mountain View
| San Francisco
| Community Engagement
|-
| Melissa Martin
| Jean Collings
| Mountain View
| San Francisco
| User Engagement
|-
| Alex Wissmann
| Marcus Cavanugh
| Mountain View
| San Francisco
| FF OS Engineer
|-
| Martin McDonough
| Randall Barker
| Mountain View
| Mountain View
| Platform Engineering: Mobile
|-
| Georgios Kontaxis
| Monica Chew
| Mountain View
| San Francisco
| Privacy and Security
|-
| Kamyar Ardekani
| Ilana Segall
| Mountain View
| San Francisco
| User Research-Quantitative
|-
| Lu Wang
| Alon Zakai
| Mountain View
| Mountain View
| Research
|-
| Piyush Waradpande
| Yvan Boily
| Mountain View
| Mountain View
| Security Assurance
|-
| Marcell Vazquez-Chanlatte
| Laura Thomson
| Mountain View
| Mountain View
| Web Eng.
|-
| James Hobin
| Gregor Wagner
| Mountain View
| San Francisco
|-
| Harsh Pathak
| Camilo Viecco
| Mountain View
| Mountain View
| Privacy Engineering
|-
|}

= <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 ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

==== bugzilla.mozilla.org ====
Notable changes to [https://bugzilla.mozilla.org/ bugzilla.mozilla.org] during the last week:
* {{bug|1014374}} CSS files are now served concatenated and minified
* {{bug|1003950}} Abusive accounts can now be automatically disabled
* {{bug|1009216}} Clicking on the 'Whiteboard' field label now takes you to a wiki page describing common whiteboard tags
[[BMO/Recent_Changes|All changes]].

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

==== Social Support ====

=== Policy & Advocacy ===
* '''Personal Democracy Forum''' — The Policy & Advocacy crew is headed to [https://personaldemocracy.com/ PDF] in New York this week. We are a sponsor of the conference and will be running a session on ‘Re-Imagining Advocacy to Protect the Free and Open Web’. Together with panelists from EFF, Fight for the Future, Engine Advocacy and Facebook, we are hoping to share and hear new ideas to boost the global open web movement.
* '''Reset the Net''' — This week is the anniversary of the first revelations from Edward Snowden about NSA surveillance, in which the world learned that the NSA is exploiting weak links in Internet security to spy on the entire world, twisting the Internet we love into something it was never meant to be. A year ago, Mozilla helped launch StopWatchingUs to apply pressure to leaders for reform. This year, Mozilla will be joining with Fight for the Future and a host of other organizations to launch a new effort called ‘Reset the Net’ to stop mass surveillance by building proven security into the everyday internet. We encourage all Mozillians to visit ResetTheNet to learn about security tools and steps they can take, including take the pledge for better security on June 5th.

Summit2013/Sessions/Sunday

2013-10-04T04:11:11Z

Mardak: /* UP: User Personalization */

==1:15 - 2:30pm==

===Distributed Leadership and decision making===

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A well-facilitated inquiry and skillshare on distributed leadership. Skills Learned: Leadership, Conflict Resolution, Facilitating distributed meetings/planning/group actions. Potential Outline of Session:
# Nature of Mozilla -- one pillar is human capability; more mozillians moving the mission forward
# history of the huge chunks of mozilla that people made up on on their own and we incorporated into the centralized piece
# Some issues with distributed decision-mkaing: risk, mistakes, surprise, messiness
# What do we do now: how we build more APIs to the centralized part of mozilla?

Facilitators:
:Brussels: Laura Thomson, Ioana Chiorean
:Toronto: [https://mozillians.org/en-US/u/regnard/ Regnard Raquedan], Lukas Blakk
:Santa Clara: Alina Mierlus, Vineel Reddy Pindi

Session Etherpad: http://mzl.la/17Zxktf

===Ideas into Action: Next steps for me and my team===

Location:
:Brussels: Studio 310
:Toronto: Conference F
:Santa Clara: Grand Ballroom Salon E

Track: Purpose and Strategy

Four breakout sessions with a joint shareback round. Determine what winning looks like as measured by Mozilla's four pillars of activity. Tools, roadmap and things you can do when you return home. How you can adapt the 3-year plan to your local context and the projects you care about. How you can multiply the mission. Skills Learned: Metrics, Building Open into your Project, How to Identify the NoM in your ideas & highlight/promote/grow those

Facilitators:
:Brussels: Karen Rudnitski (Sr Product Manager for Firefox for Android)
:Toronto: Larissa Shapiro, Selena Deckelmann
:Santa Clara: [https://mozillians.org/u/ernestchiang/ Ernest Chiang] (One of the [https://reps.mozilla.org/u/dwchiang/ Mozilla Reps], SUMO Leader in MozTW Mozilla Taiwan community)

Session Etherpad: http://mzl.la/1enyki5

===Designing your project for participation===

Location:
:Brussels: The Arc
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: People and Process

Nearly all projects will benefit from community involvement; however, there are different approaches and best practices that can better enable a project for wider contributions. This session will capture best practices and challenges to build a project with community involvement.

Facilitators:
:'''Brussels''': [https://mozillians.org/u/LauraHilliger/ Laura Hilliger] (working with Mozilla Reps to help them deliver #teachtheweb professional development content)
:'''Toronto''': [https://mozillians.org/u/deaves/ David Eaves] (creator of the community building workshops that includes a 'Designing your project for participation' module) or [https://mozillians.org/u/emmairwin/ Emma Irwin] (One of the Mozilla Reps who will be delivering the community building workshop content), Jess Klein
:'''Santa Clara''': [https://mozillians.org/u/bkerensa/ Benjamin Kerensa] (One of the Mozilla Reps, delivering the community building workshop content) and [https://mozillians.org/u/Debloper/ Soumya Deb] (Leader in Mozilla India)

Session Etherpad: http://mzl.la/17Zxm4A

===Community tools - what do we currently have===

Location:
:Brussels: Studio 313/315
:Toronto: Windsor West
:Santa Clara: Portland

Track: People and Process

The topic of tooling seems to be a frequent one. Let's discuss the needs of the various members of the community and determine if there are shared tools in which we as a community should invest.

Facilitators:
:Brussels: [https://mozillians.org/u/jdm/ Josh Matthews], [https://mozillians.org/u/williamr/ William Reynolds] (members of the Community Building Systems Working Group)
:Toronto: [https://mozillians.org/u/mhoye/ Michael Hoye], [https://mozillians.org/u/r1cky/ Ricky Rosario] (members of the Community Building Systems Working Group)
:Santa Clara: [https://mozillians.org/u/pierros/ Pierros Papadeas] (members of the Community Building Systems Working Group)

Session Etherpad: http://mzl.la/1enyrua

===Working with corporate (closed) partners===

Location:
:Brussels: Studio 311/312
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: People and Process

How to stay open at Mozilla while meeting our needs: Creating a shared understanding of how Mozilla can work in a closed environment and a roadmap for introducing open concepts to our partners.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/lmandel/ Lawrence Mandel], Lukas Blakk, Bhavana Bajaj
*Brussels: Dietrich Ayala, [https://mozillians.org/en-US/u/mcote/ Mark Côté], Chris Lee
*Santa Clara: [https://mozillians.org/en-US/u/cpeterson/ Chris Peterson], Alex Keybl

Session Etherpad: http://mzl.la/1enywhl

===Workshop on Contributor recognition guide===

Location:
:Brussels: Studio 314/316
:Toronto: Windsor East
:Santa Clara: Seattle

Track: People and Process

Workshop to share tips and tricks for how recognize contributors to your project that would cover badges, swag, events and more. Also hack on the draft Recognition Guide at https://wiki.mozilla.org/Contribute/Recognition

Facilitator:
:Brussels: Michelle Marovich (Lead Recruiter) and Lizz Noonan (Brand Campaign Coordinator/Creative Contribute Community Co-manager)
:Toronto: [https://mozillians.org/en-US/u/gueroJeff/ Jeff Beatty] (Community Building for l10n)
:Santa Clara: [https://mozillians.org/en-US/u/rosana/ Rosana Ardila] (Community Builder for SUMO)

Session Etherpad: http://mzl.la/17ZxsJo

===Moderated discussion on how we will think about product opportunities in the cloud===

Location:
:Brussels: Studio 210
:Toronto: Conference D&E
:Santa Clara: Prospector Suite A

Track: Product and Technology

Mozilla has a proud history of championing user control of data, but there are both huge user benefits and competitive pressures to having some cloud-enabled data and services. How should Mozilla approach this problem in a way that pushes the mission forward while being pragmatic to the needs of the market?

Facilitators:
:Brussels: Lloyd Hilaiel
:Toronto: John Jensen
:Santa Clara: Toby Elliott, Vishy Krishnamoorthy

Session Etherpad: http://mzl.la/17ZxrFk

===The future of web gaming===

Location:
:Brussels: Studio 211/212
:Toronto: Conference B
:Santa Clara: Prospector Suite B

Track: Product and Technology

The web is poised to become a platform for games, which opens up opportunities for new markets and independent developers. With WebGL, asm.js, and key web API's like Pointer Lock, Audio, and Video, Mozilla is making the future of web gaming a reality. Find out where we are and join us thinking about where to go from here.

Facilitators:
:Brussels: Vlad Vukicevic
:Toronto: Martin Best
:Santa Clara: Alon Zakai

Session Etherpad: http://mzl.la/17Zxu3U

===UP: User Personalization===

Time: 1:15 - 2:30pm '''(Brussels only)'''

Location:
:Brussels: Studio 214/216
:Toronto: Windsor West '''on [[Summit2013/Sessions/Saturday#UP:_User_Personalization|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector Suite A '''on [[Summit2013/Sessions/Friday#UP:_User_Personalization|Friday]] @1:00 - 2:15pm, 2:45 - 4:00pm'''

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-up

Summit2013/Sessions/Saturday

2013-10-04T04:10:56Z

Mardak: /* UP: User Personalization */

==1:30 - 3:30pm==

===Practicing Open===

'''Location''':
:'''Brussels''': Studio 313/315
:'''Toronto''': Windsor West
:'''Santa Clara''': Prospector Suite B

'''Track''': Purpose and Strategy 
[[File:MozFest crowd shot -- 9940882226 b8464450be o.jpg|700px]]

<blockquote>What does “working in the open” mean for you? How do we do it at Mozilla — and where do we need to adapt, adjust and improve?</blockquote>

In this session, we'll dive into discussion around these key themes -- and then start hacking together on something more concrete: a new FAQ guide on "How to work open at Mozilla."

We'll surface key questions around where working open seems difficult or confusing in your own work, creating a lasting resource for ongoing use and follow-up after the Summit.

The emphasis is on how we work, collaborate, and practice open on a daily basis. Mozilla is committed to open not only in terms of technology -- but also in terms of a unique way of working together. Join us to celebrate, elevate and help document this key part of our culture, history and future. [http://openmatt.org/2013/10/02/open_mozilla/ (more)]

'''Facilitators''':
<ul>
<li>Toronto: David Humphrey [https://twitter.com/humphd (@humphd)] or Matt Thompson [https://twitter.com/OpenMatt (@OpenMatt)]</li>
<li>Brussels: Stefania IoanaChiorean [https://twitter.com/ioana_cis (@ioana_cis)]</li>
<li>Santa Clara: Sakina Groth [https://twitter.com/SakinaGroth" (@SakinaGroth)]</li>
</ul>

'''Session Etherpad + agenda''': http://mzl.la/17ZwUmQ 
'''Session blog post''': http://mzl.la/open_mozilla

===TBD===

Location:
:Brussels: Hall 300
:Toronto: Conference B
:Santa Clara: Grand Ballroom Salon AB

Track: Purpose and Strategy

Facilitators:
:Brussels:
:Toronto:
:Santa Clara:

Session Etherpad:

===Building a Framework to enable Mozilla to effectively communicate across our community===

Location:
:Brussels: The Arc
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: People and Process

How does Mozilla hold a discussion on a particular topic that allows expression of positives and negatives in a productive way? This session will build the Mozilla Framework for how to invite feedback, manage the conversation and ensure all parties are acknowledged regardless of their view of the issue.

Facilitators:
:Brussels:[https://mozillians.org/u/gerv/ Gervase Markham], [https://mozillians.org/en-US/u/bsmedberg/ Benjamin Smedberg]
:Toronto: [https://mozillians.org/en-US/u/LDeCoursy/ Lainie Decoursy], [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)], [https://mozillians.org/en-US/u/Kensie/ Majken Connor]
:Santa Clara: [https://mozillians.org/en-US/u/Mardi/ Mardi Douglass], [https://mozillians.org/en-US/u/echardac/ Emily Chardac], William Quiviger

Session Etherpad: http://mzl.la/17ZwWeu

===Defining and Packaging a Mozilla Core experience for onboarding===

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference C
:Santa Clara: Grand Ballroom Salon E

Track: People & Process

How do we create an experience that captures the history of Mozilla, our values, and what makes us unique in a way that we can transfer these items to new Mozillians and even our partners?

Facilitators:
:Brussels: [https://mozillians.org/u/nukeador/ Rubén Martín [:Nukeador]] (one of the Mozilla Hispano mentors that runs the onboarding process for new contributors), Tobias Leingruber
:Toronto: Amie Tyrrel, Amira Dhalla
:Santa Clara: [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil] {{NeedCoFacilitator}}

Session Etherpad: http://mzl.la/17Zx1Pf

===What would a million Mozillians do?===
¿Qué harían un millon de Mozilleros? [Toronto: EN & ES]

Location:
:Brussels: Studio 311/312
:Toronto: Conference D&E
:Santa Clara: Seattle

Track: Purpose & Strategy

Working Narrative: A creative, "blue sky" session to imagine new kinds of contributors

Facilitators:
:Brussels: [https://mozillians.org/u/kinger/ Brian King] (Community Manager for Europe), [https://mozillians.org/u/henx/ Henrik Mitsch], [https://mozillians.org/u/nethahussain/ Netha Hussain], [https://mozillians.org/u/thornet/ Michelle Thorne], [https://mozillians.org/u/FuzzyFox/ William Duyck]
:Toronto: Marc Lesser, [https://mozillians.org/u/margaretschroeder/ Margaret Schroeder], [https://mozillians.org/en-US/u/MRomaine/ Melissa Romaine] (en Español)
:Santa Clara: [https://mozillians.org/u/davidwboswell/ David Boswell] and [https://mozillians.org/u/williamq/ William Quiviger]

Session Etherpad:http://mzl.la/1enxmmc

===Developing empathy for your users===

Location:
:Brussels: Studio 213/215
:Toronto: Conference G
:Santa Clara: Portland

Track: Product & Technology

A workshop where you learn how to easily make sure that the products you make are as appreciated as you think they should be.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co] , Maureen Hanratty
:Toronto: Cori Schauer
:Santa Clara: [https://mozillians.org/en-US/u/lkenzig/ Lindsay Kenzig], Maria Sandberg

Session Etherpad: http://mzl.la/1enxqlU

===Understanding the Servo strategy===

Location:
:Brussels: Studio 211/212
:Toronto: Willow Room East
:Santa Clara: Newport Beach

Track: Product & Technology

Web browsers were designed around yesterday's reality of computer hardware. Servo is a rethinking of the architecture of browsers to accommodate the hardware of today and tomorrow: multiple CPU's and powerful GPU's, and with limited power consumption. What's more, Servo is being built in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust], a new programming language designed to support faster and safer development practices.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/jdm/ Josh Matthews]
:Toronto: [https://mozillians.org/en-US/u/metajack/ Jack Moffitt]
:Santa Clara: Patrick Walton

Session Etherpad: http://mzl.la/17Zx5yz

===Growing Stakeholders in the Web===

Cancelled. Will be replaced with an open session.

==4:00 - 6:00pm==

===Imagining a Mozilla-Wide Open Badges System + OBI 101===

Location:
:Brussels: Studio 313/315
:Toronto: Conference F on the Mezzanine Level
:Santa Clara: Prospector B

Track: Product and Technology

Working Narrative:

The Open Badges Infrastructure makes learning and credentialing work like the Web. Through digital badges, we can build an ecosystem of open learning with stackable, information-based credentials. Open Badges can be used for recognizing and communicating skills and achievements, building reputation and community, and finding peers and hires.

In this session, we'll provide a brief badges 101 and then explore the opportunity for Mozilla badges for the global community of Mozillians. Together we'll ask: What badges would prove compelling to contributors, staff and community members? What needs to be built and provided to support this large, cohesive system? What are immediate next steps for making these badges real and recognizable? Is now the right time for a Mozilla-wide badge system?

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/timriches Tim Riches], [https://mozillians.org/en-US/u/emgollie// Emily Goligoski]
:Toronto: [https://mozillians.org/en-US/u/megan Meg Cole], [https://mozillians.org/en-US/u/erin/ Erin Knight], [https://mozillians.org/en-US/u/kerri Kerri Lemoie], [https://mozillians.org/en-US/u/Damian Damian Ewens]
:Santa Clara: [https://mozillians.org/en-US/u/threeqube/ Sunny Lee], [https://mozillians.org/en-US/u/carlacasilli/ Carla Casilli]

Session Etherpad: http://mzl.la/1enyN3W

===Designing for our users not ourselves===

Location:
:Brussels: The Arc
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon CD

Track: Product & Technology

Introduction to our users - who they are, what they do, what they need, and how Mozilla can do this.

Facilitators:
:Cori Schauer will be main facilitator for this, and will coordinate the other facilitators.
:Brussels: [https://mozillians.org/en-US/u/gpetrie/ Gemma Petrie] & Madhava Zhenshuo & [https://mozillians.org/en-US/u/dstrohmeier/ Dominik Strohmeier]
:Toronto: Cori Schauer, [https://mozillians.org/en-US/u/clarkbw/ Bryan Clark] (possibly Gregg Lind)
:Santa Clara: Bill Selman

Session Etherpad: http://mzl.la/1enxtOr

===Strategies of industry players and competing effectively===

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon AB

Track: Product & Technology

Powerful interests are creating silos of content and private walled gardens on the web. What can Mozilla do to open these silos up or create new more open alternatives? How do we need to understand how these competitors work for markets and consumers?

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/pfinch/ Patrick Finch] {{NeedCoFacilitator}}
:Toronto: [https://mozillians.org/en-US/u/kev/ Kev Needham], John Jensen
:Santa Clara: Irina Sandu, Ria Joy, Sandip Kamat

Session Etherpad:http://mzl.la/1enxOko

===Understanding web developers===

Location:
:Brussels: Studio 213/215
:Toronto: Conference D&E
:Santa Clara: Santa Barbara

Track: Product & Technology

Web developers are a key community for Mozilla. Our competitors are building sophisticated developer tools, API's, and platform technologies. How can we maintain a close and symbiotic relationship with web developers? How do we meet their needs, and how do we get them signed up for Mozilla's mission?

Facilitators:
:Brussels: Jeff Griffiths
:Toronto: Stormy Peters
:Santa Clara: Christian Heilmann

Session Etherpad: http://mzl.la/1enxVMI

===How do we scale up our innovation capacity?===

Location:
:Brussels: Studio 311/312
:Toronto: Conference C
:Santa Clara: Seattle

Track: Product and Technology

If we're to have the kind of massive impact on the internet that we hope to, we have to ask ourselves whether our structure and processes will get us there. If we want to facilitate innovation at the edges and focus on recognizing good ideas rather than having them, how should we relate to web innovators around the world?

Facilitators:
:Brussels: David Ascher
:Toronto: Simon Wex
:Santa Clara: Dan Mosedale

Session Etherpad: http://mzl.la/1enxJ00

===We're building a global movement of Webmakers: Join us===

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference B
:Santa Clara: Grand Ballroom Salon E

Track: Product and Technology

Webmaker is the brand that we're using to show a new generation of web citizens that the web is theirs to grab, shape and remix. We'll show you what that looks like with an ad hoc maker party. Come learn to build web pages and multimedia with Mozilla's awesome Webmaker tools. Or if you have skills to share, learn to be a Webmaker mentor.

Facilitators:

:Brussels: [https://mozillians.org/en-US/u/codekat/ Kat Braybrooke], [https://mozillians.org/u/thornet/ Michelle Thorne]
:Toronto: Chris Lawrence, Amira Dhalla, Matt Thompson
:Santa Clara: Brett Gaylor, [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil], Jacob Caggiano, Yoe One Ariestya Niovitta

Session Etherpad:http://mzl.la/1enxYYR

===Enter The Compartment - Gecko's Script Security Architecture Explained===

Location:
:Brussels: Studio 211/212

A talk and Q&A session targeted at frontend, extension, and
WebAPI developers.

XPConnect has historically been one of the scariest and most
mysterious parts of Gecko. In the past few years, we've made major
architectural advancements that vastly simplify things and give us
very powerful invariants. Nevertheless, knowledge about our script
architecture tends to be concentrated in the heads of a few very busy
people. This session aims to spread some of that knowledge.

We'll begin a brief history of script security on the web, and move
into an in-depth description of Mozilla's script architecture. Topics
include Compartments, Principals, Security Wrappers, Xrays, DOM bindings,
__exposedProps__, Expandos, and more. Come with questions!

Facilitators:

:Brussels: Bobby Holley

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-saturday-enterthecomparment

===UP: User Personalization===

Time: 4:00pm - 6:00pm '''(Toronto only)'''

Location:
:Brussels: Studio 214/216 '''on [[Summit2013/Sessions/Sunday#UP:_User_Personalization|Sunday]] @1:15pm - 2:30pm'''
:Toronto: Windsor West
:Santa Clara: Prospector Suite A '''on [[Summit2013/Sessions/Friday#UP:_User_Personalization|Friday]] @1:00 - 2:15pm, 2:45 - 4:00pm'''

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-up

Summit2013/Sessions/Friday

2013-10-04T04:10:44Z

Mardak: /* UP: User Personalization */

==1-2:15pm AND 2:45 - 4:00pm==

===Ecosystems in our Image===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: Purpose and Strategy

Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems.
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?

Facilitators:
:Brussels: David Ascher, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: Chris Lawrence, Ben Moskowitz
:Santa Clara: Alina Mierlus, [https://mozillians.org/en-US/u/erika/ Erika Owens]

Session Etherpad: http://mzl.la/1ent7a9

===The Web We Want===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: The Arc
:Toronto: Conference B
:Santa Clara: Seattle

Track: Purpose and Strategy

A large, interactive session to explore the web we're championing. What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?

Facilitators:
:Santa Clara: [https://mozillians.org/en-US/u/asa/ Asa Dotzler], [[User:Tantek|Tantek Çelik]]
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co], [[User:Aking|Ozten]], [https://mozillians.org/en-US/u/AlisonW/ AlisonW]
:Toronto: Potch, [https://mozillians.org/en-US/u/firetoad/ Mike Collins], Dan Sinker

Session Etherpad: http://mzl.la/15nyhNz

Session Hashtag: #mozwww

Afterwards:
* I've proposed an [[IndieWeb]] Hackspace on the [[Summit2013/Experiences#HackSpaces|Summit2013 Experiences]] wiki page for those that want to actively hack on their own websites and create the web we want by example. - [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]])

===Building a Web Literate World===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 213/215
:Toronto: Conference D&E
:Santa Clara: Newport Beach

Track: Purpose and Strategy

The Webmaker Community is changing the face of education through collaborative, participatory events, kick ass tools and relevant learning activities for creativity and learning. At the same time, they're building a more Web Literate world by helping people understand that you don't have to be a programmer to understand the technical and social infrastructures of the Web.

In this session, we'll play games and discuss how building a web literate world is integral to everything we do, not just as Mozilla, but as people. We'll discuss how Mozilla is making this not only possible - but easily accessible through open tools, learning activities, invitations to participate in the discussions, guidance and direction and invention, innovation and inspiration. And we'll prototype ways for you to get involved.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/juliarvallera/ Julia Vallera], [https://mozillians.org/en-US/u/emmairwin/ Emma Irwin]
*Santa Clara, Sandraghassen Subbaraya Pillai, [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil], Vineel Reddy Pindi, [https://mozillians.org/en-US/u/Ben/ Benny Chandra], Faye Tandog, Christos Bacharakis, Lawrence Kisuuki
*Brussels: Ibrahima SARR, [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger]

Session Etherpad: http://mzl.la/17ZwqNo

===What does "Mozillian" mean?===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?

Facilitators:
:Brussels: [https://mozillians.org/u/gerv/ Gervase Markham], Ioana Chiorean
:Toronto: Guillermo Movia, [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)- Will do second session @2:45]
:Santa Clara: Sujith Reddy (would like co facilitator), Alex Lakatos

Session Etherpad: http://mzl.la/15nymAM

===Firefox OS in 2014 and Beyond===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 311+312
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: Product and Technology

The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features. It is going to be a highly interactive session where attendees will participate in discussions and providing inputs.

Facilitators:
:Brussels: Chris Lee, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski], Vik Iya
:Santa Clara: Sandip Kamat, Christian Heilmann

Session Etherpad: http://mzl.la/17Zws7Y

===Privacy, Security, and Data: Pragmatic Innovations for Users and the Web===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 211/212
:Toronto: Conference G
:Santa Clara: Grand Ballroom Salon E

Track: Product and Technology

A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/MozStacy/ Stacy Martin] / [https://mozillians.org/en-US/u/grobinson/ Garrett Robinson] / [https://mozillians.org/en-US/u/psiinon/ Simon Bennetts]
:Toronto: [https://mozillians.org/en-US/u/fowler/ Alex Fowler] / [https://mozillians.org/en-US/u/monicachew/ Monica Chew] / [https://mozillians.org/en-US/u/yvan/ Yvan Boily]
:Santa Clara: [https://mozillians.org/en-US/u/alinah/ Alina Hua] / [https://mozillians.org/en-US/u/geekboy/ Sid Stamm] / [https://mozillians.org/en-US/u/joes/ Joe Stevenson]

Session Etherpad: http://mzl.la/17Zwvki

===Amplifying Mozilla: From Wearing T-Shirts to Sharing Online===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm

Location:
:Brussels: Studio 313/315
:Toronto: Conference F
:Santa Clara: Portland

Track: Purpose and Strategy

A look into the emotional connection that explains why we wear our brand proudly. This session will explore what the Mozilla brand means for different individuals and will focus on how Mozillians can share the brand with the world.

Facilitators (Coordinated by [https://mozillians.org/en-US/u/pscanlon/ Pete Scanlon]):
:Brussels: Ioana Chiorean, [https://mozillians.org/en-US/u/gregoryjost/ Gregory Jost]
:Toronto: [https://mozillians.org/en-US/u/wbowden/ Winston Bowden], [https://mozillians.org/en-US/u/mthayer/ Michaela Thayer], [https://mozillians.org/en-US/u/jessemontano/ Jesse Montano]
:Santa Clara: [https://mozillians.org/en-US/u/sgroth/ Sakina Groth], [https://mozillians.org/en-US/u/AlexLakatos/ Alex Lakatos]

Session Etherpad: http://mzl.la/AmplifyingMozillaSession

===UP: User Personalization===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm '''(Santa Clara only)'''

Location:
:Brussels: Studio 214/216 '''on [[Summit2013/Sessions/Sunday#UP:_User_Personalization|Sunday]] @1:15pm - 2:30pm'''
:Toronto: Windsor West '''on [[Summit2013/Sessions/Saturday#UP:_User_Personalization|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector Suite A

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-up

Summit2013/Sessions/Saturday

2013-10-04T03:29:37Z

Mardak: /* 4:00 - 6:00pm */

==1:30 - 3:30pm==

===Practicing Open===

'''Location''':
:'''Brussels''': Studio 313/315
:'''Toronto''': Windsor West
:'''Santa Clara''': Prospector Suite B

'''Track''': Purpose and Strategy 
[[File:MozFest crowd shot -- 9940882226 b8464450be o.jpg|700px]]

<blockquote>What does “working in the open” mean for you? How do we do it at Mozilla — and where do we need to adapt, adjust and improve?</blockquote>

In this session, we'll dive into discussion around these key themes -- and then start hacking together on something more concrete: a new FAQ guide on "How to work open at Mozilla."

We'll surface key questions around where working open seems difficult or confusing in your own work, creating a lasting resource for ongoing use and follow-up after the Summit.

The emphasis is on how we work, collaborate, and practice open on a daily basis. Mozilla is committed to open not only in terms of technology -- but also in terms of a unique way of working together. Join us to celebrate, elevate and help document this key part of our culture, history and future. [http://openmatt.org/2013/10/02/open_mozilla/ (more)]

'''Facilitators''':
<ul>
<li>Toronto: David Humphrey [https://twitter.com/humphd (@humphd)] or Matt Thompson [https://twitter.com/OpenMatt (@OpenMatt)]</li>
<li>Brussels: Stefania IoanaChiorean [https://twitter.com/ioana_cis (@ioana_cis)]</li>
<li>Santa Clara: Sakina Groth [https://twitter.com/SakinaGroth" (@SakinaGroth)]</li>
</ul>

'''Session Etherpad + agenda''': http://mzl.la/17ZwUmQ 
'''Session blog post''': http://mzl.la/open_mozilla

===TBD===

Location:
:Brussels: Hall 300
:Toronto: Conference B
:Santa Clara: Grand Ballroom Salon AB

Track: Purpose and Strategy

Facilitators:
:Brussels:
:Toronto:
:Santa Clara:

Session Etherpad:

===Building a Framework to enable Mozilla to effectively communicate across our community===

Location:
:Brussels: The Arc
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: People and Process

How does Mozilla hold a discussion on a particular topic that allows expression of positives and negatives in a productive way? This session will build the Mozilla Framework for how to invite feedback, manage the conversation and ensure all parties are acknowledged regardless of their view of the issue.

Facilitators:
:Brussels:[https://mozillians.org/u/gerv/ Gervase Markham], [https://mozillians.org/en-US/u/bsmedberg/ Benjamin Smedberg]
:Toronto: [https://mozillians.org/en-US/u/LDeCoursy/ Lainie Decoursy], [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)], [https://mozillians.org/en-US/u/Kensie/ Majken Connor]
:Santa Clara: [https://mozillians.org/en-US/u/Mardi/ Mardi Douglass], [https://mozillians.org/en-US/u/echardac/ Emily Chardac], William Quiviger

Session Etherpad: http://mzl.la/17ZwWeu

===Defining and Packaging a Mozilla Core experience for onboarding===

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference C
:Santa Clara: Grand Ballroom Salon E

Track: People & Process

How do we create an experience that captures the history of Mozilla, our values, and what makes us unique in a way that we can transfer these items to new Mozillians and even our partners?

Facilitators:
:Brussels: [https://mozillians.org/u/nukeador/ Rubén Martín [:Nukeador]] (one of the Mozilla Hispano mentors that runs the onboarding process for new contributors), Tobias Leingruber
:Toronto: Amie Tyrrel, Amira Dhalla
:Santa Clara: [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil] {{NeedCoFacilitator}}

Session Etherpad: http://mzl.la/17Zx1Pf

===What would a million Mozillians do?===
¿Qué harían un millon de Mozilleros? [Toronto: EN & ES]

Location:
:Brussels: Studio 311/312
:Toronto: Conference D&E
:Santa Clara: Seattle

Track: Purpose & Strategy

Working Narrative: A creative, "blue sky" session to imagine new kinds of contributors

Facilitators:
:Brussels: [https://mozillians.org/u/kinger/ Brian King] (Community Manager for Europe), [https://mozillians.org/u/henx/ Henrik Mitsch], [https://mozillians.org/u/nethahussain/ Netha Hussain], [https://mozillians.org/u/thornet/ Michelle Thorne], [https://mozillians.org/u/FuzzyFox/ William Duyck]
:Toronto: Marc Lesser, [https://mozillians.org/u/margaretschroeder/ Margaret Schroeder], [https://mozillians.org/en-US/u/MRomaine/ Melissa Romaine] (en Español)
:Santa Clara: [https://mozillians.org/u/davidwboswell/ David Boswell] and [https://mozillians.org/u/williamq/ William Quiviger]

Session Etherpad:http://mzl.la/1enxmmc

===Developing empathy for your users===

Location:
:Brussels: Studio 213/215
:Toronto: Conference G
:Santa Clara: Portland

Track: Product & Technology

A workshop where you learn how to easily make sure that the products you make are as appreciated as you think they should be.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co] , Maureen Hanratty
:Toronto: Cori Schauer
:Santa Clara: [https://mozillians.org/en-US/u/lkenzig/ Lindsay Kenzig], Maria Sandberg

Session Etherpad: http://mzl.la/1enxqlU

===Understanding the Servo strategy===

Location:
:Brussels: Studio 211/212
:Toronto: Willow Room East
:Santa Clara: Newport Beach

Track: Product & Technology

Web browsers were designed around yesterday's reality of computer hardware. Servo is a rethinking of the architecture of browsers to accommodate the hardware of today and tomorrow: multiple CPU's and powerful GPU's, and with limited power consumption. What's more, Servo is being built in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust], a new programming language designed to support faster and safer development practices.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/jdm/ Josh Matthews]
:Toronto: [https://mozillians.org/en-US/u/metajack/ Jack Moffitt]
:Santa Clara: Patrick Walton

Session Etherpad: http://mzl.la/17Zx5yz

===Growing Stakeholders in the Web===

Cancelled. Will be replaced with an open session.

==4:00 - 6:00pm==

===Imagining a Mozilla-Wide Open Badges System + OBI 101===

Location:
:Brussels: Studio 313/315
:Toronto: Conference F on the Mezzanine Level
:Santa Clara: Prospector B

Track: Product and Technology

Working Narrative:

The Open Badges Infrastructure makes learning and credentialing work like the Web. Through digital badges, we can build an ecosystem of open learning with stackable, information-based credentials. Open Badges can be used for recognizing and communicating skills and achievements, building reputation and community, and finding peers and hires.

In this session, we'll provide a brief badges 101 and then explore the opportunity for Mozilla badges for the global community of Mozillians. Together we'll ask: What badges would prove compelling to contributors, staff and community members? What needs to be built and provided to support this large, cohesive system? What are immediate next steps for making these badges real and recognizable? Is now the right time for a Mozilla-wide badge system?

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/timriches Tim Riches], [https://mozillians.org/en-US/u/emgollie// Emily Goligoski]
:Toronto: [https://mozillians.org/en-US/u/megan Meg Cole], [https://mozillians.org/en-US/u/erin/ Erin Knight], [https://mozillians.org/en-US/u/kerri Kerri Lemoie], [https://mozillians.org/en-US/u/Damian Damian Ewens]
:Santa Clara: [https://mozillians.org/en-US/u/threeqube/ Sunny Lee], [https://mozillians.org/en-US/u/carlacasilli/ Carla Casilli]

Session Etherpad: http://mzl.la/1enyN3W

===Designing for our users not ourselves===

Location:
:Brussels: The Arc
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon CD

Track: Product & Technology

Introduction to our users - who they are, what they do, what they need, and how Mozilla can do this.

Facilitators:
:Cori Schauer will be main facilitator for this, and will coordinate the other facilitators.
:Brussels: [https://mozillians.org/en-US/u/gpetrie/ Gemma Petrie] & Madhava Zhenshuo & [https://mozillians.org/en-US/u/dstrohmeier/ Dominik Strohmeier]
:Toronto: Cori Schauer, [https://mozillians.org/en-US/u/clarkbw/ Bryan Clark] (possibly Gregg Lind)
:Santa Clara: Bill Selman

Session Etherpad: http://mzl.la/1enxtOr

===Strategies of industry players and competing effectively===

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon AB

Track: Product & Technology

Powerful interests are creating silos of content and private walled gardens on the web. What can Mozilla do to open these silos up or create new more open alternatives? How do we need to understand how these competitors work for markets and consumers?

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/pfinch/ Patrick Finch] {{NeedCoFacilitator}}
:Toronto: [https://mozillians.org/en-US/u/kev/ Kev Needham], John Jensen
:Santa Clara: Irina Sandu, Ria Joy, Sandip Kamat

Session Etherpad:http://mzl.la/1enxOko

===Understanding web developers===

Location:
:Brussels: Studio 213/215
:Toronto: Conference D&E
:Santa Clara: Santa Barbara

Track: Product & Technology

Web developers are a key community for Mozilla. Our competitors are building sophisticated developer tools, API's, and platform technologies. How can we maintain a close and symbiotic relationship with web developers? How do we meet their needs, and how do we get them signed up for Mozilla's mission?

Facilitators:
:Brussels: Jeff Griffiths
:Toronto: Stormy Peters
:Santa Clara: Christian Heilmann

Session Etherpad: http://mzl.la/1enxVMI

===How do we scale up our innovation capacity?===

Location:
:Brussels: Studio 311/312
:Toronto: Conference C
:Santa Clara: Seattle

Track: Product and Technology

If we're to have the kind of massive impact on the internet that we hope to, we have to ask ourselves whether our structure and processes will get us there. If we want to facilitate innovation at the edges and focus on recognizing good ideas rather than having them, how should we relate to web innovators around the world?

Facilitators:
:Brussels: David Ascher
:Toronto: Simon Wex
:Santa Clara: Dan Mosedale

Session Etherpad: http://mzl.la/1enxJ00

===We're building a global movement of Webmakers: Join us===

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference B
:Santa Clara: Grand Ballroom Salon E

Track: Product and Technology

Webmaker is the brand that we're using to show a new generation of web citizens that the web is theirs to grab, shape and remix. We'll show you what that looks like with an ad hoc maker party. Come learn to build web pages and multimedia with Mozilla's awesome Webmaker tools. Or if you have skills to share, learn to be a Webmaker mentor.

Facilitators:

:Brussels: [https://mozillians.org/en-US/u/codekat/ Kat Braybrooke], [https://mozillians.org/u/thornet/ Michelle Thorne]
:Toronto: Chris Lawrence, Amira Dhalla, Matt Thompson
:Santa Clara: Brett Gaylor, [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil], Jacob Caggiano, Yoe One Ariestya Niovitta

Session Etherpad:http://mzl.la/1enxYYR

===Enter The Compartment - Gecko's Script Security Architecture Explained===

Location:
:Brussels: Studio 211/212

A talk and Q&A session targeted at frontend, extension, and
WebAPI developers.

XPConnect has historically been one of the scariest and most
mysterious parts of Gecko. In the past few years, we've made major
architectural advancements that vastly simplify things and give us
very powerful invariants. Nevertheless, knowledge about our script
architecture tends to be concentrated in the heads of a few very busy
people. This session aims to spread some of that knowledge.

We'll begin a brief history of script security on the web, and move
into an in-depth description of Mozilla's script architecture. Topics
include Compartments, Principals, Security Wrappers, Xrays, DOM bindings,
__exposedProps__, Expandos, and more. Come with questions!

Facilitators:

:Brussels: Bobby Holley

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-saturday-enterthecomparment

===UP: User Personalization===

Time: 4:00pm - 6:00pm '''(Toronto only)'''

Location:
:Brussels: Studio 214/216 '''on [[Summit2013/Sessions/Sunday#UP:_User_Personalization|Sunday]] @1:15pm - 2:30pm'''
:Toronto: Conference F
:Santa Clara: Prospector Suite A '''on [[Summit2013/Sessions/Friday#UP:_User_Personalization|Friday]] @1:00 - 2:15pm, 2:45 - 4:00pm'''

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-up

Summit2013/Sessions/Friday

2013-10-04T03:29:13Z

Mardak: /* UP: User Personalization */

==1-2:15pm AND 2:45 - 4:00pm==

===Ecosystems in our Image===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: Purpose and Strategy

Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems.
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?

Facilitators:
:Brussels: David Ascher, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: Chris Lawrence, Ben Moskowitz
:Santa Clara: Alina Mierlus, [https://mozillians.org/en-US/u/erika/ Erika Owens]

Session Etherpad: http://mzl.la/1ent7a9

===The Web We Want===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: The Arc
:Toronto: Conference B
:Santa Clara: Seattle

Track: Purpose and Strategy

A large, interactive session to explore the web we're championing. What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?

Facilitators:
:Santa Clara: [https://mozillians.org/en-US/u/asa/ Asa Dotzler], [[User:Tantek|Tantek Çelik]]
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co], [[User:Aking|Ozten]], [https://mozillians.org/en-US/u/AlisonW/ AlisonW]
:Toronto: Potch, [https://mozillians.org/en-US/u/firetoad/ Mike Collins], Dan Sinker

Session Etherpad: http://mzl.la/15nyhNz

Session Hashtag: #mozwww

Afterwards:
* I've proposed an [[IndieWeb]] Hackspace on the [[Summit2013/Experiences#HackSpaces|Summit2013 Experiences]] wiki page for those that want to actively hack on their own websites and create the web we want by example. - [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]])

===Building a Web Literate World===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 213/215
:Toronto: Conference D&E
:Santa Clara: Newport Beach

Track: Purpose and Strategy

The Webmaker Community is changing the face of education through collaborative, participatory events, kick ass tools and relevant learning activities for creativity and learning. At the same time, they're building a more Web Literate world by helping people understand that you don't have to be a programmer to understand the technical and social infrastructures of the Web.

In this session, we'll play games and discuss how building a web literate world is integral to everything we do, not just as Mozilla, but as people. We'll discuss how Mozilla is making this not only possible - but easily accessible through open tools, learning activities, invitations to participate in the discussions, guidance and direction and invention, innovation and inspiration. And we'll prototype ways for you to get involved.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/juliarvallera/ Julia Vallera], [https://mozillians.org/en-US/u/emmairwin/ Emma Irwin]
*Santa Clara, Sandraghassen Subbaraya Pillai, [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil], Vineel Reddy Pindi, [https://mozillians.org/en-US/u/Ben/ Benny Chandra], Faye Tandog, Christos Bacharakis, Lawrence Kisuuki
*Brussels: Ibrahima SARR, [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger]

Session Etherpad: http://mzl.la/17ZwqNo

===What does "Mozillian" mean?===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?

Facilitators:
:Brussels: [https://mozillians.org/u/gerv/ Gervase Markham], Ioana Chiorean
:Toronto: Guillermo Movia, [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)- Will do second session @2:45]
:Santa Clara: Sujith Reddy (would like co facilitator), Alex Lakatos

Session Etherpad: http://mzl.la/15nymAM

===Firefox OS in 2014 and Beyond===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 311+312
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: Product and Technology

The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features. It is going to be a highly interactive session where attendees will participate in discussions and providing inputs.

Facilitators:
:Brussels: Chris Lee, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski], Vik Iya
:Santa Clara: Sandip Kamat, Christian Heilmann

Session Etherpad: http://mzl.la/17Zws7Y

===Privacy, Security, and Data: Pragmatic Innovations for Users and the Web===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 211/212
:Toronto: Conference G
:Santa Clara: Grand Ballroom Salon E

Track: Product and Technology

A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/MozStacy/ Stacy Martin] / [https://mozillians.org/en-US/u/grobinson/ Garrett Robinson] / [https://mozillians.org/en-US/u/psiinon/ Simon Bennetts]
:Toronto: [https://mozillians.org/en-US/u/fowler/ Alex Fowler] / [https://mozillians.org/en-US/u/monicachew/ Monica Chew] / [https://mozillians.org/en-US/u/yvan/ Yvan Boily]
:Santa Clara: [https://mozillians.org/en-US/u/alinah/ Alina Hua] / [https://mozillians.org/en-US/u/geekboy/ Sid Stamm] / [https://mozillians.org/en-US/u/joes/ Joe Stevenson]

Session Etherpad: http://mzl.la/17Zwvki

===Amplifying Mozilla: From Wearing T-Shirts to Sharing Online===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm

Location:
:Brussels: Studio 313/315
:Toronto: Conference F
:Santa Clara: Portland

Track: Purpose and Strategy

A look into the emotional connection that explains why we wear our brand proudly. This session will explore what the Mozilla brand means for different individuals and will focus on how Mozillians can share the brand with the world.

Facilitators (Coordinated by [https://mozillians.org/en-US/u/pscanlon/ Pete Scanlon]):
:Brussels: Ioana Chiorean, [https://mozillians.org/en-US/u/gregoryjost/ Gregory Jost]
:Toronto: [https://mozillians.org/en-US/u/wbowden/ Winston Bowden], [https://mozillians.org/en-US/u/mthayer/ Michaela Thayer], [https://mozillians.org/en-US/u/jessemontano/ Jesse Montano]
:Santa Clara: [https://mozillians.org/en-US/u/sgroth/ Sakina Groth], [https://mozillians.org/en-US/u/AlexLakatos/ Alex Lakatos]

Session Etherpad: http://mzl.la/AmplifyingMozillaSession

===UP: User Personalization===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm '''(Santa Clara only)'''

Location:
:Brussels: Studio 214/216 '''on [[Summit2013/Sessions/Sunday#UP:_User_Personalization|Sunday]] @1:15pm - 2:30pm'''
:Toronto: Conference F '''on [[Summit2013/Sessions/Saturday#UP:_User_Personalization|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector Suite A

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-up

Summit2013/Sessions/Sunday

2013-10-04T03:29:07Z

Mardak: /* UP: User Personalization */

==1:15 - 2:30pm==

===Distributed Leadership and decision making===

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A well-facilitated inquiry and skillshare on distributed leadership. Skills Learned: Leadership, Conflict Resolution, Facilitating distributed meetings/planning/group actions. Potential Outline of Session:
# Nature of Mozilla -- one pillar is human capability; more mozillians moving the mission forward
# history of the huge chunks of mozilla that people made up on on their own and we incorporated into the centralized piece
# Some issues with distributed decision-mkaing: risk, mistakes, surprise, messiness
# What do we do now: how we build more APIs to the centralized part of mozilla?

Facilitators:
:Brussels: Laura Thomson, Ioana Chiorean
:Toronto: [https://mozillians.org/en-US/u/regnard/ Regnard Raquedan], Lukas Blakk
:Santa Clara: Alina Mierlus, Vineel Reddy Pindi

Session Etherpad: http://mzl.la/17Zxktf

===Ideas into Action: Next steps for me and my team===

Location:
:Brussels: Studio 310
:Toronto: Conference F
:Santa Clara: Grand Ballroom Salon E

Track: Purpose and Strategy

Four breakout sessions with a joint shareback round. Determine what winning looks like as measured by Mozilla's four pillars of activity. Tools, roadmap and things you can do when you return home. How you can adapt the 3-year plan to your local context and the projects you care about. How you can multiply the mission. Skills Learned: Metrics, Building Open into your Project, How to Identify the NoM in your ideas & highlight/promote/grow those

Facilitators:
:Brussels: Karen Rudnitski (Sr Product Manager for Firefox for Android)
:Toronto: Larissa Shapiro, Selena Deckelmann
:Santa Clara: [https://mozillians.org/u/ernestchiang/ Ernest Chiang] (One of the [https://reps.mozilla.org/u/dwchiang/ Mozilla Reps], SUMO Leader in MozTW Mozilla Taiwan community)

Session Etherpad: http://mzl.la/1enyki5

===Designing your project for participation===

Location:
:Brussels: The Arc
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: People and Process

Nearly all projects will benefit from community involvement; however, there are different approaches and best practices that can better enable a project for wider contributions. This session will capture best practices and challenges to build a project with community involvement.

Facilitators:
:'''Brussels''': [https://mozillians.org/u/LauraHilliger/ Laura Hilliger] (working with Mozilla Reps to help them deliver #teachtheweb professional development content)
:'''Toronto''': [https://mozillians.org/u/deaves/ David Eaves] (creator of the community building workshops that includes a 'Designing your project for participation' module) or [https://mozillians.org/u/emmairwin/ Emma Irwin] (One of the Mozilla Reps who will be delivering the community building workshop content), Jess Klein
:'''Santa Clara''': [https://mozillians.org/u/bkerensa/ Benjamin Kerensa] (One of the Mozilla Reps, delivering the community building workshop content) and [https://mozillians.org/u/Debloper/ Soumya Deb] (Leader in Mozilla India)

Session Etherpad: http://mzl.la/17Zxm4A

===Community tools - what do we currently have===

Location:
:Brussels: Studio 313/315
:Toronto: Windsor West
:Santa Clara: Portland

Track: People and Process

The topic of tooling seems to be a frequent one. Let's discuss the needs of the various members of the community and determine if there are shared tools in which we as a community should invest.

Facilitators:
:Brussels: [https://mozillians.org/u/jdm/ Josh Matthews], [https://mozillians.org/u/williamr/ William Reynolds] (members of the Community Building Systems Working Group)
:Toronto: [https://mozillians.org/u/mhoye/ Michael Hoye], [https://mozillians.org/u/r1cky/ Ricky Rosario] (members of the Community Building Systems Working Group)
:Santa Clara: [https://mozillians.org/u/pierros/ Pierros Papadeas] (members of the Community Building Systems Working Group)

Session Etherpad: http://mzl.la/1enyrua

===Working with corporate (closed) partners===

Location:
:Brussels: Studio 311/312
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: People and Process

How to stay open at Mozilla while meeting our needs: Creating a shared understanding of how Mozilla can work in a closed environment and a roadmap for introducing open concepts to our partners.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/lmandel/ Lawrence Mandel], Lukas Blakk, Bhavana Bajaj
*Brussels: Dietrich Ayala, [https://mozillians.org/en-US/u/mcote/ Mark Côté], Chris Lee
*Santa Clara: [https://mozillians.org/en-US/u/cpeterson/ Chris Peterson], Alex Keybl

Session Etherpad: http://mzl.la/1enywhl

===Workshop on Contributor recognition guide===

Location:
:Brussels: Studio 314/316
:Toronto: Windsor East
:Santa Clara: Seattle

Track: People and Process

Workshop to share tips and tricks for how recognize contributors to your project that would cover badges, swag, events and more. Also hack on the draft Recognition Guide at https://wiki.mozilla.org/Contribute/Recognition

Facilitator:
:Brussels: Michelle Marovich (Lead Recruiter) and Lizz Noonan (Brand Campaign Coordinator/Creative Contribute Community Co-manager)
:Toronto: [https://mozillians.org/en-US/u/gueroJeff/ Jeff Beatty] (Community Building for l10n)
:Santa Clara: [https://mozillians.org/en-US/u/rosana/ Rosana Ardila] (Community Builder for SUMO)

Session Etherpad: http://mzl.la/17ZxsJo

===Moderated discussion on how we will think about product opportunities in the cloud===

Location:
:Brussels: Studio 210
:Toronto: Conference D&E
:Santa Clara: Prospector Suite A

Track: Product and Technology

Mozilla has a proud history of championing user control of data, but there are both huge user benefits and competitive pressures to having some cloud-enabled data and services. How should Mozilla approach this problem in a way that pushes the mission forward while being pragmatic to the needs of the market?

Facilitators:
:Brussels: Lloyd Hilaiel
:Toronto: John Jensen
:Santa Clara: Toby Elliott, Vishy Krishnamoorthy

Session Etherpad: http://mzl.la/17ZxrFk

===The future of web gaming===

Location:
:Brussels: Studio 211/212
:Toronto: Conference B
:Santa Clara: Prospector Suite B

Track: Product and Technology

The web is poised to become a platform for games, which opens up opportunities for new markets and independent developers. With WebGL, asm.js, and key web API's like Pointer Lock, Audio, and Video, Mozilla is making the future of web gaming a reality. Find out where we are and join us thinking about where to go from here.

Facilitators:
:Brussels: Vlad Vukicevic
:Toronto: Martin Best
:Santa Clara: Alon Zakai

Session Etherpad: http://mzl.la/17Zxu3U

===UP: User Personalization===

Time: 1:15 - 2:30pm '''(Brussels only)'''

Location:
:Brussels: Studio 214/216
:Toronto: Conference F '''on [[Summit2013/Sessions/Saturday#UP:_User_Personalization|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector Suite A '''on [[Summit2013/Sessions/Friday#UP:_User_Personalization|Friday]] @1:00 - 2:15pm, 2:45 - 4:00pm'''

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-up

Summit2013/Sessions/Sunday

2013-10-04T03:27:28Z

Mardak: /* 1:15 - 2:30pm */ add UP

==1:15 - 2:30pm==

===Distributed Leadership and decision making===

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A well-facilitated inquiry and skillshare on distributed leadership. Skills Learned: Leadership, Conflict Resolution, Facilitating distributed meetings/planning/group actions. Potential Outline of Session:
# Nature of Mozilla -- one pillar is human capability; more mozillians moving the mission forward
# history of the huge chunks of mozilla that people made up on on their own and we incorporated into the centralized piece
# Some issues with distributed decision-mkaing: risk, mistakes, surprise, messiness
# What do we do now: how we build more APIs to the centralized part of mozilla?

Facilitators:
:Brussels: Laura Thomson, Ioana Chiorean
:Toronto: [https://mozillians.org/en-US/u/regnard/ Regnard Raquedan], Lukas Blakk
:Santa Clara: Alina Mierlus, Vineel Reddy Pindi

Session Etherpad: http://mzl.la/17Zxktf

===Ideas into Action: Next steps for me and my team===

Location:
:Brussels: Studio 310
:Toronto: Conference F
:Santa Clara: Grand Ballroom Salon E

Track: Purpose and Strategy

Four breakout sessions with a joint shareback round. Determine what winning looks like as measured by Mozilla's four pillars of activity. Tools, roadmap and things you can do when you return home. How you can adapt the 3-year plan to your local context and the projects you care about. How you can multiply the mission. Skills Learned: Metrics, Building Open into your Project, How to Identify the NoM in your ideas & highlight/promote/grow those

Facilitators:
:Brussels: Karen Rudnitski (Sr Product Manager for Firefox for Android)
:Toronto: Larissa Shapiro, Selena Deckelmann
:Santa Clara: [https://mozillians.org/u/ernestchiang/ Ernest Chiang] (One of the [https://reps.mozilla.org/u/dwchiang/ Mozilla Reps], SUMO Leader in MozTW Mozilla Taiwan community)

Session Etherpad: http://mzl.la/1enyki5

===Designing your project for participation===

Location:
:Brussels: The Arc
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: People and Process

Nearly all projects will benefit from community involvement; however, there are different approaches and best practices that can better enable a project for wider contributions. This session will capture best practices and challenges to build a project with community involvement.

Facilitators:
:'''Brussels''': [https://mozillians.org/u/LauraHilliger/ Laura Hilliger] (working with Mozilla Reps to help them deliver #teachtheweb professional development content)
:'''Toronto''': [https://mozillians.org/u/deaves/ David Eaves] (creator of the community building workshops that includes a 'Designing your project for participation' module) or [https://mozillians.org/u/emmairwin/ Emma Irwin] (One of the Mozilla Reps who will be delivering the community building workshop content), Jess Klein
:'''Santa Clara''': [https://mozillians.org/u/bkerensa/ Benjamin Kerensa] (One of the Mozilla Reps, delivering the community building workshop content) and [https://mozillians.org/u/Debloper/ Soumya Deb] (Leader in Mozilla India)

Session Etherpad: http://mzl.la/17Zxm4A

===Community tools - what do we currently have===

Location:
:Brussels: Studio 313/315
:Toronto: Windsor West
:Santa Clara: Portland

Track: People and Process

The topic of tooling seems to be a frequent one. Let's discuss the needs of the various members of the community and determine if there are shared tools in which we as a community should invest.

Facilitators:
:Brussels: [https://mozillians.org/u/jdm/ Josh Matthews], [https://mozillians.org/u/williamr/ William Reynolds] (members of the Community Building Systems Working Group)
:Toronto: [https://mozillians.org/u/mhoye/ Michael Hoye], [https://mozillians.org/u/r1cky/ Ricky Rosario] (members of the Community Building Systems Working Group)
:Santa Clara: [https://mozillians.org/u/pierros/ Pierros Papadeas] (members of the Community Building Systems Working Group)

Session Etherpad: http://mzl.la/1enyrua

===Working with corporate (closed) partners===

Location:
:Brussels: Studio 311/312
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: People and Process

How to stay open at Mozilla while meeting our needs: Creating a shared understanding of how Mozilla can work in a closed environment and a roadmap for introducing open concepts to our partners.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/lmandel/ Lawrence Mandel], Lukas Blakk, Bhavana Bajaj
*Brussels: Dietrich Ayala, [https://mozillians.org/en-US/u/mcote/ Mark Côté], Chris Lee
*Santa Clara: [https://mozillians.org/en-US/u/cpeterson/ Chris Peterson], Alex Keybl

Session Etherpad: http://mzl.la/1enywhl

===Workshop on Contributor recognition guide===

Location:
:Brussels: Studio 314/316
:Toronto: Windsor East
:Santa Clara: Seattle

Track: People and Process

Workshop to share tips and tricks for how recognize contributors to your project that would cover badges, swag, events and more. Also hack on the draft Recognition Guide at https://wiki.mozilla.org/Contribute/Recognition

Facilitator:
:Brussels: Michelle Marovich (Lead Recruiter) and Lizz Noonan (Brand Campaign Coordinator/Creative Contribute Community Co-manager)
:Toronto: [https://mozillians.org/en-US/u/gueroJeff/ Jeff Beatty] (Community Building for l10n)
:Santa Clara: [https://mozillians.org/en-US/u/rosana/ Rosana Ardila] (Community Builder for SUMO)

Session Etherpad: http://mzl.la/17ZxsJo

===Moderated discussion on how we will think about product opportunities in the cloud===

Location:
:Brussels: Studio 210
:Toronto: Conference D&E
:Santa Clara: Prospector Suite A

Track: Product and Technology

Mozilla has a proud history of championing user control of data, but there are both huge user benefits and competitive pressures to having some cloud-enabled data and services. How should Mozilla approach this problem in a way that pushes the mission forward while being pragmatic to the needs of the market?

Facilitators:
:Brussels: Lloyd Hilaiel
:Toronto: John Jensen
:Santa Clara: Toby Elliott, Vishy Krishnamoorthy

Session Etherpad: http://mzl.la/17ZxrFk

===The future of web gaming===

Location:
:Brussels: Studio 211/212
:Toronto: Conference B
:Santa Clara: Prospector Suite B

Track: Product and Technology

The web is poised to become a platform for games, which opens up opportunities for new markets and independent developers. With WebGL, asm.js, and key web API's like Pointer Lock, Audio, and Video, Mozilla is making the future of web gaming a reality. Find out where we are and join us thinking about where to go from here.

Facilitators:
:Brussels: Vlad Vukicevic
:Toronto: Martin Best
:Santa Clara: Alon Zakai

Session Etherpad: http://mzl.la/17Zxu3U

===UP: User Personalization===

Time: 1:15 - 2:30pm '''(Brussels only)'''

Location:
:Brussels: Studio 214/216
:Toronto: Conference F '''on [[Summit2013/Sessions/Saturday|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector Suite A '''on [[Summit2013/Sessions/Friday#UP:_User_Personalization|Friday]] @1:00 - 2:15pm, 2:45 - 4:00pm'''

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-up

Summit2013/Sessions/Friday

2013-10-04T03:11:40Z

Mardak: /* UP: User Personalization */

==1-2:15pm AND 2:45 - 4:00pm==

===Ecosystems in our Image===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: Purpose and Strategy

Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems.
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?

Facilitators:
:Brussels: David Ascher, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: Chris Lawrence, Ben Moskowitz
:Santa Clara: Alina Mierlus, [https://mozillians.org/en-US/u/erika/ Erika Owens]

Session Etherpad: http://mzl.la/1ent7a9

===The Web We Want===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: The Arc
:Toronto: Conference B
:Santa Clara: Seattle

Track: Purpose and Strategy

A large, interactive session to explore the web we're championing. What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?

Facilitators:
:Santa Clara: [https://mozillians.org/en-US/u/asa/ Asa Dotzler], [[User:Tantek|Tantek Çelik]]
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co], [[User:Aking|Ozten]], [https://mozillians.org/en-US/u/AlisonW/ AlisonW]
:Toronto: Potch, [https://mozillians.org/en-US/u/firetoad/ Mike Collins], Dan Sinker

Session Etherpad: http://mzl.la/15nyhNz

Session Hashtag: #mozwww

Afterwards:
* I've proposed an [[IndieWeb]] Hackspace on the [[Summit2013/Experiences#HackSpaces|Summit2013 Experiences]] wiki page for those that want to actively hack on their own websites and create the web we want by example. - [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]])

===Building a Web Literate World===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 213/215
:Toronto: Conference D&E
:Santa Clara: Newport Beach

Track: Purpose and Strategy

The Webmaker Community is changing the face of education through collaborative, participatory events, kick ass tools and relevant learning activities for creativity and learning. At the same time, they're building a more Web Literate world by helping people understand that you don't have to be a programmer to understand the technical and social infrastructures of the Web.

In this session, we'll play games and discuss how building a web literate world is integral to everything we do, not just as Mozilla, but as people. We'll discuss how Mozilla is making this not only possible - but easily accessible through open tools, learning activities, invitations to participate in the discussions, guidance and direction and invention, innovation and inspiration. And we'll prototype ways for you to get involved.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/juliarvallera/ Julia Vallera], [https://mozillians.org/en-US/u/emmairwin/ Emma Irwin]
*Santa Clara, Sandraghassen Subbaraya Pillai, [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil], Vineel Reddy Pindi, [https://mozillians.org/en-US/u/Ben/ Benny Chandra], Faye Tandog, Christos Bacharakis, Lawrence Kisuuki
*Brussels: Ibrahima SARR, [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger]

Session Etherpad: http://mzl.la/17ZwqNo

===What does "Mozillian" mean?===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?

Facilitators:
:Brussels: [https://mozillians.org/u/gerv/ Gervase Markham], Ioana Chiorean
:Toronto: Guillermo Movia, [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)- Will do second session @2:45]
:Santa Clara: Sujith Reddy (would like co facilitator), Alex Lakatos

Session Etherpad: http://mzl.la/15nymAM

===Firefox OS in 2014 and Beyond===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 311+312
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: Product and Technology

The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features. It is going to be a highly interactive session where attendees will participate in discussions and providing inputs.

Facilitators:
:Brussels: Chris Lee, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski], Vik Iya
:Santa Clara: Sandip Kamat, Christian Heilmann

Session Etherpad: http://mzl.la/17Zws7Y

===Privacy, Security, and Data: Pragmatic Innovations for Users and the Web===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 211/212
:Toronto: Conference G
:Santa Clara: Grand Ballroom Salon E

Track: Product and Technology

A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/MozStacy/ Stacy Martin] / [https://mozillians.org/en-US/u/grobinson/ Garrett Robinson] / [https://mozillians.org/en-US/u/psiinon/ Simon Bennetts]
:Toronto: [https://mozillians.org/en-US/u/fowler/ Alex Fowler] / [https://mozillians.org/en-US/u/monicachew/ Monica Chew] / [https://mozillians.org/en-US/u/yvan/ Yvan Boily]
:Santa Clara: [https://mozillians.org/en-US/u/alinah/ Alina Hua] / [https://mozillians.org/en-US/u/geekboy/ Sid Stamm] / [https://mozillians.org/en-US/u/joes/ Joe Stevenson]

Session Etherpad: http://mzl.la/17Zwvki

===Amplifying Mozilla: From Wearing T-Shirts to Sharing Online===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm

Location:
:Brussels: Studio 313/315
:Toronto: Conference F
:Santa Clara: Portland

Track: Purpose and Strategy

A look into the emotional connection that explains why we wear our brand proudly. This session will explore what the Mozilla brand means for different individuals and will focus on how Mozillians can share the brand with the world.

Facilitators (Coordinated by [https://mozillians.org/en-US/u/pscanlon/ Pete Scanlon]):
:Brussels: Ioana Chiorean, [https://mozillians.org/en-US/u/gregoryjost/ Gregory Jost]
:Toronto: [https://mozillians.org/en-US/u/wbowden/ Winston Bowden], [https://mozillians.org/en-US/u/mthayer/ Michaela Thayer], [https://mozillians.org/en-US/u/jessemontano/ Jesse Montano]
:Santa Clara: [https://mozillians.org/en-US/u/sgroth/ Sakina Groth], [https://mozillians.org/en-US/u/AlexLakatos/ Alex Lakatos]

Session Etherpad: http://mzl.la/AmplifyingMozillaSession

===UP: User Personalization===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm '''(Santa Clara only)'''

Location:
:Brussels: Studio 214/216 '''on [[Summit2013/Sessions/Sunday|Sunday]] @1:15pm - 2:30pm'''
:Toronto: Conference F '''on [[Summit2013/Sessions/Saturday|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector Suite A

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: https://etherpad.mozilla.org/summit-sessions-up

Summit2013/Sessions/Friday

2013-10-03T22:37:58Z

Mardak: /* UP: User Personalization */

==1-2:15pm AND 2:45 - 4:00pm==

===Ecosystems in our Image===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: Purpose and Strategy

Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems.
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?

Facilitators:
:Brussels: David Ascher, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: Chris Lawrence, Ben Moskowitz
:Santa Clara: Alina Mierlus, [https://mozillians.org/en-US/u/erika/ Erika Owens]

Session Etherpad: http://mzl.la/1ent7a9

===The Web We Want===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: The Arc
:Toronto: Conference B
:Santa Clara: Seattle

Track: Purpose and Strategy

A large, interactive session to explore the web we're championing. What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?

Facilitators:
:Santa Clara: [https://mozillians.org/en-US/u/asa/ Asa Dotzler], [[User:Tantek|Tantek Çelik]]
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co], [[User:Aking|Ozten]], [https://mozillians.org/en-US/u/AlisonW/ AlisonW]
:Toronto: Potch, [https://mozillians.org/en-US/u/firetoad/ Mike Collins], Dan Sinker

Session Etherpad: http://mzl.la/15nyhNz

Session Hashtag: #mozwww

Afterwards:
* I've proposed an [[IndieWeb]] Hackspace on the [[Summit2013/Experiences#HackSpaces|Summit2013 Experiences]] wiki page for those that want to actively hack on their own websites and create the web we want by example. - [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]])

===Building a Web Literate World===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 213/215
:Toronto: Conference D&E
:Santa Clara: Newport Beach

Track: Purpose and Strategy

The Webmaker Community is changing the face of education through collaborative, participatory events, kick ass tools and relevant learning activities for creativity and learning. At the same time, they're building a more Web Literate world by helping people understand that you don't have to be a programmer to understand the technical and social infrastructures of the Web.

In this session, we'll play games and discuss how building a web literate world is integral to everything we do, not just as Mozilla, but as people. We'll discuss how Mozilla is making this not only possible - but easily accessible through open tools, learning activities, invitations to participate in the discussions, guidance and direction and invention, innovation and inspiration. And we'll prototype ways for you to get involved.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/juliarvallera/ Julia Vallera], [https://mozillians.org/en-US/u/emmairwin/ Emma Irwin]
*Santa Clara, Sandraghassen Subbaraya Pillai, [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil], Vineel Reddy Pindi, [https://mozillians.org/en-US/u/Ben/ Benny Chandra], Faye Tandog, Christos Bacharakis, Lawrence Kisuuki
*Brussels: Ibrahima SARR, [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger]

Session Etherpad: http://mzl.la/17ZwqNo

===What does "Mozillian" mean?===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?

Facilitators:
:Brussels: [https://mozillians.org/u/gerv/ Gervase Markham], Ioana Chiorean
:Toronto: Guillermo Movia, [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)- Will do second session @2:45]
:Santa Clara: Sujith Reddy (would like co facilitator), Alex Lakatos

Session Etherpad: http://mzl.la/15nymAM

===Firefox OS in 2014 and Beyond===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 311+312
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: Product and Technology

The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features. It is going to be a highly interactive session where attendees will participate in discussions and providing inputs.

Facilitators:
:Brussels: Chris Lee, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski], Vik Iya
:Santa Clara: Sandip Kamat, Christian Heilmann

Session Etherpad: http://mzl.la/17Zws7Y

===Privacy, Security, and Data: Pragmatic Innovations for Users and the Web===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 211/212
:Toronto: Conference G
:Santa Clara: Grand Ballroom Salon E

Track: Product and Technology

A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/MozStacy/ Stacy Martin] / [https://mozillians.org/en-US/u/grobinson/ Garrett Robinson] / [https://mozillians.org/en-US/u/psiinon/ Simon Bennetts]
:Toronto: [https://mozillians.org/en-US/u/fowler/ Alex Fowler] / [https://mozillians.org/en-US/u/monicachew/ Monica Chew] / [https://mozillians.org/en-US/u/yvan/ Yvan Boily]
:Santa Clara: [https://mozillians.org/en-US/u/alinah/ Alina Hua] / [https://mozillians.org/en-US/u/geekboy/ Sid Stamm] / [https://mozillians.org/en-US/u/joes/ Joe Stevenson]

Session Etherpad: http://mzl.la/17Zwvki

===Amplifying Mozilla: From Wearing T-Shirts to Sharing Online===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm

Location:
:Brussels: Studio 313/315
:Toronto: Conference F
:Santa Clara: Portland

Track: Purpose and Strategy

A look into the emotional connection that explains why we wear our brand proudly. This session will explore what the Mozilla brand means for different individuals and will focus on how Mozillians can share the brand with the world.

Facilitators (Coordinated by [https://mozillians.org/en-US/u/pscanlon/ Pete Scanlon]):
:Brussels: Ioana Chiorean, [https://mozillians.org/en-US/u/gregoryjost/ Gregory Jost]
:Toronto: [https://mozillians.org/en-US/u/wbowden/ Winston Bowden], [https://mozillians.org/en-US/u/mthayer/ Michaela Thayer], [https://mozillians.org/en-US/u/jessemontano/ Jesse Montano]
:Santa Clara: [https://mozillians.org/en-US/u/sgroth/ Sakina Groth], [https://mozillians.org/en-US/u/AlexLakatos/ Alex Lakatos]

Session Etherpad: http://mzl.la/AmplifyingMozillaSession

===UP: User Personalization===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm '''(Santa Clara only)'''

Location:
:Brussels: Studio 214/216 '''on [[Summit2013/Sessions/Sunday|Sunday]] @1:15pm - 2:30pm'''
:Toronto: Conference F '''on [[Summit2013/Sessions/Saturday|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector A

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: --

Summit2013/Sessions/Friday

2013-10-03T22:37:04Z

Mardak: /* UP: User Personalization */

==1-2:15pm AND 2:45 - 4:00pm==

===Ecosystems in our Image===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: Purpose and Strategy

Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems.
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?

Facilitators:
:Brussels: David Ascher, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: Chris Lawrence, Ben Moskowitz
:Santa Clara: Alina Mierlus, [https://mozillians.org/en-US/u/erika/ Erika Owens]

Session Etherpad: http://mzl.la/1ent7a9

===The Web We Want===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: The Arc
:Toronto: Conference B
:Santa Clara: Seattle

Track: Purpose and Strategy

A large, interactive session to explore the web we're championing. What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?

Facilitators:
:Santa Clara: [https://mozillians.org/en-US/u/asa/ Asa Dotzler], [[User:Tantek|Tantek Çelik]]
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co], [[User:Aking|Ozten]], [https://mozillians.org/en-US/u/AlisonW/ AlisonW]
:Toronto: Potch, [https://mozillians.org/en-US/u/firetoad/ Mike Collins], Dan Sinker

Session Etherpad: http://mzl.la/15nyhNz

Session Hashtag: #mozwww

Afterwards:
* I've proposed an [[IndieWeb]] Hackspace on the [[Summit2013/Experiences#HackSpaces|Summit2013 Experiences]] wiki page for those that want to actively hack on their own websites and create the web we want by example. - [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]])

===Building a Web Literate World===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 213/215
:Toronto: Conference D&E
:Santa Clara: Newport Beach

Track: Purpose and Strategy

The Webmaker Community is changing the face of education through collaborative, participatory events, kick ass tools and relevant learning activities for creativity and learning. At the same time, they're building a more Web Literate world by helping people understand that you don't have to be a programmer to understand the technical and social infrastructures of the Web.

In this session, we'll play games and discuss how building a web literate world is integral to everything we do, not just as Mozilla, but as people. We'll discuss how Mozilla is making this not only possible - but easily accessible through open tools, learning activities, invitations to participate in the discussions, guidance and direction and invention, innovation and inspiration. And we'll prototype ways for you to get involved.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/juliarvallera/ Julia Vallera], [https://mozillians.org/en-US/u/emmairwin/ Emma Irwin]
*Santa Clara, Sandraghassen Subbaraya Pillai, [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil], Vineel Reddy Pindi, [https://mozillians.org/en-US/u/Ben/ Benny Chandra], Faye Tandog, Christos Bacharakis, Lawrence Kisuuki
*Brussels: Ibrahima SARR, [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger]

Session Etherpad: http://mzl.la/17ZwqNo

===What does "Mozillian" mean?===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?

Facilitators:
:Brussels: [https://mozillians.org/u/gerv/ Gervase Markham], Ioana Chiorean
:Toronto: Guillermo Movia, [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)- Will do second session @2:45]
:Santa Clara: Sujith Reddy (would like co facilitator), Alex Lakatos

Session Etherpad: http://mzl.la/15nymAM

===Firefox OS in 2014 and Beyond===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 311+312
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: Product and Technology

The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features. It is going to be a highly interactive session where attendees will participate in discussions and providing inputs.

Facilitators:
:Brussels: Chris Lee, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski], Vik Iya
:Santa Clara: Sandip Kamat, Christian Heilmann

Session Etherpad: http://mzl.la/17Zws7Y

===Privacy, Security, and Data: Pragmatic Innovations for Users and the Web===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 211/212
:Toronto: Conference G
:Santa Clara: Grand Ballroom Salon E

Track: Product and Technology

A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/MozStacy/ Stacy Martin] / [https://mozillians.org/en-US/u/grobinson/ Garrett Robinson] / [https://mozillians.org/en-US/u/psiinon/ Simon Bennetts]
:Toronto: [https://mozillians.org/en-US/u/fowler/ Alex Fowler] / [https://mozillians.org/en-US/u/monicachew/ Monica Chew] / [https://mozillians.org/en-US/u/yvan/ Yvan Boily]
:Santa Clara: [https://mozillians.org/en-US/u/alinah/ Alina Hua] / [https://mozillians.org/en-US/u/geekboy/ Sid Stamm] / [https://mozillians.org/en-US/u/joes/ Joe Stevenson]

Session Etherpad: http://mzl.la/17Zwvki

===Amplifying Mozilla: From Wearing T-Shirts to Sharing Online===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm

Location:
:Brussels: Studio 313/315
:Toronto: Conference F
:Santa Clara: Portland

Track: Purpose and Strategy

A look into the emotional connection that explains why we wear our brand proudly. This session will explore what the Mozilla brand means for different individuals and will focus on how Mozillians can share the brand with the world.

Facilitators (Coordinated by [https://mozillians.org/en-US/u/pscanlon/ Pete Scanlon]):
:Brussels: Ioana Chiorean, [https://mozillians.org/en-US/u/gregoryjost/ Gregory Jost]
:Toronto: [https://mozillians.org/en-US/u/wbowden/ Winston Bowden], [https://mozillians.org/en-US/u/mthayer/ Michaela Thayer], [https://mozillians.org/en-US/u/jessemontano/ Jesse Montano]
:Santa Clara: [https://mozillians.org/en-US/u/sgroth/ Sakina Groth], [https://mozillians.org/en-US/u/AlexLakatos/ Alex Lakatos]

Session Etherpad: http://mzl.la/AmplifyingMozillaSession

===UP: User Personalization===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm '''(Santa Clara only)'''

Location:
:Brussels: Studio 214/216 '''on [[Summit2013/Sessions/Sunday|Sunday]] @1:15pm - 2:30pm'''
:Toronto: Conference F '''on [[Summit2013/Sessions/Saturday|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and without user control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: --

Summit2013/Sessions/Friday

2013-10-03T22:36:19Z

Mardak: /* UP: User Personalization */

==1-2:15pm AND 2:45 - 4:00pm==

===Ecosystems in our Image===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: Purpose and Strategy

Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems.
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?

Facilitators:
:Brussels: David Ascher, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: Chris Lawrence, Ben Moskowitz
:Santa Clara: Alina Mierlus, [https://mozillians.org/en-US/u/erika/ Erika Owens]

Session Etherpad: http://mzl.la/1ent7a9

===The Web We Want===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: The Arc
:Toronto: Conference B
:Santa Clara: Seattle

Track: Purpose and Strategy

A large, interactive session to explore the web we're championing. What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?

Facilitators:
:Santa Clara: [https://mozillians.org/en-US/u/asa/ Asa Dotzler], [[User:Tantek|Tantek Çelik]]
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co], [[User:Aking|Ozten]], [https://mozillians.org/en-US/u/AlisonW/ AlisonW]
:Toronto: Potch, [https://mozillians.org/en-US/u/firetoad/ Mike Collins], Dan Sinker

Session Etherpad: http://mzl.la/15nyhNz

Session Hashtag: #mozwww

Afterwards:
* I've proposed an [[IndieWeb]] Hackspace on the [[Summit2013/Experiences#HackSpaces|Summit2013 Experiences]] wiki page for those that want to actively hack on their own websites and create the web we want by example. - [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]])

===Building a Web Literate World===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 213/215
:Toronto: Conference D&E
:Santa Clara: Newport Beach

Track: Purpose and Strategy

The Webmaker Community is changing the face of education through collaborative, participatory events, kick ass tools and relevant learning activities for creativity and learning. At the same time, they're building a more Web Literate world by helping people understand that you don't have to be a programmer to understand the technical and social infrastructures of the Web.

In this session, we'll play games and discuss how building a web literate world is integral to everything we do, not just as Mozilla, but as people. We'll discuss how Mozilla is making this not only possible - but easily accessible through open tools, learning activities, invitations to participate in the discussions, guidance and direction and invention, innovation and inspiration. And we'll prototype ways for you to get involved.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/juliarvallera/ Julia Vallera], [https://mozillians.org/en-US/u/emmairwin/ Emma Irwin]
*Santa Clara, Sandraghassen Subbaraya Pillai, [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil], Vineel Reddy Pindi, [https://mozillians.org/en-US/u/Ben/ Benny Chandra], Faye Tandog, Christos Bacharakis, Lawrence Kisuuki
*Brussels: Ibrahima SARR, [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger]

Session Etherpad: http://mzl.la/17ZwqNo

===What does "Mozillian" mean?===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?

Facilitators:
:Brussels: [https://mozillians.org/u/gerv/ Gervase Markham], Ioana Chiorean
:Toronto: Guillermo Movia, [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)- Will do second session @2:45]
:Santa Clara: Sujith Reddy (would like co facilitator), Alex Lakatos

Session Etherpad: http://mzl.la/15nymAM

===Firefox OS in 2014 and Beyond===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 311+312
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: Product and Technology

The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features. It is going to be a highly interactive session where attendees will participate in discussions and providing inputs.

Facilitators:
:Brussels: Chris Lee, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski], Vik Iya
:Santa Clara: Sandip Kamat, Christian Heilmann

Session Etherpad: http://mzl.la/17Zws7Y

===Privacy, Security, and Data: Pragmatic Innovations for Users and the Web===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 211/212
:Toronto: Conference G
:Santa Clara: Grand Ballroom Salon E

Track: Product and Technology

A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/MozStacy/ Stacy Martin] / [https://mozillians.org/en-US/u/grobinson/ Garrett Robinson] / [https://mozillians.org/en-US/u/psiinon/ Simon Bennetts]
:Toronto: [https://mozillians.org/en-US/u/fowler/ Alex Fowler] / [https://mozillians.org/en-US/u/monicachew/ Monica Chew] / [https://mozillians.org/en-US/u/yvan/ Yvan Boily]
:Santa Clara: [https://mozillians.org/en-US/u/alinah/ Alina Hua] / [https://mozillians.org/en-US/u/geekboy/ Sid Stamm] / [https://mozillians.org/en-US/u/joes/ Joe Stevenson]

Session Etherpad: http://mzl.la/17Zwvki

===Amplifying Mozilla: From Wearing T-Shirts to Sharing Online===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm

Location:
:Brussels: Studio 313/315
:Toronto: Conference F
:Santa Clara: Portland

Track: Purpose and Strategy

A look into the emotional connection that explains why we wear our brand proudly. This session will explore what the Mozilla brand means for different individuals and will focus on how Mozillians can share the brand with the world.

Facilitators (Coordinated by [https://mozillians.org/en-US/u/pscanlon/ Pete Scanlon]):
:Brussels: Ioana Chiorean, [https://mozillians.org/en-US/u/gregoryjost/ Gregory Jost]
:Toronto: [https://mozillians.org/en-US/u/wbowden/ Winston Bowden], [https://mozillians.org/en-US/u/mthayer/ Michaela Thayer], [https://mozillians.org/en-US/u/jessemontano/ Jesse Montano]
:Santa Clara: [https://mozillians.org/en-US/u/sgroth/ Sakina Groth], [https://mozillians.org/en-US/u/AlexLakatos/ Alex Lakatos]

Session Etherpad: http://mzl.la/AmplifyingMozillaSession

===UP: User Personalization===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm '''(Santa Clara only)'''

Location:
:Brussels: Studio 214/216 '''on [[Summit2013/Sessions/Sunday|Sunday]] @1:15pm - 2:30pm'''
:Toronto: Conference F '''on [[Summit2013/Sessions/Saturday|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector

Track: Product and Technology

Personalization is happening on the web but often done with fragmented tracking data and likely without users in control. Join a discussion on how Mozilla can make things better for everyone for a more personal web experience that respects the user.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: --

Summit2013/Sessions/Friday

2013-10-03T22:19:59Z

Mardak: /* UP: User Personalization */

==1-2:15pm AND 2:45 - 4:00pm==

===Ecosystems in our Image===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 201 A+B
:Toronto: Conference C
:Santa Clara: Santa Barbara

Track: Purpose and Strategy

Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems.
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?

Facilitators:
:Brussels: David Ascher, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: Chris Lawrence, Ben Moskowitz
:Santa Clara: Alina Mierlus, [https://mozillians.org/en-US/u/erika/ Erika Owens]

Session Etherpad: http://mzl.la/1ent7a9

===The Web We Want===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: The Arc
:Toronto: Conference B
:Santa Clara: Seattle

Track: Purpose and Strategy

A large, interactive session to explore the web we're championing. What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?

Facilitators:
:Santa Clara: [https://mozillians.org/en-US/u/asa/ Asa Dotzler], [[User:Tantek|Tantek Çelik]]
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co], [[User:Aking|Ozten]], [https://mozillians.org/en-US/u/AlisonW/ AlisonW]
:Toronto: Potch, [https://mozillians.org/en-US/u/firetoad/ Mike Collins], Dan Sinker

Session Etherpad: http://mzl.la/15nyhNz

Session Hashtag: #mozwww

Afterwards:
* I've proposed an [[IndieWeb]] Hackspace on the [[Summit2013/Experiences#HackSpaces|Summit2013 Experiences]] wiki page for those that want to actively hack on their own websites and create the web we want by example. - [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]])

===Building a Web Literate World===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 213/215
:Toronto: Conference D&E
:Santa Clara: Newport Beach

Track: Purpose and Strategy

The Webmaker Community is changing the face of education through collaborative, participatory events, kick ass tools and relevant learning activities for creativity and learning. At the same time, they're building a more Web Literate world by helping people understand that you don't have to be a programmer to understand the technical and social infrastructures of the Web.

In this session, we'll play games and discuss how building a web literate world is integral to everything we do, not just as Mozilla, but as people. We'll discuss how Mozilla is making this not only possible - but easily accessible through open tools, learning activities, invitations to participate in the discussions, guidance and direction and invention, innovation and inspiration. And we'll prototype ways for you to get involved.

Facilitators:
*Toronto: [https://mozillians.org/en-US/u/juliarvallera/ Julia Vallera], [https://mozillians.org/en-US/u/emmairwin/ Emma Irwin]
*Santa Clara, Sandraghassen Subbaraya Pillai, [https://mozillians.org/en-US/u/ankitgadgil/ Ankit Gadgil], Vineel Reddy Pindi, [https://mozillians.org/en-US/u/Ben/ Benny Chandra], Faye Tandog, Christos Bacharakis, Lawrence Kisuuki
*Brussels: Ibrahima SARR, [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger]

Session Etherpad: http://mzl.la/17ZwqNo

===What does "Mozillian" mean?===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Hall 300
:Toronto: Willow Room Centre
:Santa Clara: Grand Ballroom Salon CD

Track: Purpose and Strategy

A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?

Facilitators:
:Brussels: [https://mozillians.org/u/gerv/ Gervase Markham], Ioana Chiorean
:Toronto: Guillermo Movia, [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)- Will do second session @2:45]
:Santa Clara: Sujith Reddy (would like co facilitator), Alex Lakatos

Session Etherpad: http://mzl.la/15nymAM

===Firefox OS in 2014 and Beyond===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 311+312
:Toronto: Willow Room East
:Santa Clara: Grand Ballroom Salon AB

Track: Product and Technology

The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features. It is going to be a highly interactive session where attendees will participate in discussions and providing inputs.

Facilitators:
:Brussels: Chris Lee, [https://mozillians.org/en-US/u/wmaggs/ Bill Maggs]
:Toronto: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski], Vik Iya
:Santa Clara: Sandip Kamat, Christian Heilmann

Session Etherpad: http://mzl.la/17Zws7Y

===Privacy, Security, and Data: Pragmatic Innovations for Users and the Web===

Time: 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Location:
:Brussels: Studio 211/212
:Toronto: Conference G
:Santa Clara: Grand Ballroom Salon E

Track: Product and Technology

A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/MozStacy/ Stacy Martin] / [https://mozillians.org/en-US/u/grobinson/ Garrett Robinson] / [https://mozillians.org/en-US/u/psiinon/ Simon Bennetts]
:Toronto: [https://mozillians.org/en-US/u/fowler/ Alex Fowler] / [https://mozillians.org/en-US/u/monicachew/ Monica Chew] / [https://mozillians.org/en-US/u/yvan/ Yvan Boily]
:Santa Clara: [https://mozillians.org/en-US/u/alinah/ Alina Hua] / [https://mozillians.org/en-US/u/geekboy/ Sid Stamm] / [https://mozillians.org/en-US/u/joes/ Joe Stevenson]

Session Etherpad: http://mzl.la/17Zwvki

===Amplifying Mozilla: From Wearing T-Shirts to Sharing Online===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm

Location:
:Brussels: Studio 313/315
:Toronto: Conference F
:Santa Clara: Portland

Track: Purpose and Strategy

A look into the emotional connection that explains why we wear our brand proudly. This session will explore what the Mozilla brand means for different individuals and will focus on how Mozillians can share the brand with the world.

Facilitators (Coordinated by [https://mozillians.org/en-US/u/pscanlon/ Pete Scanlon]):
:Brussels: Ioana Chiorean, [https://mozillians.org/en-US/u/gregoryjost/ Gregory Jost]
:Toronto: [https://mozillians.org/en-US/u/wbowden/ Winston Bowden], [https://mozillians.org/en-US/u/mthayer/ Michaela Thayer], [https://mozillians.org/en-US/u/jessemontano/ Jesse Montano]
:Santa Clara: [https://mozillians.org/en-US/u/sgroth/ Sakina Groth], [https://mozillians.org/en-US/u/AlexLakatos/ Alex Lakatos]

Session Etherpad: http://mzl.la/AmplifyingMozillaSession

===UP: User Personalization===

Time: 1:00 - 2:15pm, 2:45 - 4:00pm '''(Santa Clara only)'''

Location:
:Brussels: Studio 214/216 '''on [[Summit2013/Sessions/Sunday|Sunday]] @1:15pm - 2:30pm'''
:Toronto: Conference F '''on [[Summit2013/Sessions/Saturday|Saturday]] @4:00pm - 6:00pm'''
:Santa Clara: Prospector

Track: --

--

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/fligtar/ Justin Scott]
:Toronto: [https://mozillians.org/en-US/u/oyiptong/ Olivier Yiptong]
:Santa Clara: [https://mozillians.org/en-US/u/Mardak/ Ed Lee], [https://mozillians.org/en-US/u/maksik/ Maxim Zhilyaev]

Session Etherpad: --