Contribute to Radio Downloader

If you have found Radio Downloader useful and would like to 'give something back', here are a few options:

Answer questions

Due to the number of people using Radio Downloader (and my limited free time), I can't give people as much help and support as I'd like.  You could help out by submitting answers to the current open questions in my FAQ, or adding comments to existing FAQ entries to add more detail or suggest corrections.

If you are unable to donate your time, financial contributions are always gratefully received to cover hosting and development costs.  There is a PayPal donate button at the very bottom of this (and every other) page, which goes to me directly.

Contribute code

I don't currently have enough time to implement all of the requested enhancements for Radio Downloader, so I'd welcome contributions of patches to implement these.

Prerequisites

You'll need the following before you can start developing:

These items are optional:

Getting started

Unzip the source code to a convenient location, open the Radio Downloader.sln solution file, and get cracking!

Picking a bug

In theory any bugs assigned to me and CONFIRMED (rather than IN_PROGRESS) are okay to work on, but please add a comment to the bug asking to have it assigned to you before starting work, as that saves wasted effort if I am working on it but have forgotten to change the status.

Submitting code

First make sure that your code follows the StyleCop and FxCop rules.  The projects are configured to scan for StyleCop violations during each build, but you will need to run FxCop manually as it takes a little longer.

When you are ready to submit, you will need to generate a unified diff of your changes (against the latest release) and then attach it to the bug in Bugzilla.

You can generate a unified diff on Windows using DiffUtils for Windows.  For instance, if the folder containing your modified code was called my feature, and you had a copy of the original source code in a folder called Radio Downloader then you could generate a diff with the following command:

diff -u -r -N "Radio Downloader" "my feature" > "my feature.diff"

Once you've checked to make sure the diff is nice and tidy, you can then attach it to the bug in Bugzilla (don't forget to check the 'This is a patch' box when you upload it).  I can then give your code a try and provide some feedback or apply it to the codebase.