Personal tools

AMO:Editors/MeetingNotes

From MozillaWiki

Jump to: navigation, search

Contents

November 11th, 2011

  • Held in Berlin, Germany, as part of Mozilla Camp EU.
  • Attendees
    • Jorge Villalobos (Mozilla)
    • Justin Scott (Mozilla)
    • Andrew Williamson (Mozilla)
    • Kris Maglione
    • Andreas Wagner
    • Archeaopteryx
    • Brian King
    • Erik Vold
    • Kent James
    • Andreas Wagner
    • Nils Maier
    • Kenneth Barbalace
    • Axel Grude
    • Jeff Griffiths

Discussion topics

  • Survey results.
  • SDK add-on reviews.
  • Apps and personas on AMO.
    • Content moderators: Personas, User Reviews, forum?
    • Manifest reviewers: Search Engines and Apps.
    • SDK reviewers: fast-track queue add-ons.
    • Editors: extensions, themes, etc.
    • Admin editors.
  • Notes from the last meeting.
  • Bug triage.
  • Queue burndown!

July 7th, 2010

  • Held at the Mozilla Summit in Whistler, Canada.
  • Attendees
    • Jorge Villalobos (Mozilla)
    • Nick Nguyen (Mozilla)
    • Justin Scott (Mozilla)
    • Andrew Williamson
    • Andreas Wagner
    • Archeaopteryx
    • Brian King
    • Erik Vold
    • Kent James
    • Mario Alvarado
    • Zadkiel M
    • Nils Maier
  • Topics
    • Use of contractors as a way to advance our work.
      • The general consensus is that this was a good idea.
      • Some feel that there must be additional motivation for volunteers, to make them feel like they are still making a significant contribution.
      • Make a list of advantages of being an AMO Editor and add them to the wiki. Learning about add-ons, invitations to Mozilla events, good for resume,...
      • Add stats in the weekly reports that indicate the volume of volunteer work, and an expected goal.
    • (very low) Editor retention
      • Consider creating a requirement system, where editors getting started need to contribute a specific amount of hours or reviews in a given time period.
      • We should probably extend this for all editors, so they know they have to remain active.
      • We need an online identity. We should get a badge or icon that identify us. And t-shirts! Maybe that can be the "prize" for finishing the initiation period. It could also appear on editor profile pages. Bug 578713.
    • XUL Tutorial and Editor Guide
      • Need to review if they are properly linked in all the right places: developer hub, add-on upload checklist.
    • Firefox 4 compatibility.
      • Warn people about nsIExtensionManager and XPCOM changes, using the validator. Bug 578722.
      • Email all authors about Firefox 4 compatibility instead of a small subset. Need to discuss this with IT.
    • UA string modification policy.
      • It shouldn't be opt-in because it's too technical and most people won't understand it.
      • However, it will only be accepted when strictly necessary.
      • Add check to validator. Bug 578725.
    • Other bugs that should be fixed soon.

April 10, 2010

  • Topics
    • State of the queues. The latest report.
    • Phasing out Appcoast contractor work.
    • Policy Updates: Private Browsing Mode, enablePrivilege and codebase_principal, FatPlug and SurfCanyon search refinements.
    • XUL School. Change link for namespacing documentation?
    • Reviewing Personas. How we think the teams will work and collaborate as Personas are fully integrated into AMO.
    • Search engine add-on policies.
    • Meeting effectiveness so far
  • Attendees
    • Jorge Villalobos (Mozilla)
    • Michael Buckley
    • Zadkiel M
    • Andrew Williamson
  • Regarding Personas, we should contact the Personas review team and see what their plans are regarding AMO integration -> Ryan Doherty is now product manager for Personas, and he's in charge of the review team.
  • For search engine add-ons, we should update our rules to give priority to engines that don't have referral codes, ads, or intermediate pages. Done.
  • It would also be good to work on a search engine generator for AMO (similar to Mycroft), in order to give users new options and reduce search engine spam. Bug 534619
    • Michael is working on an add-on that does this.

November 28, 2009

  • 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 531905
    • Maybe include editor name in subject. Bug 531906
  • Allow editors to search for already done add-on reviews Bug 531910

September 26, 2009

  • 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.
  • 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.