AMO:Editors/MeetingNotes

AMO Editors Meeting Details

For now tentatively done every month,
1-800-707-2533 (pin 369) or 1-650-215-1282 or 1-650-903-0800
Conferencing Center: x92
Conference ID: 398
Additional discussion at #addons (irc.mozilla.org)

November 28

• Topics
  • State of the queues. The latest report.
  • Editor contractors from Appcoast.
  • Trusted add-on cleanup. One public reaction.
  • Usage of "Gmail" in German locales. Bug 513252
  • Review process redesign suspended.
  • Revisit suggestions from previous meetings.
• Attendees
  • Jorge Villalobos (Mozilla)
  • Mario Alvarado (Mozilla)
  • Andrew Williamson
  • Andreas Wagner
  • Shivanand Sharma
  • Adarsh TP
• AMO Editor wiki update -> Jorge
• Editors should know which add-ons are trusted.
• Enforce a strong password policy in AMO.
• Improve sorting in queues to avoid penalizing authors that frequently update.
• Follow up on namespacing code validation -> clouserw
• Look for ways to improve editor motivation and retention.
• Allow AMO Editors to edit the validation tool page.
• Use https://preview.addons.mozilla.org/ for testing.
• Need an AMO change log (with bug links).
• Improve the review commenting system. It should be possible to comment on a version, and have a comments flag.
• Create information request flag (answered and unanswered).
• Create RSS feed for queues.
• Include test steps as part of nomination requirements.
• Improve context for authors to reply to editors:
  • I think it would be a good idea to modify the text of the notifications so that authors know how to properly follow up on any rejections. Something like "please reply to this message and make sure this e-mail is fully quoted".

Maybe include editor name in subject.

September 26

• Attendees
  • Nick Nguyen (Mozilla)
  • Jorge Villalobos (Mozilla)
  • Rey Bango (Mozilla)
  • Zadkiel
  • Andrew Williamson
  • Andreas Wagner
  • Adam Green
  • Teun van Eijsden
  • Shivanand Sharma
  • Archaeopteryx

• Queue status and new editor weekly report.
  • Editor focus on nominations is working well.
  • Focus back on updates eventually. Rey: rotating queues schedules for editors in order to distribute work properly.
  • Bring super-review escalation to a minimum.

• Review process redesign overview. http://docs.google.com/Doc?id=dcxw3w5k_25hn9nd8vg

• Suggestions from editors on how to improve the system.
  • Request more descriptive information from authors, specially regarding expected behavior
  • Screenshots showing differences in add-on.
  • Allow uploading updates when in nomination queue without bumping the add-on to the back of the line.
  • Improve validation tools to detect lack of namespacing.
  • Diff for nominations https://bugzilla.mozilla.org/show_bug.cgi?id=498072
  • Separating themes and search engines from main queues. Rey: you can sort the queues by type in the editor tools.
  • More editors.
  • Make the validation tool more verbose about its flags.
  • Author checklist before submission.
  • Inspire Confidence in new editors
  • Categorize the addons queue by the level of expertise required for reviews
  • Queue rotation. Monthly / bi-monthly.
  • Sandbox after info request and no response? 1 week, maybe?
  • Add-on update/nomination feed.
  • Editor comments -> not used much
  • Private editor mailing list.

• Feedback on call -> very good. The meeting was long and very productive, but the frequency shouldn't be too high to prevent having the meetings become meaningless.