Hacking Chandler

We'd like this page to be similar to http://www.mozilla.org/hacking/. Note that instructions for developing parcels (Chandler add-ons) can be found in the documentation wiki.

Once you've written code for Chandler (a bug fix or internal change), there are processes and procedures for getting it checked in. To get your code checked into osafoundation.org's Subversion repository you'll need to understand a number of things about how we collaboratively develop code:

• code development cycle
• coding practices
• checkin requirements

We don't have this well organized yet, but useful pages include

• ChandlerCodingStyleGuidelines
• PatchLifeCycle
• ChandlerCodeReviewProcess
• UpgradingExternalInternal -- how to add or upgrade libraries in /external or /internal directories
• CheckinRules
• BugWritingHelp
• ReleaseManagementWithBugzilla
• TestingChandler
• Tinderbox build status

You probably also want to have a reasonable understanding about the project's organization.