On this page, you'll find small coding jobs for a beginner to work on. All these problems are relativley easy, some of them might even be one-liners. Of course, it is always a good idea to find your own thing to fix, the best motivation is scratching your own itch.
These tasks are intended for beginners with little or no experience programming with KDE. For those beginners, the biggest challenges are not actually the coding problems, but setting the development environment up, finding the correct place of code where the bug happens (in the jungle of all those source files) and interacting with the community, with the final step being sending the patch.
The knowledge prerequisite for those jobs are not that big. You should be familar in C++, and knowing Qt a bit would help. Knowing kdelibs or KMail internals is not required, that can usually be picked up during coding.
For more general information, visit the following places: KDE Techbase: Contains a lot of information about developing KDE, in particular a section on how to build KDE from source KMail's HACKING file: Some KMail specific information.
The steps for your first coding contribution are roughly like this:
1. Build KDE trunk from sources, including KDEPIM 2. Pick something to work on, like some of the things suggested below 3. Start coding and fix the problem! 4. Send in a patch
Should you need help, feel free to ask us in the #kontact IRC channel.
If you find some information missing, feel free to add it to this page after you learn it.
Below follows a list of junior jobs. It always includes a rough location where in the KMail sources to start.