Difference between revisions of "Projects/PIM/KMail Junior Jobs"

< Projects‎ | PIM
Jump to: navigation, search
(add inital content)
 
(wikify a bit)
Line 2: Line 2:
  
 
On this page, you'll find small coding jobs for a beginner to work on.
 
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.
+
All these problems are relatively 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.
 
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.
 
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.
+
The knowledge prerequisite for those jobs are not that big. You should be familiar 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:
 
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
+
* [[Welcome_to_KDE_TechBase|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.
+
* [http://websvn.kde.org/*checkout*/trunk/KDE/kdepim/kmail/HACKING KMail's HACKING file]: Some KMail specific information.
  
 
The steps for your first coding contribution are roughly like this:
 
The steps for your first coding contribution are roughly like this:
  
1. Build KDE trunk from sources, including KDEPIM
+
#Build KDE trunk from sources, including KDEPIM
2. Pick something to work on, like some of the things suggested below
+
#Pick something to work on, like some of the things suggested below
3. Start coding and fix the problem!
+
#Start coding and fix the problem!
4. Send in a patch
+
#Send in a patch
  
 
Should you need help, feel free to ask us in the #kontact IRC channel.
 
Should you need help, feel free to ask us in the #kontact IRC channel.
Line 26: Line 26:
 
Below follows a list of junior jobs. It always includes a rough location where in the KMail sources to start.
 
Below follows a list of junior jobs. It always includes a rough location where in the KMail sources to start.
  
=== Folder quick search should have "Search" as inital search text ===
+
=== Folder quick search should have "Search" as initial search text ===
 
=== Pressing enter in the filter dialog opens the help by default ===
 
=== Pressing enter in the filter dialog opens the help by default ===
 
=== The default column sizes of the message structure viewer are too small ===
 
=== The default column sizes of the message structure viewer are too small ===
Line 33: Line 33:
 
=== Unify options to enable or disable the tooltips in the folder and message list ===
 
=== Unify options to enable or disable the tooltips in the folder and message list ===
 
=== Better handling of empty column titles in the message list ===
 
=== Better handling of empty column titles in the message list ===
=== Bug 187041: Folder filter persistant after restart ===
+
=== Bug 187041: Folder filter persistent after restart ===
 
=== Bug 186803: Missing newline in folder tooltip ===
 
=== Bug 186803: Missing newline in folder tooltip ===
 
=== Bug 185069: After renaming a SMTP account, the identities are not updated ===
 
=== Bug 185069: After renaming a SMTP account, the identities are not updated ===
 
=== Bug 182581: KMail should warn when creating a filter without a filter action ===
 
=== Bug 182581: KMail should warn when creating a filter without a filter action ===
=== Bug 156653: Changing the font size has no effect on the seperate reader window ===
+
=== Bug 156653: Changing the font size has no effect on the separate reader window ===

Revision as of 23:40, 19 March 2009

Contents

KMail Junior Jobs

On this page, you'll find small coding jobs for a beginner to work on. All these problems are relatively 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 familiar 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.

Folder quick search should have "Search" as initial search text

Pressing enter in the filter dialog opens the help by default

The default column sizes of the message structure viewer are too small

Add an indicator to the composer's toolbar whether the mail is in plain text or HTML

Move aggregation, theme and sorting options to the menubar

Unify options to enable or disable the tooltips in the folder and message list

Better handling of empty column titles in the message list

Bug 187041: Folder filter persistent after restart

Bug 186803: Missing newline in folder tooltip

Bug 185069: After renaming a SMTP account, the identities are not updated

Bug 182581: KMail should warn when creating a filter without a filter action

Bug 156653: Changing the font size has no effect on the separate reader window


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal