Firefox/AddOns/Status/20150929: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Status for November 5, 2015 =
= Status for December 24th, 2015 =


== Overall Project Health - YELLOW ==  
== Overall Project Health - YELLOW ==


* 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.  
== Exec Summary ==
* Overall add-ons '''strategy development''' is going well.  We are working through timing and trade-offs, aligning across the teams (including UX).
**We have a preliminary [https://mozilla.aha.io/published/0d49e74c6853d3d721010bd9d4f67f34?page=1 '''Roadmap'''] that we are working from and will keep improving as we fully integrate our priorities / new hires.
* '''Signing''' went out the week of Dec 15th (with pref to turn off). 
**No un-fixable bugs (patched already) - but more excitement than the ideal.  We are looking into how it could have been smoother and adjusting accordingly. **evaluating user sentiment data from several sources: ex: twitter, SUMO, social media. 
**Currently targeting Signing with no pref to turn off in Firefox 47.
**[https://bugzilla.mozilla.org/show_bug.cgi?id=1209341 Bug 1209341 ] - Allow loading unsigned restartless add-ons at runtime was fixed and landed in Firefox 45 to help Developers test their add-ons without getting them Signed.


* 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.   
* '''Review-Queues''':  Looking at the "quick wins" to improve the queues, along with the on-going dedicated focus in this area.  Working on a dashboard for better visibility into what's happening, to see when adjustments have a positive or negative impact. We need more detailed info than just "average review time", for example - it's interesting looking at a snapshot (time range: Nov 18, 2015 - Nov 25, 2015) of how long it takes to review the Average compared to the "50%":
 
**Listed-nominated:
* 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.
***Average waiting time: 35 days
 
***50% of all waiting add-ons reviewed in less than 12 days
* 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.
**Listed-pending:
 
***Average waiting time: 9 days
== Exec Summary ==
***50% of all waiting add-ons reviewed in less than 1 day
* Overall add-ons strategy development in progress - team met in Toronto to discuss.
**Listed-preliminary:
* Development team now in place led by Andy McKay, [https://wiki.mozilla.org/Marketplace/AMMO Dev Relations and Community team] also now reports to Nick Nguyen
***Average waiting time: 26 days
* One of two budgeted add-on review contractors was onboarded this week, second hire in progress.
***50% of all waiting add-ons reviewed in less than 2 days
* FirefoxOS Add-ons
* [https://wiki.mozilla.org/E10s#Schedule '''e10s''']: Add-ons continues to work with e10s for [http://arewee10syet.com compatibility] and planning how to stage the roll-out. For a smoother user & developer experience, it is planned for the first 1-2 Releases where e10s goes to Release (earliest in Fx45) to exclude add-on audiences, as the team continues to make more add-ons work.
* Add-on Signing: is now live in 41 beta, but progress to release is now [https://blog.mozilla.org/addons/2015/09/16/extending-the-deadline-for-add-on-signing/ extended to 43].
* [https://wiki.mozilla.org/WebExtensions '''WebExtensions''':] Development continues to add more capabilities. There is a targeted QA push for Fx48, where take the webextensions that have been created and stabilize any that need it and "launch" more broadly.
* e10s: e10s will ship in 42 Aurora. Add-on compatibility testing efforts continue to be maintained at [http://arewee10syet.com]  Earliest e10s will ship in release is 43.
* While we have a dedicated developer, developer relations and community team hit (YAY!) - we are still hiring and on-boarding new folks to focus full-time on these projects.
* WebExtensions: Extension API landed on Nightly. [https://wiki.mozilla.org/WebExtensions the WebExtensions Wiki] has details. Development is now being supported by Andy McKay's team
** Luca Grecco joined the Developer team from Italy in December, after being a lont time contributor!!!
* AMO further roadmap development is now moving forward actively.
* Full details on each work iteration (three iterations per Firefox release) can be found on our new canonical [http://wiki.mozilla.org/Add-ons Add-ons wiki]
* Add-ons for FxOS are progressing, status can be found at the [https://mana.mozilla.org/wiki/display/PM/FxOS+2.5+Addons+Project FxOS add-ons Mana page] (LDAP login required)


== Risks/Issues ==
== Risks/Issues ==
Line 29: Line 32:
! Initiative !! Risks/Issues !! Owner !! Mitigation/Approach
! Initiative !! Risks/Issues !! Owner !! Mitigation/Approach
|-
|-
|| Addon Signing|| Unlisted add-ons considered critical are being reviewed as soon as they are submitted (unlisted queue is under control) but many unlisted add-on developers have not (or are presumed to have not) yet submitted for review.  We are at over 50% of "need to have" add-ons signed as per https://docs.google.com/spreadsheets/d/1xLnFtXLcIfIXFZodj1sFYzyDdFJ1vR3CKYNb_n-g30c/edit#gid=1874511985 but less than 25% of "nice to have". || Lisa Brewster/Add-ons Review Team || Reaching out to unlisted add-on devs to ensure they submit for review, focusing resources on unlisted add-on reviews, longer term we are changing how we review.
|| Addon Signing|| See exec summary || Lisa Brewster/Add-ons Review Team || pending shell update
|-
|-
|| AMO Review Queue || We have insufficient resources for the listed review queue which is very long and growing. We recently hired one new FTE, but also moved one reviewer over to engineering development. We do have budget for two contract reviewers, but hiring has been a challenge. Review queue challenges illustrated here: http://diox.github.io/amo-review-times/ and https://docs.google.com/spreadsheets/d/1E41MCpqf71Ayx1Im4dCspu7bxNzaMpOSYiVDQXL8dK4
|| AMO Review Queue || see exec summary


|| Lisa/Add-on Review team || Additional contract reviewers being hired now for short term mitigation, one starts Friday at 30 hrs but second hire has not yet been made. Also longer term changes to how we review are planned, SLA being established, etc.
|| Lisa/Add-on Review team || pending shell update
|-
|-
|| AMO Validator || the validator has several issues slowing down the queue - it is not providing very useful results to developers, and it is rejecting 4/5 add-ons.  || Validator team, Andy, Kev, Larissa || We have plans in development, 2 Engineers assigned to improvements, and the first phase of these is nearly complete.
|| AMO Validator || Andy, Lisa, Kev || pending shell update
|-
|-
|}
|}


== Accomplished for last three Weeks ==
== Accomplished for last three Weeks ('''from Sept - pending Shell update''') ==
* team reorganization mostly complete - engineering team, now led by Andy McKay, and Dev/Community team, led by Lisa Brwester, now moved to firefox org and dedicating full resources to add-ons.
* [https://docs.google.com/document/d/17o2l7VV9OBwXxGeEUQf0-4dZhlbbrJPkGbIXA-ht2Tg/edit# Bi-weekly Public Current Activity] notes and history.
* leadership team met in Toronto last week and worked on planning the future of Add-ons. the new wiki will be the place to find plans as they evolve. Iteration 44.3 is already detailed and listed out.
* blogs - Shell needs to update with info from what Andy, Kev, and Jorge have recently posted.
* process for streamlined review signing of internal mozilla addons (experiments, system addons, lightning, etc) tlive
* Future of Developing Add-Ons Blog Live! https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/
* Add-on signing shipped in 41 beta, driving considerable growth in unlisted addons submitted for review (See attached chart)and will not ride trains to release until 43 based on feedback, need for additional development and time needed for developers to get add-ons signed.
* Social media feedback moderate, neither positive nor negative (see attached graph)
* WebExtensions shipped in nightly
* Slow Add-On Watcher is in early development
* Phase one validator improvements are all done or nearly done to be live in the coming week (see: https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=validator-p1&list_id=12471788)
* Benchmarks for validator improvements are in progress
* Add-on reviewer new contract hire selected, contract in progress.
* Many unlisted addons reviewed - Andreas averaging *30 or more per day*! https://docs.google.com/spreadsheets/d/1E41MCpqf71Ayx1Im4dCspu7bxNzaMpOSYiVDQXL8dK4


== Planned for Upcoming Iteration ==
== Planned for Upcoming Iteration ==
Line 59: Line 52:


== Important Links/References ==
== Important Links/References ==
* [https://docs.google.com/document/d/17o2l7VV9OBwXxGeEUQf0-4dZhlbbrJPkGbIXA-ht2Tg/edit# Bi-weekly Current Events in Add-ons Notes]
* [https://wiki.mozilla.org/Add-ons Add-ons Wiki]
* [https://wiki.mozilla.org/Add-ons Add-ons Wiki]
* [https://wiki.mozilla.org/AMO/SigningService Signing Service Overview]  
* [https://wiki.mozilla.org/AMO/SigningService Signing Service Overview]  

Latest revision as of 19:39, 24 December 2015

Status for December 24th, 2015

Overall Project Health - YELLOW

Exec Summary

  • Overall add-ons strategy development is going well. We are working through timing and trade-offs, aligning across the teams (including UX).
    • We have a preliminary Roadmap that we are working from and will keep improving as we fully integrate our priorities / new hires.
  • Signing went out the week of Dec 15th (with pref to turn off).
    • No un-fixable bugs (patched already) - but more excitement than the ideal. We are looking into how it could have been smoother and adjusting accordingly. **evaluating user sentiment data from several sources: ex: twitter, SUMO, social media.
    • Currently targeting Signing with no pref to turn off in Firefox 47.
    • Bug 1209341 - Allow loading unsigned restartless add-ons at runtime was fixed and landed in Firefox 45 to help Developers test their add-ons without getting them Signed.
  • Review-Queues: Looking at the "quick wins" to improve the queues, along with the on-going dedicated focus in this area. Working on a dashboard for better visibility into what's happening, to see when adjustments have a positive or negative impact. We need more detailed info than just "average review time", for example - it's interesting looking at a snapshot (time range: Nov 18, 2015 - Nov 25, 2015) of how long it takes to review the Average compared to the "50%":
    • Listed-nominated:
      • Average waiting time: 35 days
      • 50% of all waiting add-ons reviewed in less than 12 days
    • Listed-pending:
      • Average waiting time: 9 days
      • 50% of all waiting add-ons reviewed in less than 1 day
    • Listed-preliminary:
      • Average waiting time: 26 days
      • 50% of all waiting add-ons reviewed in less than 2 days
  • e10s: Add-ons continues to work with e10s for compatibility and planning how to stage the roll-out. For a smoother user & developer experience, it is planned for the first 1-2 Releases where e10s goes to Release (earliest in Fx45) to exclude add-on audiences, as the team continues to make more add-ons work.
  • WebExtensions: Development continues to add more capabilities. There is a targeted QA push for Fx48, where take the webextensions that have been created and stabilize any that need it and "launch" more broadly.
  • While we have a dedicated developer, developer relations and community team hit (YAY!) - we are still hiring and on-boarding new folks to focus full-time on these projects.
    • Luca Grecco joined the Developer team from Italy in December, after being a lont time contributor!!!

Risks/Issues

Initiative Risks/Issues Owner Mitigation/Approach
Addon Signing See exec summary Lisa Brewster/Add-ons Review Team pending shell update
AMO Review Queue see exec summary Lisa/Add-on Review team pending shell update
AMO Validator Andy, Lisa, Kev pending shell update

Accomplished for last three Weeks (from Sept - pending Shell update)

Planned for Upcoming Iteration

  • dev team working on Iteration 4.1 - 3 iterations per firefox release
  • Program management continues to develop the wiki and reporting and associated documents including an up to date schedule showing the relationships of different add-ons work streams
  • Developer and Community team working on onboarding new reviewer hire, and getting add-on developers to submit for signing.

Important Links/References

Retrieved from "https://wiki.allizom.org/index.php?title=Firefox/AddOns/Status/20150929&oldid=1110624"