664
edits
Changes
no edit summary
This page will help you:
* Get the source,
* Get set up, and
* '''Get Involved!'''
== Get the Source ==
SUMO can be checked out of Subversion:
svn co https://svn.mozilla.org/projects/sumo/trunk sumo
You'll find three directories inside the <code>trunk</code> directory:
trunk/
scripts/ -- Maintenance scripts and configuration files
tests/ -- QA tests
webroot/ -- The web app
== Get Set Up ==
We have detailed [[Support/SUMO_install_process|instructions]] for getting SUMO up and running.
=== Requirements ===
At a minimum, you'll need:
* [http://httpd.apache.org Apache] with [http://php.net/ PHP 5] (>=5.2 recommended)
* [http://www.mysql.com MySQL]
* [http://www.danga.com/memcached/ Memcached] (strongly recommended)
To work on the search system, you'll need [http://www.sphinxsearch.com/ Sphinx] (version 0.9.9-rc2 recommended).
== Get Involved ==
=== Bug Triage Meetings ===
We meet for 30-60 minutes every Tuesday to evaluated our progress and make sure bugs are targeted to the right milestone. The meeting time is:
* 9:00 AM PDT
* 12:00 PM EDT
Phone call details:
* California: 650-903-0800 then extension 92
* Toronto: 416-848-3114 then extension 92
[[Support/SUMOdev_Meeting_Notepad|Meeting notes]]
== Installing SUMO =Communication === The best way to get in touch with us is IRC::irc.mozilla.org, #sumodev
=== SUMOdev practices ======= Whiteboard strings ====
* runsql -- This bug has a SQL patch that needs to be run on production before/after code push.
* changepref -- At least one patch in this bug requires enabling/changing a preference
* Additional whiteboard strings related to tiki vs sumo bugs at [[Support/TikiUpstreamTriage#What]]
==== Commit policy ====
# With rare exceptions, always ask for review. Always post a patch, regardless. It may be acceptable to commit without review for e.g. string changes.
# Commit to trunk first. Once QA verifies the fix, commit to production and any other active branches (fennec, etc)
