I did fail to provide any context. With Akonadi supporting lots of different address books, we end up with lots of contacts all making up the same person.
There was a plan to aggregate all of these inside Nepomuk. This is something that's been planned out with some PIM people, Nepomuk people (back in the time of Sebastian Treug doing it) long before I got involved. The goals are so when you get an email from someone, we can show an avatar from some alternate source, be able to start an IM chat, or load a LinkedInProfile. Other apps can use it differently. libkpeople provides: - a model for getting some data on lots of people - classes for getting lots of data on a contact - an API to merge/unmerge people - a plugin system (and some plugins) for starting actions on a contact - a plugin system (and some plugins) for displaying all this contact info I'm speaking as a developer of a KDE IM client, KTp, and we're using it soon as the metacontact problem is very prevalent. Most development has come from my team, but AFAIK, it's planned to eventually be used in kmail/korganiser etc. Long term, I'm not sure if it's going to a new library, or going into kdepimlibs. If KMail is going to depend on it, it will have to be into the main SC, and not extragear. Video on the subject here: http://files.kde.org/akademy/2013/videos/Vishesh_Handa,_Martin_Klapetek_-_People_in_KDE.webm David _______________________________________________ KDE-Telepathy mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-telepathy
