Add-ons Review Update – Week of 2010/02/23


  • These 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 as well. We’re just getting started with these, so your feedback is greatly appreciated.
  • Most nominations are being reviewed within 3 weeks. Our goal is to reduce this to 2 weeks before April.
  • Most updates are being reviewed within a week. We want to reduce this even more in the future, but nominations are the current priority.

The Review Queues

  • The stats are taken from the latest queue report from last Friday.
  • 80 new nominations that week. 215 nominations in the queue awaiting review.
  • 91 new updates that week. 95 updates in the queue awaiting review.
  • 1013 reviews performed by AMO Editors this month. There were 25 editors performing reviews that week.

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

Notes for Developers

  • 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 us/me know if you want to help fixing AMO bugs. Thanks!
  • Private Browsing Mode support will soon become a requirement for add-ons that handle browsing data.
  • Adding SeaMonkey 2 support in your add-ons is easy and strongly encouraged. Learn how.
  • I’m currently working on porting the XUL School Tutorial for Extension Developers to MDC. This tutorial was originally developed by Glaxstar (now Appcoast) back when I worked for them. I wrote most of it, and now Appcoast has graciously donated the full tutorial contents to Mozilla. I expect to have ported all of the material within a week or so.

Jorge Villalobos

Add-ons Developer Relations Lead, Mozilla

3 responses

  1. Bee wrote on :

    Well, if you could do what you wrote for real and also solve all the bugs at AMO… it would be nice!!!!!!!!!!!!!!!!!!!!!!!!

    Anyway, for my addon `BeeFree’, i’m using my own updating tool, because i don’t like how AMO works!!!!!!!!!!!!!!
    It isn’t only about bugs blocking updates, slowdowns, and all the possible unexpected hassles you should face every time you’re uploading your addon at AMO!!!!!!!!!

    I think that the system used at AMO to give updates to users is very bad!!!!!!!!!!!!!!!!!!!!!! It’s bad, because it’s a system that isn’t respecting users!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    I wrote one article about that, and my own solution, at the HONEY BEE NET:

    AMO is almost,’s without “almost”, a SPYWARE!!!!!!!!!!!! Because it’s spying users without their consent!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


  2. Jorge wrote on :


    The alleged “spyware” in the previous comment refers to the statistics dashboard that was included on AMO a very long time ago:

    These stats are gathered from the update pings add-ons send to look for new versions, and are completely anonymous. As almost all of you already know, Mozilla makes an extraordinarily serious commitment to protect user privacy.

  3. Bee wrote on :

    Hi Jorge!!!!!!!!!!

    yeah, they were introduced long time ago, but i didn’t knew it!!!!!!!!!!!!!!!!!!!
    How many people know it? aside from old and new addons developers, i don’t think that many know about AMO’s statistics dashboards!!!!!!!!!!!!!

    I also know that Mozilla takes user’s privacy seriously!!!!!!!!
    That’s why i find very suspicious the fact that Firefox hasn’t one option like “Allow AMO to collect my addons usage information” unchecked by default!!!!!!!! what is even more suspicious, is that such a option doesn’t exists at all!!!!!!!!!!!!!!!!!!!!!!!!!!!

    > Mozilla makes an extraordinarily serious commitment to protect user privacy.

    TRUE, but not is this case!!!!!!!!!!!!!!!!