AMO

About

addons.mozilla.org is a resource for finding and installing Extensions and Themes for Mozilla products.

Schedule

Date	Task
December 31	Split developer and public pages in CVS
End of March	Complete and release public v2.0 code and begin focus on developer tools
April-May	Rewrite of developer tools one-script-at-a-time

TODO

v1 migration

• migrate install.php
  • make sure we are still collecting pseudo-stats
• migrate finalists.php page
• migrate winners.php page, front page change for winners.php
• search-engines.php, search-engines-static changes
  • move images/search-engines/* to search-engines-static/
  • images in this directory are duplicated between the two (because of shaver)
• rss and other query changes for popular/newest
  • situations involving joins across main, version need to be reexamined for accuracy

leftovers for morgamic

• optimize search results
• add search results pagination
• add comments pagination and orderby

critical TODO

• ensure seamlessness between public side and existing developer/ side - clouser (this is already taken care of)
• modify setters or getters that don't do one or the other to do one or the other - morgamic
• add the ability to take an app GUID as a query param then rewrite it as ?app===appname
  • this is used in the "get more extensions" link to addons.mozilla.org found in the client
• add ability to use SeaMonkey app -- make app more dynamic
• add "where supported==='1'" to app queries
• Fix the javascript so the +'s don't show up when you're logged in -- (clouserw)
• Change background color of "install now" to green (like mozilla.com) -- (clouserw)
• Make the "install now" detect the OS -- (clouserw)

qa

• make sure that install.php is logging hits/downloads - morgamic
• check that maintenance.php works correctly - morgamic
• verifying that update script works (update.php allows you to update an extension) - morgamic
• link checker to verify we don't have 404's
• no php errors or warning in E_ALL
• validation on every page
• no js console errors or warnings
• get testers to click through
• decide which URLs we need to rewrite to their new locations, which ones we will let break
• Try to create a new account, but leave one password blank. The error says look below, but there are no errors below.

DONE

session

• add sessions table to database
• either modify existing or rewrite session class
  • create
  • check cookie
  • logout / destroy
  • add gc function for deleting expired records

• login script
  • take username/password, create valid session for registered users
  • redirect to the referrer on auth, like the create account page
• logout script
  • call session destroy, show logout confirmation

.htaccess

• .htaccess-dist, remove morgamic from this

rss < 1hr

• reimplement all rss feeds

recommended.php

• make listing dynamic, migrate existing content

front page

• make feature dynamic, switchable based on application

comments < 1hr

• add UserID to feedback table in order to link users to comments
• write comment form for adding comments to addons
• add session checks / login requirement to both pages (addcomment.php, ratecomment.php)

logins

• create account page (redirects to referrer on auth)
  • when a user first registers, their UserMode is 'D'
• verify account script (compare confirmation code, then flag account as active)
  • when a user comes in with the proper email/confirmation code, their UserMode is set to 'U'
• forgotten password
  • enter email address
  • email them another link
  • user clicks on link
  • goes to form
  • form allows them to change pw, but only if they reset their password in the last couple of hours
• change config-dist.php to make new app know web address of login page
• debug missing app data in search results page - N/A

odds and ends

• modify configuration to use a shadow db for read-only queries - morgamic
  • get relative path from webroot and check to see if current script is in the $use_shadow_db array (or whatever it's called)
  • if it is in_array(), use shadow, if not use master
• centralize cache status and cache lifetime settings per-page using a central config array, much like shadow - morgamic
• set up caching, simulate a production environment - morgamic
• rewrite page output caching to use memcached instead. - morgamic
• add compat grid for application compatibility - clouser
• double check v2.sql against a diff between v1 and v2 databases - clouser

testing

• find a box to test on that would serve as a good control - morgamic
• choose testing suite (ab or httperf or other?) - both
• enable caching, and test requests per second for same pages on v2 - clouser
• log results, make pretty puffy.dll graphs, maybe, if time permits :) - clouser
• double check database indexes - clouser
• test requests per second for a handful of pages for v1 - both
• other comprehensive testing for various configurations - both
• test with memcache, rerun master test script, add to results

deployment

• document deployment requirements and instructions for server infra team
  • listing any requirements that differ from v1 (Smarty, db changes, existence of cache directories)
• choosing a date and time and being available to work with sysadmins

server testing

• give APC a shot, and see if it has gains over phpa - morgamic

non-critical TODO (cosmetic)

• do not display comment ratings that have no rating
• do not display "removed by staff" comments

leftovers for morgamic

• fix search page layout

critical TODOs

• add gc function calls to maintenance.php and add to crontab
• change version selection so we can pull out os-specific links
• add JS to display the proper download link based on OS in UserAgent string

v1 migration

• migrate PFS data, and figure out what to do there

Roadmap

v1.0

v1.0 was released, based in part on work done in the security audit. Further revisions will be addressed on a case-by-case basis as our efforts turn towards v2.0, which is based on a much better framework.

v2.0

addons.mozilla.org will be rewritten. v2.0 has two key points:

• reimplement and fix existing features and functionality
• add new features and functionality

We realize that rewriting has been a long time coming. This is why we have reevaluated our situation and have set more realistic short-term goals.

Read the v2.0 plan.

• Trunk check-ins this week

Contact Information

Weekly Meetings

Tuesday, 2pmPST, 1(866)489-0573 - *4432040*

General

• Mailing list: umo-admins AT mozilla DOT org
• IRC: #umo on irc.mozilla.org

Leads

• Project Manager: Rafael Ebron, rebron on irc.mozilla.org
• Module Owner: Mike Morgan, morgamic on irc.mozilla.org

Collaborators

• Mike Morgan, morgamic on irc.m.o, Reviewer
• Alan Starr aka alanjstr
• Giorgio Maone, maoztetung on irc.m.o., g.maone at informaction,com, Reviewer
• Chris Thomas, CTho on irc.m.o, cst at andrew,cmu,edu, Reviewer
• Colin Ogilvie, Colin on irc.m.o, colin.ogilvie AT gmail DOT com
• Mike Connor, mconnor on irc.m.o, Reviewer
• Alex Sirota, iosart on irc.m.o., alex at elbrus,com
• Dave Miller, justdave on irc.m.o (production system administrator)
• Barry Chen, chenb on irc.m.o
• Johnny Stenback, [[User::jst|jst]] on irc, Plugin Finder Service.
• Paul Querna, chip on irc.m.o, chipig on freenode.
• Joey Gannon, jgannon on irc.m.o, jgannon at ticalc dawt org, Reviewer
• Rafael Ebron on irc.m.o, rebron or rebron at mozilla.com
• Michael L. Hostbaek, mich on irc.m.o, Reviewer
• Ray Booysen, Twyford on irc.m.o, Reviewer
• Daniel Steinbrook, MarbleheadMan on irc.m.o, dsteinbrook at that e-mail service by Google dot com, Reviewer, Marketing Relations Assisstant, Lead of Bugging Admins to Finally Add Features That Users Want

Volunteering

We are looking for volunteers to help us with UMO. We are in need of PHP developers to help with redesigning the site, and people to review extensions and themes that get submitted to UMO. We especially need mac OS users, and Thunderbird users. If you are interested in being a part of this exciting project, please do the following:

For Reviewers

1. Create an UMO account at https://addons.mozilla.org/developers/createaccount.php

2. Send an email to umo-reviewer at mozilla.org with the subject "UMO Volunteer Step 1". The email should contain: the name you used when creating your account and the email address you used for the account. Please also mention which products you use (i.e. Firefox, SeaMonkey, Mozilla, etc) on which operating systems, and any experience you have testing or creating extensions.

3. If you're also interested in being a developer, please see below.

Also, please join us in #umo on irc.mozilla.org to start getting a feeling for what's up!

If you sent your request before November and have not received a response, please email us again, following the directions above.

For Developers

Stop by #umo-dev on irc.mozilla.org - you'll probably want to talk to morgamic.

Addon Developer's Guide

Developer's Section

Reviewers/Editors Guide

Guide to Helping

Website Developer's Guide

Website Developer's Guide

Requirements

• Software Integrity Policy for Mozilla Update

• See a complete list of project requirements.

End User's Guide

End-User Website

Software Update

Software Updates