canmove, Confirmed users
1,448
edits
m (formatting) |
(Added enforcement of review quality policy) |
||
Line 24: | Line 24: | ||
Admins monitor the reviewer group regularly and remove reviewers who have been inactive for extended periods of time. While we appreciate all contributions, it's best that reviewers have regular activity so they are less likely to overlook things. Also, access to add-on code and our internal mailing list are privileges that should be limited to active contributors. | Admins monitor the reviewer group regularly and remove reviewers who have been inactive for extended periods of time. While we appreciate all contributions, it's best that reviewers have regular activity so they are less likely to overlook things. Also, access to add-on code and our internal mailing list are privileges that should be limited to active contributors. | ||
==Enforcement== | |||
Unfortunately, there are times when we have to remove reviewers from this group because of egregious and/or frequent violations of reviewing guidelines. Reviewers will receive a warning if they are close to being put on probation. In probation, an admin will spot-check a reviewer’s activity for a month and remove them from the group if they continue making mistakes. If the reviewer improves, they will remain in the group conditionally for the next six months, provided they do not revert to making errors. | |||
Here are the types of mistakes we track and their corresponding severity: | |||
'''Most severe''' | |||
These errors lead to a terrible developer experience, or security issues for users: | |||
* Approving an add-on that should have been rejected | |||
'''Severe''' | |||
These errors are not egregious but can lead to a bad developer experience if numerous: | |||
* Rejecting an add-on when it should have been approved | |||
* Rudeness or offensive language when addressing a developer | |||
'''Minor''' | |||
These errors are minor, but again not great if numerous: | |||
*Incoherent English | |||
*Unresponsive or not helpful when involved in conversation with developer | |||
Removal of reviewing rights is rare and done only when we feel users may experience a security risk, developers are having a terrible experience, or the contributions are causing a drain on resources. If you have any questions or concerns, please contact us in one of the ways listed above. | |||
Thanks for joining the team and supporting the add-on community, our developers and users appreciate your contributions! | |||
[[Add-ons/Reviewers/Guide/CompleteThemes|Next: Complete Themes]] | [[Add-ons/Reviewers/Guide/CompleteThemes|Next: Complete Themes]] |