Mozdev.org

At long last bug#20841 is coming to a close which means our top 50 projects page has been updated to show all the new stats that we're tracking for our projects.  Want to know who commits the most or has the most active mailing list, now you can!  Along with the updated top 50 page is a new set of RSS feeds so that you can follow any of these lists in any order you want (other than just the top 50 projects by pages as it was previously).

Other than that, Mozilla has deployed our customized fizzypop in their new add-on builder with a tip over to use for the non-Mozilla apps or advanced tasks.  Their add-on builder looks great and we definitely appreciate the link!  They've already made improvements that we need to incorporate.

This week I was able to finish up porting our Bugzilla templates and skin to work with version 3.4 as well as implement graphs for various project stats.

Fixing up our Bugzilla templates was slightly complicated due to moving away from editing the templates directly and putting them into the "custom" directory to override the built-in templates.  The skins needed slight updates to override new styles in 3.4.  Permissions problems caused problems porting the templates as I was unable to view my changes frequently causing slow-downs in testing.

The graphs for project stats are available both for all projects and on a per-project basis on each project's overview page.

Next week I would like to update the top 50 page to pull data from the new stats since this will provide both a rolling 30-day window (instead of a window reset at the 1st of each month) and will also allow new projects to show up for certain stats (we have some projects with large numbers of downloads that don't currently show up - and I'm really interested to see the project with the most commits).

Two things have primarily been worked on this week; project stats and getting our bugzilla templates updated for Bugzilla 3.4.

The biggest thing going on with project stats this week has been bug fixing and backend code to get the data gathered and presented properly.  I've now finally begun frontend work, and you can see that the project overview page now has some more stats about the last 30 days (see www's page for an example).  Next I'd like to add some graphs for the web stats we have as well as VCS commits and list posts (probably not bugs right now).

The bugzilla templates are coming along fine, I just haven't spent too much time tweaking them.  It looks like our CSS will need some work, but it shouldn't be too difficult.

Other minor things include a Drupal upgrade to version 5.20 and addressing some bugs found from error message reports.

This coming week I'd like to finish up the project stats by adding the graphs to the overview page; a site-wide graph of the various stats, and updating the top 50 page to show all the new stats values.  I'd also like to finish up the Bugzilla template updates so we can look into upgrading to 3.4.

I've been busy the past couple weeks and forgot to post a status update.  In the past two weeks I've primarily been working on improving the per-project stats we're gathering in preparation to show them on the project overview page.  Stats we're now tracking per-project are include: web hits, page views, and bandwidth as well as the number of downloads, bugs, list posts, and vcs commits.  This week I hope to get these stats visible on the project overview page and hopefully re-tool some other pages (like the top 50 page) to use more of this data.
Other tasks the past few weeks include:

• bug#21315 - fixing long CVS commit problem after server upgrade
• bug#19617 - announced Project Wizard (sounds like AMO will be getting a similar tool)
• Added support for Songbird Feathers to project wizard
• bug#20841 - started gathering web stats for all projects instead of just top 50.  Also started gathering stats for number of list posts, VCS commits, and bugs.
• Fixed bug in hg log parsing (script wasn't being run w/ proper path)
• Upgrade OpenX ad server
• Upgrading Bugzilla templates for 3.4.x (bug#21711)

A week ago I was spending a good bit of time on a non-Mozdev-related project so I didn't post a status update since there was very little work done.

This past week I've been finishing up our project wizard (suggestions on a better name that distinguish between a Mozdev project and a wizard project are welcome) and it's now ready for production.  New projects are given links to the wizard to get started on their project right away.  Existing projects can select their project and have a template generated for them to get them going quickly as well.  We even support Songbird extensions and hope to add Songbird feathers and possibly Komodo extensions in the near future.  If you have any problems feel free to add them to bug#19617.

Besides the project wizard I helped look for problems with our recent server upgrade which seemed to go very smoothly.

This week I'd like to finish adding support for any new project types to the wizard and then I will be looking back to the roadmap for futher ideas.

Last week was a slow week as I handled lots of project support requests and had some outside projects on my plate.  Some things that were accomplished include:

• bug#19617 - Fixed zip file creation; some minor display problems
• fixed bug in user overview page which prevented display for some usernames with punctuation (periods, underscores)
• fixed bug in project request form which showed an error for email addresses with a plus in them
• fixed bug in project creation where mail list passwords weren't sent to the project owner
• added project creation time to the project overview page

This week I plan to continue finishing up the project wizard.  Feel free to add your comments to bug#19617 if there's anything you'd like to see.

Last week was spent getting our extension/project wizard (bug#19617) ready and a lot of progress has been made.  It can currently:

• Display a choice for type of project to create (extension, application, or component)
• Display an empty form for each type of project
• Pre-fill data for existing or pending projects
• Re-display a form with error data
• Generate a zip file for the user to download and get started with their work

There seems to be a problem with the zip file generation that I haven't been able to debug yet.  Otherwise it's most polish that needs to happen now and should be finished up very quickly.
Other tasks included:

• Project & mirror support
• bug#21315 - Problems commiting large-ish file to CVS

Next week I'll be on vacation and should resume normal tasks in a week with finishing up this extension wizard.

Last week was spent beginning integration Fizzypop into Mozdev for bug#19617.  This included

• Publishing the existing work in bug#505441 and an hg repository
• Integrating the updated Fizzypop into Hovercraft as a mercurial subrepo
• Beginning work on the controller for how to render the wizard in certain situations

Some other minor bug fixes:

• Fixing case sensitivity of download files (impacted display when a file was deleted/readded w/ a different case)
• Cleaning up PHP notices for undefined variables (cleans up error log making debugging easier)

This week I hope to get our extension wizard to a testable condition.

Last week was primarily spent hacking on FizzyPop for bug#19617.  I was able to split out the project (extension, application, etc) generation from the frontend scripts as well as separate the form fields from the web pages so that the form fields can be reused with different frontends.
Other projects included improving the spam filter options for our Drupal install and some general bug fixing to fix errors reported in our logs.
This week I'd like to work on getting FizzyPop in place at Mozdev once I get some feedback on the best implementation for our users.

Last week was fairly busy as I finished the wiki upgrade and began working on setting up an extension wizard.
This week I plan on continuing to work on the extension wizard to try to get it to a point where the backend is fully separated from the frontend so it can be used at Mozdev with a simplified web interface.

I spent a lot of time last week finishing up the preparations for the wiki upgrade and notifying project owners that it was about to happen. This week I should be ready to put that in production so that all of our wikis have an easier-to-use WYSYIWYG editor.

Since the wiki update will be getting finished up, I'll be looking at adding a extension setup wizard to Mozdev that can be used during the project creation process to get users up and running faster. This might also entail some improvements to our project request form.

In list form, last weeks activities included:

• wiki upgrade - finished up testing the upgrade process, finished updating our install profile so new Drupal installs get the new wiki settings, and informed Drupal users of the upgrade
• Upgraded Drupal to 5.19

I was a little ambitious in my plans for last week, but I did get a couple things done before I went on vacation. Primarily it was getting notifications sent to our projects that don't support 3.5 yet, but do support at least 3.0. I was also able to fix a bug in our XPI parsing and did some research into a misconfigured old project.

This week I plan on getting the wiki upgrade process finalized using the Drush tool and get any final impressions before performing the upgrade.

This week was mostly spent looking over Firefox 3.5 support, compiling stats, and fixing bugs. I was able to get a little bit of time in on the wiki upgrade, but didn't finalize the upgrade procedure yet.

• Compiling high-priority, low-effort tasks for new sysadmin
• Firefox 3.5 upgrade planning; put together blog on current support at Mozdev and trying to compile lists of projects and extensions to contact about upgrading
• Improving page rendering time on Mozdev pages by ensuring that links/styles/scripts are ordered properly in the head tag
• Cleaning up our supported applications pages to make the extension totals clearer
• Wiki upgrade - switched from using the custom module update script I was using to drush; still has some bugs to iron out

This coming week I'd like to make sure the projects who need Firefox 3.5 support get notified early in the week and then I plan on finalizing the wiki upgrade process so we can have projects test out the changes. The upgrade seems to be working well on the projects and pages I tested, so we can probably move forward with the upgarde in the near future (the next week or so).

Last week's highlights include download graphs being rolled out to project overview pages and an update/test of our wiki.

• Fixed a bug in mirror bytes transferred calculations which capped the transfers at 4GB
• bug#20841 - added download stats to project overview pages
• Fixed bug with hash verification failing in file management tool
• Wiki upgrade progress with adding additional Drupal modules, default configuration, and testing of other sites

This week I'd like to do some more testing of the wiki upgrade for our projects and researching to see if there's anything Mozdev can do to help with or prepare for the Firefox 3.5 update.

Last week was mostly spent updating our mirror stats to track download sizes for mirrors and regions (so we have some estimate of how much traffic our mirror network pushes) as well as working on our Drupal wiki update.

• Started tracking download size per-mirror, per-region, and for each mirror/region combo
• Added per-region graphs and download size graphs for our mirror stats
• bug#18975 - Working on wiki upgrade to re-save content as HTML instead of wiki-syntax so we can use a WYSIWYG editor to make changes. The re-saving/conversion to HTML is going well; I'm currently trying to enable the new modules we would like to have after the upgrade and have them configured properly.

This week I hope to have the wiki upgrade process completed so I can begin testing with the hosted wikis we currently have. I'd also like to upgrade our project overview page to include download stats which should just be a matter of consolidating my previous work on the mirror stats into that page.