[Nepomuk] Akonadi PIMO Integration
Vishesh Handa
handa.vish at gmail.com
Mon May 2 14:38:46 CEST 2011
Hello List
This year we have a KDE PIM and Nepomuk related GSoC project [1] - PIMO
Integration. The student - Martin Klapetek, his mentor - Volker Krause, and
I, had a meeting[2] this Sunday to discuss how he would go about
implementing this. This is a short summary of the meeting.
Martin's project consists of linking all the appropriate nco:Contacts with
pimo:Persons, merging duplicates, and propagating the changes made in a
contact up/down the chain. Here the chain would be PIMO -> NCO -> Akonadi.
nco:Contact and Akonadi have a 1:1 mapping, but pimo:Person and nco:Contact
would obviously have a 1:n mapping.
It was decided that a new Nepomuk service could host all the related code.
This would include the initial scanning for duplicates, and
change propagation. The change propagation will require us ( Nepomuk
developers ) to create a more appropriate resource watching mechanism.
Is everyone okay with this? Or does anyone have any other ideas?
[1]
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/mck182/1
<http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/mck182/1>
[2] http://paste.kde.org/47137/
--
Vishesh Handa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/nepomuk/attachments/20110502/1f708b8d/attachment.htm
More information about the Nepomuk
mailing list