[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-telepathy
Subject: Re: [Kde-pim] Contact aggregation
From: Martin Klapetek <martin.klapetek () gmail ! com>
Date: 2012-01-11 9:18:57
Message-ID: CAPLgePqOWZxyHwiuMufWGDcUA1-=qRNHYcBrnmMSYLMufgTBJg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Jan 9, 2012 at 12:00, David Edmundson <david@davidedmundson.co.uk>wrote:
> 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.
>
Exactly. And for that I'm a bit disappointed that so far it was only the
KDE Telepathy team discussing this across three mailing lists, but not a
single message from PIM (except Christian's) or perhaps even Plasma Active
guys :/
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.
>
That is absolutely true. But obviously I can't do it alone and should PIM
people not be interested, there's not much point doing it at all, because
we'd end up with two incompatible contact sources/storages, confused users
and raging comments everywhere.
--
Martin Klapetek | KDE Developer
[Attachment #5 (text/html)]
<div>On Mon, Jan 9, 2012 at 12:00, David Edmundson <span dir="ltr"><<a \
href="mailto:david@davidedmundson.co.uk">david@davidedmundson.co.uk</a>></span> \
wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 \
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My concerns with Pimo:Person (or equivalents) in KDE Telepathy is that<br>
no-one else is using it or appears to be moving towards it.<br>
<br>
We're only going this route to help feed our data to other<br>
applications, we don't exactly need it ourselves, we could do contact<br>
aggregation with a simple text file if we're the only people using \
it.<br></blockquote><div><br></div><div><br></div><div>Exactly. And for that I'm \
a bit disappointed that so far it was only the KDE Telepathy team discussing this \
across three mailing lists, but not a single message from PIM (except \
Christian's) or perhaps even Plasma Active guys :/</div>
<div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> People keep saying "it only \
works if everyone uses it", normally as an<br> argument for pushing this nepomuk \
side, but it also works the other<br> way. I don't want to be left out in the \
cold on our own maintaining an<br> over complicated library which isn't \
benefiting anyone.<br> <br>
Realistically either we (or rather Martin :-P) need to commit to<br>
switching to using Pimo:Person everywhere, i.e a brand new<br>
KAddressbook, updated KMail etc. rather than using Akonadi directly or<br>
this entire thing is just a completely pointless \
exercise.<br></blockquote><div><br></div><div>That is absolutely true. But obviously \
I can't do it alone and should PIM people not be interested, there's not much \
point doing it at all, because we'd end up with two incompatible contact \
sources/storages, confused users and raging comments everywhere.</div>
<div><br></div><div><div>--</div><div><font color="#666666">Martin Klapetek | KDE \
Developer</font></div></div></div>
_______________________________________________
KDE-Telepathy mailing list
KDE-Telepathy@kde.org
https://mail.kde.org/mailman/listinfo/kde-telepathy
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic