Spreadfirefox

Background

People

  • Paul Booker
  • Alix Franquet
  • Alex Buchanan

Milestones

Source Code

Meetings

Getting Started

SFX runs on a default MAMP install with no issues.

  1. Checkout the code
  2. Get the database
  3. Start coding

How to develop SFX

  1. Get svn access if you don't already
  2. Get a bug to work on
  3. Write code for the bug
  4. When done, create a patch, upload to Bugzilla and request a review
  5. Once the patch is ok'd, commmit to SVN with the bug # in the commit message and a brief description of what the patch does or the bug title
  6. Add a comment to Bugzilla with the revision number of the commit: 'rXXXX'
  7. Mark the bug as fixed
  8. QA verifies bug and marks as VERIFIED if it's really been fixed

Do's and Don'ts

  • Use PEAR coding style
  • Always comment your code.
    • Function definition blocks at the least
    • Inline comments for complex code, use your best judgment
  • Always put a bug # and comment in your commit messages.
  • Don't embed HTML code in module files.
    • Define templates and keep presentation separate from logic code.
  • Don't touch the Drupal core. If you think you absolutely have to, ok it with another developer and document where and why you did so.
  • Don't push on Fridays or when you won't be around to verify the changes.

Staging Server

Deployment

  • Merge the changes you want into tags/production
  • File an IT bug requesting an update with the svn revision # and the expected changes/fixes
  • When IT closes the bug, verify the fixes/features are working.