Spreadfirefox Dev Tips: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Spreadfirefox|Spread Firefox wiki home]]
[[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]
* Use [http://drupal.org/coding-standards PEAR coding style]
* Comment your code.   
* Comment your code.   
Line 10: Line 11:
* 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 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.
* Don't push on Fridays or when you won't be around to verify the changes.
 
* [http://drupal.org/handbook/cvs/quickstart Drupal CVS]
=== How to anonymously download drupal from CVS ===
* Please commit changes back to drupal.org wherever possible as it's important that we don't fork our distribution
**cvs -z6 -d:pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal co -r DRUPAL-<TAG>  drupal
* For specific detailed instructions on how to setup a local MAMP server for development , please click [https://wiki.mozilla.org/Local_development_with_mamp here]
* How to checkout a contributed module from CVS
* For generic instructions on setting up a local server on different OS's please click [http://drupal.org/node/157602 here]
**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>
 
=== Notes ===
#Please commit changes back to drupal.org wherever possible as it's important that we don't fork our distribution

Latest revision as of 06:26, 30 March 2009

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 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.
  • Drupal CVS
  • Please commit changes back to drupal.org wherever possible as it's important that we don't fork our distribution
  • For 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
Retrieved from "https://wiki.mozilla.org/index.php?title=Spreadfirefox_Dev_Tips&oldid=136896"