View source for AMO

== About ==
UMO provides web-based services like [http://addons.mozilla.org addons.mozilla.org] providing a resource for finding and installing Extensions and Themes for Firefox and Thunderbird, as well as the Plugin Finder and Application Update services.

== Project Status ==
There is a commit freeze for v1.0.  A full security audit is in progress.  Some features will be disabled until that is completed.  We will provide a more accurate timeline as it becomes available.

=== When is X going to happen? ===
Until we have a clear picture of what we have and where we are going, we won't have a timeline.  Right now the goal is to get an assessment completed by 2005-03-01 which will help drive our development efforts moving forward.

== Meetings ==
'''Next Conference Call:'''  [[Update:Conference_calls:2/17/2005|2/17/2005 at 3:00 p.m. PST]]
* [[Update:Status|Weekly status updates and conference call minutes]]

== Contact Information ==

=== General ===
*'''Mailing list:''' umo-admins@mozilla.org
*'''IRC:''' #umo on irc.mozilla.org

=== Leads ===
*'''Module Owner:''' Scott Kveton, [[User:kveton|kveton]] on irc.m.o
*'''Mozilla Foundation Lead:''' Christopher Beard, [[User:cbeard|cbeard]] on irc.m.o, cbeard at mozilla dot org

=== Collaborators ===
* [http://morgamic.com/ Mike Morgan], morgamic on irc.m.o
* Alan Starr aka alanjstr
* Chris Thomas, [[User:CTho|CTho]] on irc.m.o, cst at andrew,cmu,edu
* Colin Ogilvie, [[User:Csogilvie|Colin]] on irc.m.o, colin.ogilvie AT gmail DOT com
* Giorgio Maone, [[User:maotzetung|maoztetung]] on irc.m.o., g.maone at informaction,com
* Mike Connor, mconnor on irc.m.o
* Alex Sirota, [[User:iosart|iosart]] on irc.m.o., alex at elbrus,com
* Dave Miller, [[User:Justdave|justdave]] on irc.m.o (production system administrator)
* Barry Chen, chenb on irc.m.o

== Requirements ==
See a [[Update:Requirements|complete list of project requirements]].


== Infrastructure ==
* [[Update:Architecture_and_General_Design|Architecture and General Design]]
* [[Update:Infrastructure|Architecture Notes/Details/Requirements]]

In looking at the future, we need to identify what it's going to take to handle the UMO service during peak loads.  The community will not judge us on how sexy UMO is or the tools built around it.  We believe the community and pundits will be most critical of UMO if it fails to perform during peak usage.  If a new security update is released and UMO melts down, that will reflect poorly on the use of Firefox but also the Mozilla Foundation as a whole.

The [[Update:Infrastructure|existing infrastructure]] will not scale to handle peak loads at this time.  Peak loads will occur when new and popular extensions come out and most notably when security updates are released.  We need to build a scalable, reliable and secure infrastructure to handle the delivery of the UMO service to end users.

Corey Shields will be tasked with coming up with a plan for this and presenting it to the Mozilla Foundation system administrators.  The [http://osuosl.org OSL] would be willing to completely manage this service up to the application layer (including upgrades, etc) for the MoFo.

== Roadmap ==
=== v1.0 ===
We are only going to be doing security and performance fixes to this release.  This will tie into the [[Update:Development:v1.0|security audit]] which will identify any changes that need to happen before we turn UMO on with the v1.0 codebase.

* [[Update:Development:v1.0|Complete plan for v1.0]]
* http://update-dev1.mozilla.org 
* [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=MOZILLA_UPDATE_1_0_BRANCH&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=week&mindate=&maxdate=&cvsroot=%2Fcvsroot branch checkins]
* [https://bugzilla.mozilla.org/buglist.cgi?product=Update&amp;target_milestone=1.1&amp;resolution=--- open bugs]
* [[Update:Development:v1.0|v1.0 plans]]
* [[Update:Development:v2.0|v2.0 plans]]
* [[Update:Infrastructure|Deploying UMO : Infrastructure]]

=== v2.0 ===
The overall opinion is we should rewrite from scratch to take advantage of frameworks/tools to improve scalability and extensibility.  See the complete [[Update:Development:v2.0|v2.0 plan]].

* http://update-dev2.mozilla.org
* [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=%2Fmozilla%2Fwebtools%2Fupdate%2F&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=week&mindate=&maxdate=&cvsroot=%2Fcvsroot trunk checkins]
* [https://bugzilla.mozilla.org/buglist.cgi?product=Update&amp;component=Administration&amp;component=Developers&amp;component=Web+Site&amp;target_milestone=2.0&amp;resolution=--- open bugs]

== Developer's Guide ==
* [[Update:Development:Tools|Development Tools]]
* [[Update:Development:Best_Practices|Best practices and coding standards]]
* [[Update:Development:Server_Configuration|Supported Server Configuration]]
* [[Update:Development:Common_Code|Reusable Code]]
* [[Update:Development:Review_Process|Review Process]]

==== Staging Environment ====
The staging environment is a safe place stage our changes in the production environment.  The following URL is hosted on the production UMO servers.  This will allow us to make sure that our changes work in the existing server environment as well as do any final testing of the code.
* http://update-beta.mozilla.org/

== Other Documents ==
* [[Update:Architecture and General Design|Architecture and General Design]]
* [[Update:Development|Development: Guidelines, Best Practices and Tools]]
* [[Update:Website|End-User Website]]
* [[Update:Website:DevelopersSection|Developers Section of the Website]]
* [[Update:Suggestions|Suggestions for v2.0]]
* [[Update:A Vision for the Future|A Vision for the Future]]
* [[Update:Assessment|Assessing the Situation]]