AMO Review Teams

Introduction

The integration of Personas and Apps into AMO raises the complexity of reviews and review teams. We need to prepare for this and avoid turning the current editor tools and editor team into a Tower of Babel. These are the combined review responsibilities that will be necessary after the merger:

• Personas.
• Apps.
• Extensions.
• Themes.
• Search Engines.
• Language Packs.
• Dictionaries.
• Moderated user comments.

This proposal suggests the creation of 3 review teams that will handle these responsibilities: Add-ons Review Team, Personas Review Team, and Apps Review Team. Moderated comments and abuse reports would be moderated by all teams. It's also worth considering if Abuse Reports should be treated similarly (only handled by admins at the moment).

Personas Review Team

• Lead by: Deb (?)
• Mailing list: personas-review
• IRC channel: #personas
• AMO Tools: https://addons.mozilla.org/reviewers/personas
• Required skills:
  • Filtering spam, inappropriate content and duplicates.
• Can review:
  • Personas.
  • Moderated user comments.

Apps Review Team

• Lead by: (?)
• Mailing list: apps-review
• IRC channel: #apps (?)
• AMO Tools: https://addons.mozilla.org/reviewers/apps
• Required skills:
  • Verifying valid websites.
  • Looking for and removing duplicates.
  • Reading structured manifest data: JSON, XML.
• Can review:
  • Apps.
  • Search Engines.
  • Moderated user comments.

Add-ons Review Team

• Lead by: Jorge
• Mailing list: addons-review (forward amo-editors), addons-review-internal
• IRC channel: #addons (might be good to keep #amo-editors for internal communication)
• AMO Tools: https://addons.mozilla.org/reviewers/addons
• Required skills:
  • Experienced add-on developer.
• Can review:
  • Extensions, Themes, Language Packs, Dictionaries.
  • Moderated user comments.

Notes

• While there are 3 sets of review tools, they would mostly be the same code. The 3 teams need a dashboard, queue views, a detailed review view, a MOTD and a performance view. They will just be using different data.
• The review email templates will be different for each team.
• A reviewer from team X shouldn't have access to review pages of team Y.
• A reviewer can belong to more than one team, potentially all 3.
• The Add-ons Review team currently needs 2 mailing lists. Perhaps the other teams will need the same.
• As a bonus (lagniappe, if you will), I'm aiming to move away from the unrelated "editors" term.