[Kde-pim] Contact aggregation

[David Edmundson]

My concerns with Pimo:Person (or equivalents) in KDE Telepathy is that
no-one else is using it or appears to be moving towards it.

We're only going this route to help feed our data to other
applications, we don't exactly need it ourselves, we could do contact
aggregation with a simple text file if we're the only people using it.

People keep saying "it only works if everyone uses it", normally as an
argument for pushing this nepomuk side, but it also works the other
way. I don't want to be left out in the cold on our own maintaining an
over complicated library which isn't benefiting anyone.

Realistically either we (or rather Martin :-P) need to commit to
switching to using Pimo:Person everywhere, i.e a brand new
KAddressbook, updated KMail etc. rather than using Akonadi directly or
this entire thing is just a completely pointless exercise.

David Edmundson

On Wed, Jan 4, 2012 at 9:38 PM, Christian Mollekopf
<chrigi_1 at fastmail.fm> wrote:
> Hey Martin,
>
> While I agree that the situation with Nepomuk is less then ideal right now
> regarding its maintenance, it would IMO be a very bad idea to abandon Nepomuk
> now. The KDE community has the unique chance to make the semantic desktop fly,
> with huge potential. The whole workspace seems  very committed to nepomuk and
> many other projects, such as PIM, are starting to  use it successfully.
> Therefore I believe that this community is capable of  maintaining Nepomuk,
> now that all the important parts are in place (with the addition of the dms).
> Nepomuk has come a long way to where it is today and I would find it very sad
> if people start jumping off now.
>
> I think you now the potential yourself and what a waste it would be to not use
> that now. I can only say, the more people are using Nepomuk, the better the
> solution will be. I myself will certainly continue to improve nepomuk
> integration in PIM and Zanshin (after my exams that is =)
>
> Only if projects start to really use it, it becomes more than an advanced
> desktop search/indexing service.
>
> But even that aside I believe Nepomuk is a very good framework for what you
> want to achieve. Not only does it already provide some merging heuristics, but
> also is it one of it's core concepts to integrate with various applications
> (the semantic desktop). So the work is done once and can be used everywhere.
>
> I really hope you'll help to strengthen Nepomuk, providing a whole new level
> of application integration =)
>
> Cheers,
> Christian
>
> On Tuesday 03 January 2012 16.39:30 Martin Klapetek wrote:
>> Hi,
>>
>> I currently work on a contact library based on Nepomuk's PIMO:Person, which
>> will later be foundation of KDE Telepathy's contact list and possibly new
>> semantic KAddressBook. The more it's advancing, the more people are voicing
>> their concerns about it. Some people are calling after using libfolks as
>> the main KDE's contact aggregation solution, some wants to have completely
>> different things and some wants to proceed with Nepomuk's PIMO:Person,
>> which is imho really good, but has it's drawbacks and an uncertain future.
>>
>> Therefore I'd like to ask the people who are the most capable to give
>> advices in this regard - what do you think it's the best contact
>> aggregation solution for KDE? What should we use in KDE Telepathy as an
>> aggregation service? What would suit the PIM as the best? What could be
>> used by other apps easily (eg. DigiKam and their face recognition, these
>> can also be "contacts" and you should be able to contact them easily right
>> from the app)?
>>
>> Cheers!
>> --
>> Martin Klapetek | KDE Developer
>> _______________________________________________
>> KDE PIM mailing list kde-pim at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-pim
>> KDE PIM home page at http://pim.kde.org/
> _______________________________________________
> KDE-Telepathy mailing list
> KDE-Telepathy at kde.org
> https://mail.kde.org/mailman/listinfo/kde-telepathy