canmove, Confirmed users
1,448
edits
AMO:Editors/EditorGuide/AddonReviews: Difference between revisions
AMO:Editors/EditorGuide/AddonReviews (view source)
Revision as of 20:37, 19 January 2011
, 19 January 2011no edit summary
No edit summary |
No edit summary |
||
| Line 26: | Line 26: | ||
The grey box near the top of the review page shows the possible resolutions for a review.<br> | The grey box near the top of the review page shows the possible resolutions for a review.<br> | ||
[[Image:Resolutions.png|center|Possible review resolutions]] | [[Image:Resolutions.png|center|Possible review resolutions]] | ||
Clicking on any of them will open a form below it. | Clicking on any of them will open a form below it. | ||
| Line 34: | Line 34: | ||
You should normally use one of the first three resolutions: | You should normally use one of the first three resolutions: | ||
*Push to Public: the version doesn't have any problems and it's OK for the public. | *Push to Public: the version doesn't have any problems and it's OK for the public. | ||
* Grant Preliminary Review: the version has problems that prevent us from making it fully public, but it's still safe to use. | *Grant Preliminary Review: the version has problems that prevent us from making it fully public, but it's still safe to use. | ||
*Reject: the version has security issues and must be rejected. | *Reject: the version has security issues and must be rejected. | ||
The other two are for special situations: | The other two are for special situations: | ||
*Request More Information: this allows you to ask the author for information necessary to perform the review, without removing the add-on from the queue. A very common case for this is when the add-on is site-specific and the author didn't provide a test account. Since we can't be registering to every site on the web just to test, we always require authors to provide the necessary information. Replies from the author will appear in the review page. | *Request More Information: this allows you to ask the author for information necessary to perform the review, without removing the add-on from the queue. A very common case for this is when the add-on is site-specific and the author didn't provide a test account. Since we can't be registering to every site on the web just to test, we always require authors to provide the necessary information. Replies from the author will appear in the review page. | ||
*Request Super-Review: this is for very special cases where you think an admin editor should review this add-on. It can be because you think there's some malicious intent from the author; in this case you should notify the mailing list about it. It can also be because you are aware Mozilla has received a DMCA notice about this add-on. It is critical that you do '''not''' try to resolve this issue yourself. Copyright complaints should be escalated to admins and, at most, you can point the person making the complaint to the Digital Millennium Copyright Act Notice section of our [http://www.mozilla.com/en-US/about/legal.html legal notices page] for an explanation of the protocol to follow. The add-on will remain in the queue, and in this case the comments aren't sent to the author. They're only readable from the review page. | *Request Super-Review: this is for very special cases where you think an admin editor should review this add-on. It can be because you think there's some malicious intent from the author; in this case you should notify the mailing list about it. It can also be because you are aware Mozilla has received a DMCA notice about this add-on. It is critical that you do '''not''' try to resolve this issue yourself. Copyright complaints should be escalated to admins and, at most, you can point the person making the complaint to the Digital Millennium Copyright Act Notice section of our [http://www.mozilla.com/en-US/about/legal.html legal notices page] for an explanation of the protocol to follow. The add-on will remain in the queue, and in this case the comments aren't sent to the author. They're only readable from the review page. | ||
While you perform your review, you should be keeping notes of everything you noticed about the add-on: validator flags, errors in the error console, bugs, areas for improvement, etc. You can either use a note-taking program, or just type your notes in the comments textbox of the review page. Changing the resolution won't clear your notes. Just make sure you selected the right one when you're ready to submit!<br> | While you perform your review, you should be keeping notes of everything you noticed about the add-on: validator flags, errors in the error console, bugs, areas for improvement, etc. You can either use a note-taking program, or just type your notes in the comments textbox of the review page. Changing the resolution won't clear your notes. Just make sure you selected the right one when you're ready to submit!<br> | ||
The sections below include tables with the recommended resolution for the most common situations. If there are many policy problems in a review, you must take the strictest of all required actions. | |||
'''Editor Tour:''' an admin editor should have given you a specific add-on to review. Also, don't submit your first review without admin approval!<br> | '''Editor Tour:''' an admin editor should have given you a specific add-on to review. Also, don't submit your first review without admin approval!<br> | ||