AMO:Editors/MeetingNotes: Difference between revisions
Jump to navigation
Jump to search
(→November 28: added a topic) |
|||
Line 28: | Line 28: | ||
* Follow up on namespacing code validation -> clouserw | * Follow up on namespacing code validation -> clouserw | ||
* Look for ways to improve editor motivation and retention. | * 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]. [https://bugzilla.mozilla.org/show_bug.cgi?id=531880 Bug 531880] | * <strike>Allow AMO Editors to edit the [https://addons.mozilla.org/en-US/firefox/pages/validation validation tool page].</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=531880 Bug 531880] | ||
* Use https://preview.addons.mozilla.org/ for testing. | * Use https://preview.addons.mozilla.org/ for testing. | ||
* Need an AMO change log (with bug links). | * Need an AMO change log (with bug links). | ||
Line 34: | Line 34: | ||
* Create information request flag (answered and unanswered). [https://bugzilla.mozilla.org/show_bug.cgi?id=531889 Bug 531889] | * Create information request flag (answered and unanswered). [https://bugzilla.mozilla.org/show_bug.cgi?id=531889 Bug 531889] | ||
* Create RSS feed for queues. [https://bugzilla.mozilla.org/show_bug.cgi?id=531893 Bug 531893] | * Create RSS feed for queues. [https://bugzilla.mozilla.org/show_bug.cgi?id=531893 Bug 531893] | ||
* Include test steps as part of nomination requirements. [https://bugzilla.mozilla.org/show_bug.cgi?id=531901 Bug 531901] | * <strike>Include test steps as part of nomination requirements.</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=531901 Bug 531901] | ||
* Improve context for authors to reply to editors: | * 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". [https://bugzilla.mozilla.org/show_bug.cgi?id=531905 Bug 531905] | ** <strike>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". </strike>[https://bugzilla.mozilla.org/show_bug.cgi?id=531905 Bug 531905] | ||
** Maybe include editor name in subject. [https://bugzilla.mozilla.org/show_bug.cgi?id=531906 Bug 531906] | ** <strike>Maybe include editor name in subject.</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=531906 Bug 531906] | ||
* Allow editors to search for already done add-on reviews [https://bugzilla.mozilla.org/show_bug.cgi?id=531910 Bug 531910] | * Allow editors to search for already done add-on reviews [https://bugzilla.mozilla.org/show_bug.cgi?id=531910 Bug 531910] | ||
Revision as of 00:32, 30 March 2010
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. Bug 531866
- Enforce a strong password policy in AMO. Bug 531868
- Improve sorting in queues to avoid penalizing authors that frequently update. Bug 531875
- 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.Bug 531880- 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. Bug 531887
- Create information request flag (answered and unanswered). Bug 531889
- Create RSS feed for queues. Bug 531893
Include test steps as part of nomination requirements.Bug 531901- 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".Bug 531905Maybe include editor name in subject.Bug 531906
- Allow editors to search for already done add-on reviews Bug 531910
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 reviewsQueue 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.