Hello List<div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>nco:Contact and Akonadi have a 1:1 mapping, but pimo:Person and nco:Contact would obviously have a 1:n mapping.</div><div><br></div><div>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. </div>
<div><br></div><div>Is everyone okay with this? Or does anyone have any other ideas?</div><div> </div><div>[1] <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/mck182/1">http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/mck182/1</a></div>
<div><a href="http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/mck182/1"></a>[2] <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://paste.kde.org/47137/">http://paste.kde.org/47137/</a><br>
-- <br><font color="#999999">Vishesh Handa</font><br>
</div>