canmove, Confirmed users
1,448
edits
AMO:Editors/MeetingNotes: Difference between revisions
→November 28
| Line 15: | Line 15: | ||
** Review process redesign suspended. | ** Review process redesign suspended. | ||
** Revisit suggestions from previous meetings. | ** 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 [https://addons.mozilla.org/en-US/firefox/pages/validation 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 == | == September 26 == | ||