Here are some idea of how you can contribute
Below we give you more detail on these:
Before we release new versions of the Toolkit we need people to check that they still work correctly. If you are a frequent user you might want to start using the release candidate on your current work and report any errors before we release them.
Compile and install the software to see if we have any platform issues
Check for any files that are missing, tools that were not installed, etc.
Run unit tests to see if there are any issues. Please report any failures.
Finally, simply work with the software. Checking all your current usage patterns and report problems.
Now you need to try and validate the bug. Your aim is to confirm that the bug is either fixed, is invalid or still exists.
If its fixed please close the bug and give details of how when it was fixed or what version you used to validate it as corrected.
If you find that the bug reporter has made the incorrect assumptions or their suggestion cannot work. Then mark the bug as invalid and give reasons why.
The last case, an existing bug is the most interesting. Check through the bug and do the following:
Don't ignore this area if you feel like you are not a hotshot coder!
You will need some Python skills, this is a great way to learn.
Here are some ideas to get you going:
Now is the time to familiarise yourself with the developers guide.
This is the easy one. Login to the wiki and start!
The key areas that need to be looked at are:
After that and always: