Getting Started
First, it is recommended that you use a very recent CVS nightly build or get the code straight from CVS. There are two reasons for this:

• The bug you are attempting to fix or the feature you plan to add may already be in CVS, but just wasn't in the last stable release.
• Large portions of code can change greatly over a short period of time.

Coding Style
Patches are more likely to be accepted if they are in the same format and style as the rest of the code in the project. I won't purposefully reject a patch if it's coding style doesn't match the projects, but It definitely makes it easier on the developers when it does.

• Most variables should be in lowercase and use underscores (_) to separate words. Variables that reference interface elements (Buttons, Textboxes, ...) should capitalize every word after the first word (e.x. textBoxEelement).
  
  
• Use tabs not spaces. This is simply a preference of mine. I find that tabs in source code are easier to deal with than spaces are.
  
  
• Try to keep the maximum line width to 104 characters (using a tab-width of 8). Lines that need to be broken up into multiple lines should only be indented once under their parent line.
  
  e.x. x = get_value(1,
        really_long_function_name(c))
  
  

Patch Format
All patches should be generated from the root ToDo Manager source directory. If possible, the patch should be in the unified format. This can be accomplished with CVS by executing the following command:

cvs diff -u > patchfile.diff

You should consult the documentaion for any other software that you may use to generate the patch.

Submitting the Patch
Once the patch is completed you may submit it to the patch tracker at http://sourceforge.net/projects/todo-manager. Or you may email it as an attachment to click81@softhome.net.