Add-ons Review Update – Week of 2010/06/08

Jorge Villalobos

Summary

  • These bi-weekly posts explain the current state of add-on reviews and other information relevant to add-on developers. There’s a lengthy overview of the Add-on Review Process posted in this blog that should be read as a general guide about the review process.
  • Most nominations are being reviewed within 9 days.
  • Almost every update is being reviewed within 5 days. We want to reduce this in the future, but nominations are the current priority.
  • By the end of this month we expect all nominations to be reviewed in less than a week, and all updates in 3 days or less.

The Review Queues

  • The stats are taken from the latest queue report from last Friday.
  • 66 new nominations that week. 79 nominations in the queue awaiting review.
  • 42 updates that week. 40 updates in the queue awaiting review.
  • 111 reviews performed by AMO Editors this month, and 965 for the month of May. There were 16 editors performing reviews last week.

See the Add-on Review Process and You for information on how to check your  add-on status.

Notes for Developers

  • New Proposal for Review Process and Delightful Add-ons. This is a new and different approach to resolve the issue of add-on safety in the sandbox and code reviews. All add-on developers should read this and give feedback. It’s been a long process to try to find the right balance of the many elements involved, and we think this is it.
  • The AMO Editor Guide. This new page in the wiki is a comprehensive guide to the work performed by AMO Editors. It will serve as an introductory guide for new editors, and is a step forward in being as transparent as possible with our review process. There are still some corrections to be made, and I’ll be blogging more about it later this week.
  • I made a proposal for the Google Summer of Code which has been accepted as a project. The idea consists in simplifying and refreshing the way add-ons are packaged and installed locally, including a completely new manifest file. In the past couple of weeks I have been blogging the spec proposal: Part 1, Part 2, Part 3. I’m now working on the wiki page that will be the actual specification for the project, that incorporates much of the feedback received so far. As the blog posts explain, this is not something that is intended to be included on Firefox. It’s an experiment on how we can do things differently, and hopefully (part of) it will be integrated into the product after more community feedback and polish.
  • AMO is currently being migrated to a new code base, some of which is already live in production. If you notice any strange behavior on the site , please make sure to file a bug (see note below about AMO bug reporting).
  • Useful Information for Add-on Authors. How to improve review times for your add-on, information about the review process, etc.
  • Bugzilla information for editors. How to file AMO bugs, how to flag bugs relevant for editors, and information on current and future AMO version releases. Let me know if you want to help fixing AMO bugs.

Jorge Villalobos

Add-ons Developer Relations Lead, Mozilla