posts categorized as “mozilla”

I’m falling for Canada

Mozilla Summit

This week I’m in Whistler, British Columbia, Canada for the Mozilla Firefox Summit – a gathering of 300-400 of the contributors to Firefox 3. Whistler is outside of Vancouver and the trip is about 3 hours on the Sea to Sky Highway, a winding mountain road with beautiful sites and lots of construction in preparation for the upcoming Winter Olympics in Vancouver and Whistler.

Last night around 11:00pm there was a rockslide on this road that left boulders the size of houses that will have to be cleared by dynamite and will take days. The only other way out of Whistler, besides helicopter and floatplane, is a 6-8 hour trip the other way around the mountain. I leave at 11pm Friday night, so not sure what the plan is for getting 400 people out yet.

Having lots of fun and will post a more detailed update on that later.

I recently posted about the current status of the review queues. When I started writing this post, there were 241 pending updates to already-public add-ons and 479 nominated add-ons waiting review to become public for the first time. 24 hours later, the queue is now 169 pending updates and 467 nominated add-ons, a difference of over 100 versions processed (taking into account the new versions submitted today). Great job, editors!

I’d like to explain a bit about what Add-on Editors do so that developers waiting desperately for an email from AMO know what happens during this process, and also to encourage people to consider becoming an editor. If you’re thinking about getting involved more directly with the Mozilla community or are an existing contributor looking for a new way to help out, reviewing add-ons is a great way to do that. You might even meet new people, learn something, discover an add-on that you start using every day, or occasionally have a tiny bit of fun while doing it.

Ever since I started working with AMO in 2006, in addition to primarily working on the development of the site and Developer Tools, I’ve been interested and involved in the direction and administration of AMO and Firefox Add-ons in general. As of today, I’ve switched roles to follow my interests, and will be working with Basil on Add-ons Product Management instead of being a part of Mozilla Web Development. I’ll be working on a number of new projects and continuing to help AMO from a different perspective. I’ll also be helping out with community management until the AMO Community Manager position is filled.

I’ll be finishing up development of the AMO 3.5 Developer Tools Revamp milestone before I make myself forget CakePHP, but I’ve already started working on a couple of exciting new projects that I hope to share with everyone soon.

I’m looking forward to working with everyone in the coming months in my new role.

The AMO editors have been hard at work, reviewing 255 add-on updates and submissions in the 2 weeks before Firefox 3’s launch, and 238 updates/submissions between launch day (Tuesday) and Sunday.

There are currently 228 updates in the queue and 373 new nominated add-ons. There are normally about 10 new add-ons submitted to AMO every day, but since the release there have been 20-40 every day. Similarly, there are normally about 60-70 updates to existing add-ons every day, but since the launch there have been 100 – 150 every day.

Below is a graph of submission and update rates since 2004, hitting a peak of 235 updates on the day after release and 42 new submissions 2 days after release. You can also see a zoomed-in version of the graph. Astute observers will also notice a large increase in submissions in November 2006, when Firefox 2 was released.

Add-on developers who log in to AMO and check their stats dashboard may be very happy to find that their active daily users have increased quite a bit this week (my own add-on reports a 46% increase since last week). I wanted to remind developers how we determine ADU and why it is slightly skewed this week.

By default, Firefox will check an add-on’s updateURL every 24 hours to look for an update. Add-ons that don’t have an updateURL specified default to AMO, which is how we determine how many “active daily users” an add-on has. The number of times an add-on’s GUID was pinged on AMO is approximately how many people were using that add-on that day.