Reviewing add-ons is a complicated task, and we haven’t been very good at documenting the whole process. New editors were trained live through IRC, and the training session usually took the better part of 2 hours. Even though I am pretty much the only person training new editors, it is very difficult to convey the same message and all the intricacies of add-on reviewing to every new trainee. It was all very inconsistent. That is, until now.
After a few days’ work, we now have the AMO Editor Guide on the Mozilla wiki. This guide covers all of the editor tools, testing set up, and the usual editor work, that can be summed up to two major responsibilities: reviewing add-ons and moderating flagged user comments.
This is meant to be a comprehensive guide, so I’ve tried to put everything we do in there. Every step we take and every policy we apply should be expressed in this guide in some form. And if it isn’t there, we’ll add it. There are, however, situations where we don’t have exact rules, and editors have to apply their better judgment. You shouldn’t see this as a script editors follow to the letter or as our final word in add-on quality. Add-on authors should always feel free to reply to reviews and let us know if they disagree with them. No message will go unanswered.
This guide should interest add-on authors, to better understand what we do and why. Also, if you’re interested in becoming an editor, this will give you a very good idea of what our day to day work involves. If you want to discuss this guide or suggest changes, I’ve opened up a topic in the Add-ons Forum for it.