For the third time, the town of Osnabrück was the place for a lot of KDE PIM hackers to hold their annual meeting, kindly hosted by Intevation. While theparticipants were primarily focused on fixing bugs and getting the various
PIM applications in shape for the KDE 3.4 release, some discussions also
targeted post-3.4 development.

With over 40 bugs fixed, some interestingfeatures implementented, the Kolab hackers participating, and thedraft for GroupDAV revised with Helge Hess from OpenGroupware.org, this
meeting was not only a successful boost of KDE PIM development, but also for
PIM client-server interoperability in general.

Let me explain, as a native Bavarian beer-drinker: Both descriptions are right. Though, people here in Munich prefer to call it "Weißbier", and people in other parts of Bavaria call it "Weizen". I have not so often heard the description "Weizenbier". But "Weißbier" is more official.

Nevertheless I prefer Schneider Weizen. I know Georg Schneider (the boss of the brewery) personally, and I know that they have excellent production standards. Besides, it is very tasty.

Well, last year we were in this Arabic (?) pub and they didn't serve any alcoholic beverages. So last year there was at least one pub without beer in Osnabrück. I guess you just don't go there. I can't blame you. :-)

at least, that's what the Ximian people inside Novell are going to try. From my point of view, that a bold venture. They'll need to apply massive changes to get it work, and it may even got stuck in the middle. Time will tell, if it's a good idea to already advertise it while they haven't done anything to the code yet.
I'm very pleased with the ongoings on KDE-PIM though. Kontact matures apparently. I think it would be a wasted effort to (officially) try to port Kontact/kdelibs to windows (well you never know, if kdelibs can be ported, maybe we'll even see apps like Kontact on windows one day)

Evolution... Now that chimes in with a discovery I made yesterday evening. I'm porting the Wet & Sticky paint model to Krita, and I needed a cut & dried rgb to hls color conversion routine. That particular routine wasn't yet in the KOffice painter lib, so I googled for something cut & pastable.

It turns out that (at least in some version) Evolution contains not just code to draw a bevelled button, but that that code also contains its own particular colourspace conversion routines:

I don't like to use the word 'bloat' in combination with code, mostly because that almost invariably exposes one as a complete ignoramus, but, well, I'd be tempted if I were sure that this code is actually inside a compiled Evolution.

Right now there is only a Qtopia Konnector available when using Multisynk or Kitchensync.
But there is also a IRmC Konnector , for Handys like Motorla T610 t630 in Kde-bluetooth. The Problem was that it has dependencies on KDEPIM and KDEBluetooth.
I also think that there is an SyncML Konnector , for Syncing newer devices or handies which already understand Syncml. (or pda's).
Can you make a plan to include those ? i used the irmc konnector with bluetooth quite a while, to sync my t630 with kadressbook, and its perfectly stable.

The inclusion of the mostly Bluetooth related sync stuff would benefit many people and would kick off sync usage and device integration.

are there plans to talk with the kde-bluetooth people for collaboration ?

Also a systray daemon for syncable devices would be nice if they are getting in range (detected).

I did once get it to work under KDE3.2. Syncing Evolution1 with either IRmC and the LDAP plugins. However, when I install Multisync and Evolution2, it looks as if it compiles all necessary plugins but won't show any of them under the resources. Just the default plugins as local, Qtopia etc. Right now, under KDE3.4, I can't even view my resources. It just crashes.

Should I compile all necessary apps manually with certain features enabled or disabled?