Confirmed users
613
edits
Firefox/AddOns/Status/20150921: Difference between revisions
Firefox/AddOns/Status/20150921 (view source)
Revision as of 23:45, 21 September 2015
, 21 September 2015→Risks/Issues: typo
(→Risks/Issues: fixed table) |
(→Risks/Issues: typo) |
||
| Line 25: | Line 25: | ||
! 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 43% of "need to have" add-ons signed as per https://docs.google.com/spreadsheets/d/1xLnFtXLcIfIXFZodj1sFYzyDdFJ1vR3CKYNb_n-g30c/edit#gid=1874511985 but only 5% of "nice to have". || Lisa Brewster/Add-ons Review Team || | || 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 43% of "need to have" add-ons signed as per https://docs.google.com/spreadsheets/d/1xLnFtXLcIfIXFZodj1sFYzyDdFJ1vR3CKYNb_n-g30c/edit#gid=1874511985 but only 5% 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. | ||
|- | |- | ||
|| 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 wengineering 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 || 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 wengineering 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 | ||