So you want to volunteer, eh? Great! Here's how you go about doing it:

First, download the latest version of the code. Decompress, compile and start it up as described in the quick-start guide. See how the code operates and then look through the code and see how it's doing what it's doing. You will notice as you use your client that certain functionality is missing. That's a good thing to implement.

So, let's say you've decided to implement missing functionality. Email me and let me know what you're doing; the nature of your changes, your plan of attack, time to completion, etc. I will write back to you and either ACK or NAK, depending on whether or not the particular piece is being worked on already, if it's out of scope, etc.

That's it. There is no CVS source code tree available externally, so all patches have to come through us. Any patches you make, realize, are subject to the force of consistency. That is to say, any code you turn over may be modified to fit into our program scaffolding. Do not worry though, your code will be properly documented as to the author, scope, change date, etc. You'll also get your own place on the list of volunteers on the people page. Cool, huh?

If you can't think of anything to do, check out our todo page.