Spreadthunderbird: Difference between revisions
Jump to navigation
Jump to search
Ken Saunders (talk | contribs) (→People) |
Graphicsguru (talk | contribs) (→People) |
||
| Line 5: | Line 5: | ||
== People == | == People == | ||
* Rafael Ebron (Project leader) | * Rafael Ebron (Project leader) | ||
* Jamey Boje | * [https://wiki.mozilla.org/User:Graphicsguru Jamey Boje] | ||
* [https://wiki.mozilla.org/User:Ken_Saunders Ken Saunders] | * [https://wiki.mozilla.org/User:Ken_Saunders Ken Saunders] | ||
* [https://wiki.mozilla.org/User:Paulbooker Paul Booker] | * [https://wiki.mozilla.org/User:Paulbooker Paul Booker] | ||
Revision as of 15:34, 10 October 2008
Background
- http://www.spreadthunderbird.com
- Community website for Thunderbird
People
- Rafael Ebron (Project leader)
- Jamey Boje
- Ken Saunders
- Paul Booker
- Ian Hayward
Milestones
- Current Bugs (Coming soon :-))
Source Code & Database
- SVN: http://svn.mozilla.org/projects/spreadthunderbird.com/ (To be confirmed)
- DB : (Coming soon)
Meetings
Every Thursday on irc.mozilla.com #marketing
Getting Started
- Check out the code
- Get the database
- Start coding
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
- Get svn access if you don't already
- Get a bug to work on
- Write code for the bug
- When done, create a patch, upload to Bugzilla and request a review
- Once the patch is ok'd, 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'. Please indicate if the changes have been committed back to drupal.org as it's important that we don't fork our distribution
- Mark the bug as fixed
- QA verifies bug and marks as VERIFIED if it's really been fixed
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.spreadthunderbird.com/ (To be confirmed)
- Updated automatically from trunk every 10 minutes (To be confirmed)
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.