Spreadfirefox Dev Tips: Difference between revisions

Revision as of 06:18, 30 March 2009

Although some content is specific to Bugzilla, Bugzilla:Developers is a good example of how development works in general on Spread Firefox (and Mozilla in general).
Use PEAR coding style
Comment your code.
- Function definition blocks at the least
- Inline comments for complex code, use your best judgment
Always put a bug # and descriptive comment about the changes in your SVN commit messages.
Don't embed HTML code in PHP code.
- 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.

- cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal co -r DRUPAL-<TAG> drupal
How to checkout a contributed module from CVS
- cvs co -r DRUPAL-<TAG> -d <CONTRIBUTED-MODULE> contributions/modules/<CONTRIBUTED-MODULE>
How to update drupal core or contributed module to a new release
- cvs update -r DRUPAL-<TAG>

Please commit changes back to drupal.org wherever possible as it's important that we don't fork our distribution

@@ Line 1: / Line 1: @@
 [[Spreadfirefox|Spread Firefox wiki home]]
+* Although some content is specific to Bugzilla, [[Bugzilla:Developers]] is a good example of how development works in general on Spread Firefox (and Mozilla in general).
 * Use [http://drupal.org/coding-standards PEAR coding style]
 * Comment your code.