Support:Sumodev
- This page is for people interested in working on the support.mozilla.com (SUMO) web application. If you want to contribute to SUMO's knowledge base or forums, head to Support or the Contributor Home Page.
Want to use your web development skills to help 300 million Firefox users? Start contributing to SUMO! (support.mozilla.com)
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 trunk directory:
trunk/ scripts/ -- Maintenance scripts and configuration files tests/ -- QA tests webroot/ -- The web app
Get Set Up
We have detailed instructions for getting SUMO up and running.
Requirements
At a minimum, you'll need:
To work on the search system, you'll need Sphinx (version 0.9.9-rc2 recommended).
Get Involved
Development environment
- It's best to develop on a UNIX-based system. For example, our developers use Ubuntu or Fedora. See James Socol's post about his development environment for SUMO or Paul Craciunoiu's similar post
- Checkout our source code:
svn co https://svn.mozilla.org/vc/projects/sumo/trunk/ sumo
- Visit our wiki page for the install process: Support/SUMO_install_process
- Ask one of our team members for a copy of the database
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
- 18:00 CEST
Phone call details:
- California: 650-903-0800 then extension 92
- Toronto: 416-848-3114 then extension 92
- Toll-free: 800-707-2533 then password 369
- Skype (free): +18007072533 then password 369
Then, enter the conference number: 309#
irc.mozilla.org: #sumodev
Communication
The best way to get in touch with us is IRC:
People:
- James Socol
- Email: james[at]mozilla.com
- IRC nick: jsocol
- Paul Craciunoiu
- Email: paulc[at]mozilla.com
- IRC nick: paulc
SUMOdev practices
How pushes work
- Only trunk/ is used.
- For a given milestone, we have a code freeze (no commits) for about a week after all bugs are fixed.
- Once all bugs are verified, we push the site live during a push window (usually Tuesdays or Thursdays)
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.
Useful links
- WikiMo:
- TikiWiki: