Spreadthunderbird

Background

• http://www.spreadthunderbird.com
• Community website for Thunderbird

People

• Rafael Ebron (Project leader)
• Jamey Boje (Marketing,Creative Director)
• Ken Saunders
• Paul Booker (Drupal Developer | Wiki page maintainer)
• Ian Hayward
• Philippe M. Chiasson (Server Operations)

Milestones

• Current Bugs (Coming soon :-))

Bespoke modules and derivative theme

• SVN: http://svn.mozilla.org/mozillamessaging.com/sites/spreadthunderbird.com/trunk/sites/all/modules/stb
• SVN: http://svn.mozilla.org/mozillamessaging.com/sites/spreadthunderbird.com/trunk/sites/all/themes/acquia_marina/stb

Contributed modules and themes

• http://drupal.org/project/cck 6.x-2.0-rc10
• http://drupal.org/project/views 6.x-2.0-rc5
• http://drupal.org/project/simpleviews 6.x-1.x-dev
• http://drupal.org/project/upload_image 6.x-1.x-dev
• http://drupal.org/project/image 6.x-1.0-alpha3
• http://drupal.org/project/imagecache
• http://drupal.org/project/service_links 6.x-1.0
• http://drupal.org/project/simplefeed 6.x-1.x-dev
• http://drupal.org/project/webform 6.x-2.2
• http://drupal.org/project/simplemenu 6.x-1.0
• http://drupal.org/project/captcha 6.x-1.0-rc2
• http://drupal.org/project/votingapi 6.x-2.0-rc1
• http://drupal.org/project/fivestar 6.x-1.13
• http://drupal.org/project/mollom 6.x-1.5
• http://drupal.org/project/devel
• http://drupal.org/project/acquia_marina 6.x-1.1
• http://drupal.org/project/affiliates 6.x-1.x-dev

Meetings

Every Thursday on irc.mozilla.com #marketing

Getting Started

1. Get drupal core
2. Get the list of contributed modules
3. Checkout our bespoke modules and our acquia derivate theme
4. Test the code ...

For more specific detailed instructions on how to setup a local MAMP server for development , please click here For generic instructions on setting up a local server on different OS's please click here

How to develop STB

1. Get svn access if you don't already
2. Get a bug to work on
3. Write code for the bug
4. If the bug fixes a problem with a contributed module on drupal.org then create a patch and submit for review on drupal.org by the module maintainer. As soon as the patch is accepted and the module updated then update the ticket so that the module can be updated on STB. If the bug fixes a problem with bespoke code that is in SVN then create a patch upload to Bugzilla and request a review.Once the patch is accepted, commit to SVN with the bug # in the commit message and a brief description of what the patch does or the bug title. Add a comment to Bugzilla with the revision number of the commit: 'rXXXX'.
5. Mark the bug as fixed
6. QA verifies bug and marks as VERIFIED if it's really been fixed
7. Please commit changes back to drupal.org wherever possible as it's important that we don't fork our distribution

Basic Functionality Testing

(Coming soon)

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

• http://stage.d6.spreadthunderbird.com/
• https://stage.d6.spreadthunderbird.com/ (points to the same location)
• Updated automatically from trunk every 10 minutes (To be confirmed)
• All pages are served behind a caching reverse-proxy

Deployment

• File an IT bug requesting that changes on stage be synchronised with production
• When IT closes the bug, verify the fixes/features are working.