This page details WikkiTikkiTavi Development and related pages. Some alternative ways to contribute are described at the bottom of the page.

Related Pages:

How to Contribute:

The easiest way to contribute is to add your ideas to TaviSuggestions, or bug reports to TaviBugs.

If you\'re interested in actually hacking on WikkiTikkiTavi, you should start by joining the TaviMailingList. This is where the \'Tavi developers discuss possible changes and new features.

There is also a SourceForge project page for \'Tavi at SourceForge:projects/tavi. You can submit bugs or features there, browse the CVS repository, e-mail the Tavi developers, and more. And its through SourceForge we make releases, and how to do that is described in (/HowToRelease)?.

TaviCVS:

WikkiTikkiTavi makes use of the ConcurrentVersionsSystem software for source code revision control.

You can browse the \'Tavi CVS repository from the web here: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/tavi/

The exact details of how \'Tavi makes use of CVS and how it\'s CVS setup is organized can be found at TaviCVS.

Patch File Submission:

Please submit patches either to the TaviMailingList, or the SourceForge patch submission page.

Patches should be generated with diff. Single file patches can be created with the -u option (unified) passed to the diff command. Multi-file patches (or single file patches, if you want) should be created by running diff from the top level \'Tavi directory, and passed the -N (new file), -a (treat as text), -u (unified), -r (recursive) options. For example, diff -Naur tavi.old tavi.new.

For feature additions and code changes, you should be generating your diff with cvs diff against the latest development version of the \'Tavi code. Remember to cvs update before generating the patch file. An example of a CVS patch is, cvs diff -Nau from within the top level of the checked out source directory.

For bug fixes, you may submit patches against the currently released stable code..