AMO:Editors/InfoAuthors: Difference between revisions

Jump to navigation Jump to search
Updates to the notes to authors
(Updates to the notes to authors)
Line 3: Line 3:
== The Review Process ==
== The Review Process ==


[http://blog.mozilla.com/addons/2010/02/15/the-add-on-review-process-and-you This blog post] covers most aspects of the review process. We recommend you read it first.
[http://blog.mozilla.com/addons/2011/02/04/overview-amo-review-process/ This blog post] covers most aspects of the review process. We recommend you read it first.


You should read the [https://addons.mozilla.org/en-US/developers/docs/policies/ add-on policies documentation] first. This details most of the requirements and processes involved. There is also more information in the [[AMO:Editors/InfoEditors#Review_policies|editor information page]].
You should read the [https://addons.mozilla.org/developers/docs/policies/ add-on policies documentation] first. This details most of the requirements and processes involved. There is also more information in the [[AMO:Editors/EditorGuide|Editor Guide]].


Here are some recommendations to make sure that your add-on is reviewed quickly:
Here are some recommendations to make sure that your add-on is reviewed quickly:


* When nominating your add-on for the first time, make sure that it's stable, ready for the public, and generally useful. However, don't wait for it to be perfect before nominating. The nomination process can take many weeks (sometimes months), so it's better for you to nominate a good version rather than an fully polished one.
* When nominating your add-on for the first time, make sure that it's stable, ready for the public, and generally useful. However, don't wait for it to be perfect before nominating. The nomination process can take a few weeks, so it's better for you to nominate a good version rather than an fully polished one.
* Verify that your add-on is in the review queue.
* Verify that your add-on is in the review queue.
** For nominations, check the add-on Status page: https://addons.mozilla.org/en-US/developers/addon/status/YOUR_ADDON_ID/
** Check the add-on Status page: https://addons.mozilla.org/developers/addon/YOUR_ADDON_ID/versions/
** For updates, check the Versions and Files page: https://addons.mozilla.org/en-US/developers/versions/YOUR_ADDON_ID/
** If your add-on should be nominated but isn't, contact amo-editors at mozilla.org
** If your add-on should be nominated but isn't, contact amo-editors at mozilla.org
* Include descriptions and version notes in English.
* Include descriptions and version notes in English.
* Carefully inspect the results from the code validation tool.
* Carefully inspect the results from the code validation tool.
** Flags that will normally be a problem: namespacing, eval usage, browser/iframe security.
** The [[AMO:Editors/EditorGuide|Editor Guide]] explains which are important and which aren't a problem.
** Flags that normally are not a problem: setTimeout, setInterval, wrappedJSObject.
* If your add-on requires to have an account on a website, you should include a test username and password in the Notes to Reviewer section of your submission. Also include details on how to test the add-on, because the reviewer may not know how to use the website.
* If your add-on requires to have an account on a website, you should include a test username and password in the Approval Notes section of your submission. Also include details on how to test the add-on, because the reviewer may not know how to use the website.
* If your add-on contains compiled components, obfuscated or otherwise unreadable code, you need to send the clearly readable version of the code to amo-admin-reviews AT mozilla DOT org. Even when you do this, the review will take longer than normal because it needs to be done by an admin editor.
* If your add-on contains compiled components, obfuscated or otherwise unreadable code, you need to send the clearly readable version of the code to jorge at mozilla.com. Make sure you specify that you've done this in the Approval Notes section when submitting the add-on. Even when you do this, the review will take longer than normal because it needs to be done by an admin editor.
* If your add-on uses libraries or any other code not authored by you, make sure you include:
* If your add-on uses libraries or any other code not authored by you, make sure you include:
** The name of the package or original add-on.
** The name of the package or original add-on.
canmove, Confirmed users
1,448

edits

Navigation menu