AMO:Editors: Difference between revisions
| Line 15: | Line 15: | ||
=== Resources === | === Resources === | ||
* [[Update:Editors/Applying|How to become an editor]] | * [[Update:Editors/Applying|How to become an editor]] | ||
* [[Update:Editors/ReviewingGuide|Processing the add-on queues | * [[Update:Editors/ReviewingGuide|Processing the add-on and review queues]] | ||
* [[Update:Editors/Testing|Testing add-ons]] | * [[Update:Editors/Testing|Testing add-ons]] | ||
* [http://addons.mozilla.org/pages/policy Add-on Policy] | * [http://addons.mozilla.org/pages/policy Add-on Policy] | ||
Revision as of 18:20, 26 March 2008
Introduction
AMO leverages volunteer reviewers/editors to look over pending and nominated add-ons for publication on the site. With the launch of Remora and the sandbox, aspects of this role have changed significantly.
What's a reviewer?
In version 2 of addons.mozilla.org, the term "reviewer" referred to a person that had access to an approval queue of extensions and themes that were submitted. Reviewers would install the add-on and test it to ensure that it worked properly, and would then either approve the version or deny it.
In Remora (version 3), anyone that has access to the sandbox is considered a reviewer. Users can enable the sandbox and install add-ons as soon as the author submits them. We hope that these users will then return to write a review of their experience with the add-on, whether it be good or bad.
What's an editor?
Editors have access to the queue of pending and nominated add-ons, and their main role is to assess the existing reviews and determine whether the add-on should be pushed to the public side based on criteria in the policy.
Resources
- How to become an editor
- Processing the add-on and review queues
- Testing add-ons
- Add-on Policy
- Sandbox Information
- Random notes
- Tools for Editors
- Editors FAQ