302
edits
Add-ons/QA/Testplan/Add-ons Post Reviews Process: Difference between revisions
Add-ons/QA/Testplan/Add-ons Post Reviews Process (view source)
Revision as of 13:00, 20 June 2017
, 20 June 2017→what's in scope?
ValentinaP (talk | contribs) |
ValentinaP (talk | contribs) |
||
| Line 36: | Line 36: | ||
== Scope == | == Scope == | ||
===what's in scope?=== | ===what's in scope?=== | ||
'''1. Deploy Auto-approval''' | |||
*WebExtensions will continue to be submitted through the regular flow, and a command will be run regularly (~every hour) to evaluate and auto-approve some of them, based on criteria defined in the linked [https://docs.google.com/document/d/1VxvvzQQvfDOVCylSVlpfeXv0tDYRLZfIMvWOoraANGU/edit#heading=h.diha6b7e1on6 PRD]. | |||
'''2. Implement post-review list for auto-approved add-ons''' | |||
*Add-ons that are auto-approved will appear in the post-review queue from [https://addons-dev.allizom.org/en-US/editors/queue/auto_approved Reviewer Tools]. List will contain: add-on name and version number (linking to the corresponding review page), last review - time since last manual review (in days), Flags and Weight (sorted after weight) | |||
'''3. Changes to Reviewer Tools''' | |||
*If the last review for an add-on was done manually or the user looking at the page doesn’t have the Addons:PostReview permission, show the current reviewer page. | |||
*If the last review for an add-on was automatic and the user looking at the page has the Addons:PostReview permission, show the reviewer page with the following changes: | |||
- Display recent user ratings (3 stars of fewer) and abuse reports (for the add-on or the developers, if there are any reports), with links to the full lists, below the add-on metadata and right above “More about this add-on”. | - Display recent user ratings (3 stars of fewer) and abuse reports (for the add-on or the developers, if there are any reports), with links to the full lists, below the add-on metadata and right above “More about this add-on”. | ||
- The "Confirm Approval" resolution should be available, and shouldn’t display the form for comments and canned responses. Instead, it should only show the Save button. Confirming doesn’t send any information to the developer or change its status. It only records it so the last manually-approved version is used to calculate the code changes compared to the latest version. | - The "Confirm Approval" resolution should be available, and shouldn’t display the form for comments and canned responses. Instead, it should only show the Save button. Confirming doesn’t send any information to the developer or change its status. It only records it so the last manually-approved version is used to calculate the code changes compared to the latest version. | ||
| Line 50: | Line 50: | ||
- The Reject action should include a way to select which versions of the add-on are affected by the rejection. All of those versions should be disabled once the review is saved, and should be listed in the email sent to the developer. | - The Reject action should include a way to select which versions of the add-on are affected by the rejection. All of those versions should be disabled once the review is saved, and should be listed in the email sent to the developer. | ||
'''4. Post-review prioritization''' | |||
*The post-review list will be sorted according to a weighted sum of the following risk factors: | |||
- The add-on has the admin review flag. | - The add-on has the admin review flag. | ||
- Flags raised during static analysis. | - Flags raised during static analysis. | ||
| Line 61: | Line 61: | ||
- Past rejection history. | - Past rejection history. | ||
Note: Add-on Reputation - is an admin-set override that helps rank down popular add-ons that are known to be high-quality and would generally rank higher due to code complexity and high volume of user feedback. This also includes add-ons developed by Mozilla. | '''Note''': Add-on Reputation - is an admin-set override that helps rank down popular add-ons that are known to be high-quality and would generally rank higher due to code complexity and high volume of user feedback. This also includes add-ons developed by Mozilla. | ||
The reputation is an integer ranging between 0 and 3, that is set per-add-on, defaulting to 0. | The reputation is an integer ranging between 0 and 3, that is set per-add-on, defaulting to 0. | ||
'''5. Submission process updates''' | |||
*The submission flow will have the following changes: | |||
- Replace the Developer Agreement step with a step linking to the 3 main documents: Developer Agreement, Review Policy, and Review Rules. Each document will have a checkbox next to it indicating the developer has read them and agreed to them. | - Replace the Developer Agreement step with a step linking to the 3 main documents: Developer Agreement, Review Policy, and Review Rules. Each document will have a checkbox next to it indicating the developer has read them and agreed to them. | ||
- Ensure all developers see these documents on their next submission, even for an update. | - Ensure all developers see these documents on their next submission, even for an update. | ||
| Line 71: | Line 71: | ||
- For WebExtensions, the text in the last step should be adjusted to reflect the new process. | - For WebExtensions, the text in the last step should be adjusted to reflect the new process. | ||
'''6. Remove auto-approval restrictions''' | |||
*All WebExtension submissions will be post-reviewed after this point | |||
===what's out of scope?=== | ===what's out of scope?=== | ||