Nepomuk Contacts in 0.4 (sort of)!

[David Edmundson]

The following conversation just took place on IRC.

The problem:
 - TpLogger is crap, and instead of returning aliases in the method
TplEntity::alias() it just returns their email address.
 - I can't just query Telepathy as it's perfectly reasonable to look
up a log when you're offline, at which point you can't get a roster
(with actual names).
 - I imagine they killed support because they're merging with "Folks".
 - It's upstream so actually fixing it properly is a pain.

A proposed solution:
 - Given we're going to have (in all of KDE) nepomuk metacontacts this
seemed a good way to phase it in.
 - We ship ktp-nepomuk-service (possibly stripped down to what's
currently needed?)
 - In KTp-Log-Viewer we match up the accountID + contactID
 - Fetch alias from nepomuk, everything else from TpLogger

Why it's a good idea:
 - We phase in nepomuk gently.
 - We can test the nepomuk service.
 - No messing about with PIMO:Persons, purely just matching NCO:Contacts.
 - We can test chucking two datasources together in one model on a
completely static model where things are easiest.
 - Vishesh is going to do it, he can do anything.
 - We're going to need to do this when it's metacontacts in the logger
anyway, we're just using it for a very very simple case first before
we build things up.

If you don't have nepomuk:
 - you see an email addy instead of a name in the list of names at the
side of the log viewer, that's it.

What about using nepomuk for /all the logs/:
 - Not something being discussed right now. TpLogger works, lets not
change anything.

Obviously this depends on time constraints, if it's not done - we ship
with a minor bug, and it's purely optional.

 Let me know if you have comments.