kArm

KArm tracks time spent on various tasks. It is useful for tracking hours to be
billed to different clients or just to find out what percentage of your day is
spent playing Doom or reading Slashdot.

Abstract

This topic is about KArm development. If you want help on USING (not developing) KArm, please read the documentation that comes with your KArm: help://karm

Developers' info

KArm is part of the KDE module KDEPIM. KArm is based on KDEPIM's libkcal, a library to load and save calendars in the ical-format.
The KArm general documentation can be found here: http://developer.kde.org/documentation/library/cvs-api/kdepim/karm/html/index.html
The KArm classes documentation can be found here:
http://developer.kde.org/documentation/library/cvs-api/kdepim/karm/html/classes.html
How to compile kdepim for KDE 4 can be found here: KDE3To4.
You can watch the latest code as well as the latest code changes here:
http://websvn.kde.org/trunk/KDE/kdepim/karm/
You can request a mail in case of code changes within all of KDE here:
http://commitfilter.kde.org/
If you want us to do something for you or want to see what you can do for us, find our bugzilla here:
bugs.kde.org
KArm can be run stand-alone as well as part of kontact. This part is also called a plugin, the special form is a kPart. There are two files, one to implement the kPart, the other to implement the stand-alone KArm, that is why you might have to implement a function twice.
Developers communicate over the following channels:

• the mailing list kde-pim@kde.org
• irc.kde.org, channels #kontact and #kde-devel

How to change KArm's code

• have write access to the KDE subversion repository
• have a usecase
• find out that there is no code-freeze (best, ask on irc.kde.org, channel #kontact)
• test if the automated tests are working: make check in the KArm source dir
• do your change
• test if the automated tests are still working
• commit your changes