Consider packaging FlyWeb UI for Fennec as opt-in add-on on AMO for Beta and Release

NEW
Unassigned

Status

()

Core
Networking
a year ago
6 months ago

People

(Reporter: mconley, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-would-take])

(Reporter)

Description

a year ago
This was kar's idea for attempting to expose FlyWeb to a larger audience.

The current plan is to land FlyWeb UI code on Nightly for Fennec within a system add-on. That system add-on is cleared to ride up the trains as far as Aurora, but then it will hold there as the team iterates and shops the technology around to enthusiasts, developers, etc.

While it's holding on Nightly and Aurora, the platform support for FlyWeb is likely going to ride up through Beta and to Release, even though it will be entirely inert without its UI.

kar suggested that once this occurs, we _also_ ship the system add-on as a normal add-on to users on Beta and Release on AMO, to increase audience exposure, and give the opportunity for people not using Nightly and Aurora the opportunity to participate.
Whiteboard: [necko-would-take]
You need to log in before you can comment on or make changes to this bug.