Add-ons/Reviewers/Guide/Team: Difference between revisions

→‎Enforcement: clarified spot check process, probation notifications
(→‎Enforcement: clarified probation)
(→‎Enforcement: clarified spot check process, probation notifications)
Line 23: Line 23:


==Enforcement==
==Enforcement==
Unfortunately, there are times when we have to remove reviewers from this group because of severe and/or frequent violations of reviewing guidelines. Reviewers will receive a notice if they are put on probation. In probation, an admin will spot-check a reviewer’s activity for six and remove them from the group if they continue making severe mistakes. If the reviewer improves, they will remain in the group conditionally, provided they do not revert to making errors.
Volunteer reviewers represent Mozilla in their decisions and interactions with add-on developers, so establishing and enforcing review standards is essential to a good developer experience and user safety.


Here are the types of mistakes we track and their corresponding severity:
Admin reviewers perform regular spot checks of reviews. During these checks, they might find mistakes in review decisions. Here are the types of mistakes we track and their corresponding severity:


'''Most severe'''
'''Most severe'''
Line 43: Line 43:
*Incoherent English
*Incoherent English
*Unresponsive or not helpful when involved in conversation with developer
*Unresponsive or not helpful when involved in conversation with developer
If multiple severe and/or frequent mistakes are found, reviewers will receive a notification that they have been put on probation. In probation, an admin will spot-check a reviewer’s activity for six and remove them from the group if they continue making severe mistakes. If the reviewer improves, they will remain in the group conditionally, provided they do not revert to making errors.


Removal of reviewing rights is rare and done only when we feel users may experience a security risk, developers are having a poor 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.
Removal of reviewing rights is rare and done only when we feel users may experience a security risk, developers are having a poor 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.
1,698

edits