AMO: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Replaced content with "#REDIRECT Add-ons '''Note: please see Add-ons for up to date information.'''")
 
(295 intermediate revisions by 69 users not shown)
Line 1: Line 1:
== About ==
#REDIRECT [[Add-ons|Add-ons]]
UMO (Updates Mozilla Org) 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 ==
'''Note: please see [[Add-ons|Add-ons]] for up to date information.'''
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.
 
== Volunteering ==
We are looking for volunteers to help us with UMO.  We are in need of PHP developers and people to review extensions and themes that get submitted to UMO.  If you are interested in being a part of this exciting project, please send information such as your fullname, timezone and experience to scott at osuosl dot org.  Also, please join us in #umo on irc.mozilla.org to start getting a feeling for what's up!
 
=== 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 ==
* [[Update:Conference calls:4/5/2005|4/5/2005 conference call minutes]]
* [[Update:Conference calls:3/17/2005|3/17/2005 conference call minutes]]
* [[Update:Conference calls:3/3/2005|3/3/2005 conference call minutes]]
* [[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 ===
* Mike Morgan, [[User:morgamic|morgamic]] on irc.m.o, Reviewer
* Alan Starr aka alanjstr
* Giorgio Maone, [[User:maotzetung|maoztetung]] on irc.m.o., g.maone at informaction,com, Reviewer
* Chris Thomas, [[User:CTho|CTho]] on irc.m.o, cst at andrew,cmu,edu, Reviewer
* Colin Ogilvie, [[User:Csogilvie|Colin]] on irc.m.o, colin.ogilvie AT gmail DOT com
* Mike Connor, mconnor on irc.m.o, Reviewer
* 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
* Johnny Stenback, [[User::jst|jst]] on irc, Plugin Finder Service.
* Paul Querna, [[User:chipig|chip]] on irc.m.o, chipig on freenode.
 
== 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&target_milestone=1.1&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&component=Administration&component=Developers&component=Web+Site&target_milestone=2.0&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]]
 
We grab the update and plugin files as well as the database every 4 hours from the production servers.  In addition, we also update the /data/update-dev and /data/update-staging via cvs every 4 hours as well.
 
=== Anonymous CVS Access ===
* http://www.mozilla.org/cvs.html
setenv CVSROOT :pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot 
cvs login
(password is "anonymous")
'''NOTE:''' you want to do this from your public_html directory:
cvs co -rMOZILLA_UPDATE_1_0_BRANCH -d . mozilla/webtools/update
 
=== Staging Environment ===
* https://update-staging.mozilla.org/
* /data/update-staging/
 
=== Dev Environment ===
* https://update-dev.mozilla.org:8080/
* /data/update-dev/
 
=== Sandbox Environment ===
Each developer can use a sandbox environment on chameleon.mozilla.org hosted in their public_html directory.  If you would like access to this environment talk with kveton in #umo on irc.mozilla.org.  This will allow you to do testing of patches and do custom development in your own sandbox and not affect the production development or staging environments.
 
* http://update-staging.mozilla.org/~username/
* /home/username/public_html
 
The latest dump of the UMO database is in /data/db on chameleon.  To use it just grab it and put it in your home directory and run:
 
* cp mozilla-update.sql .
* mysql -u username -p --database username < mozilla-update.sql
 
You can edit your database via phpmyadmin if you go to https://update-staging.mozilla.org/db/ using your sandbox username/password.  You will be asked to enter your password twice as the first one is an htaccess password to protect the phpmyadmin tool behind it.
 
No error messages will be displayed by default.  You can change that via .htaccess or ini_set - you must change display_errors to 1 and set error_reporting.  To do this, you can set the following in your config.php:
 
ini_set('error_reporting', E_ALL);
ini_set('display_errors', true);
 
== 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]]
 
 
== Reviewers/Editors Guide ==
 
UMO leverages reviewers/editors to look over pending extensions and themes for publication on the site.  We have a large number of extensions and themes and need a good coverage of timezones, etc to make sure we get them moderated in a timely fashion.

Latest revision as of 16:05, 17 February 2020

Redirect to:

Note: please see Add-ons for up to date information.

Retrieved from "https://wiki.allizom.org/index.php?title=AMO&oldid=1223890"