Confirmed users
613
edits
Firefox/AddOns/Status/20150929: Difference between revisions
Firefox/AddOns/Status/20150929 (view source)
Revision as of 13:34, 30 September 2015
, 30 September 2015→Overall Project Health - YELLOW: updated
(...) |
(→Overall Project Health - YELLOW: updated) |
||
| Line 5: | Line 5: | ||
* The great news is that we've now got a dedicated developer team, developer relations and community team, all in one place (Firefox) working on Add-ons for Firefox. We're yellow because these folks are hitting the ground running, already trying to catch up for the time when we were not as well resourced. | * The great news is that we've now got a dedicated developer team, developer relations and community team, all in one place (Firefox) working on Add-ons for Firefox. We're yellow because these folks are hitting the ground running, already trying to catch up for the time when we were not as well resourced. | ||
* Per discussion in the last | * Per discussion in the last month, there's concern around what the impact to end-users will be once add-on signing is required by Firefox. Consensus is that we're not quite ready to enforce it, and we're going to continue developer outreach and burning down the existing review queues to ensure we have as many addons as possible updated and signed. Add-on signing will move to enforcement in Firefox 43. | ||
* The review team has been doing fantastic work keeping the unlisted queue moving, and we don't want to take our foot off the gas in reducing all the queues. We do need to have a better picture of what the release channel profiles looks like, and we're working with the metrics team to get a regular picture of what addons remain unsigned, and what the likely impact to users will be. | * The review team has been doing fantastic work keeping the unlisted queue moving, and we don't want to take our foot off the gas in reducing all the queues. We do need to have a better picture of what the release channel profiles looks like, and we're working with the metrics team to get a regular picture of what addons remain unsigned, and what the likely impact to users will be. | ||
* We're also looking at how we can deliver a developer mode without compromising the goals of signing, as well as whether we can improve the user experience when addons are disabled to help users who lose functionality with unsigned addons. | * We're also looking at how we can deliver a developer mode without compromising the goals of signing, as well as whether we can improve the user experience when addons are disabled to help users who lose functionality with unsigned addons. The earliest we will add this is Firefox 44. | ||
== Exec Summary == | == Exec Summary == | ||