From kde-core-devel Mon Dec 26 11:53:24 2011 From: Martin Klapetek Date: Mon, 26 Dec 2011 11:53:24 +0000 To: kde-core-devel Subject: Re: KDE Telepathy on its way to Extragear Message-Id: X-MARC-Message: https://marc.info/?l=kde-core-devel&m=132492925004995 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--f46d041b4a9636a47d04b4fd6b68" --f46d041b4a9636a47d04b4fd6b68 Content-Type: text/plain; charset=UTF-8 On Sun, Dec 25, 2011 at 22:39, Ben Cooksley wrote: > On Mon, Dec 26, 2011 at 10:26 AM, Martin Klapetek > wrote: > > Hello, > > Hi Martin, > > > > > > We're very short of releasing third version (0.3), which is also first > beta. > > We plan to introduce Nepomuk as main contact storage in the next release > > (June or July) and in the meantime we'll maintain 0.3 branch. > > Please ensure you store the main copy of the data somewhere outside > Nepomuk. In a large number of user support scenarios, especially those > involving an inconsistent Akonadi, it is necessary to destroy the > Nepomuk database to ensure ghost entries do not cause problems. > Right now we actually don't store any data. Everytime you open contact list, it fetches "fresh" data right from Telepathy. There will be a Nepomuk service, which will feed Telepathy data right into Nepomuk, so when you clear your Nepomuk database, the feeder will take care of filling it up again. There are some discussions about what to do with chat history, but this will most probably be the same case - Telepathy already stores it, so the feeder can just feed it to Nepomuk and recreate it on clean database. This hasn't been really decided yet though. > > If KDE Telepathy uses Nepomuk as it's primary store of contacts > information, it will make user support for other areas of KDE which > are still maturing much harder. > We plan to use it as a primary store, yes, but I also plan to have some discussion with KDE PIM on this subject as the unified contacts storage and handling is not exactly clear right now. > > There are also a number of users who have Nepomuk disabled, or a > system where Nepomuk is broken (due to old configurations, corrupt > databases, and the like). > We hope and believe that using Nepomuk as a hard dependency will help move Nepomuk forward and hopefully make it more lean&clean for production use. In the meantime, users will still be able to use the 0.3 branch, which will be Nepomuk-free and maintained for some time (especially if Kubuntu will decide to ship it in their upcoming LTS release). The interface will stay exactly the same, only the backend models will change. -- Martin Klapetek | KDE Developer > > > > > Thanks for all the support and happy holidays! > > -- > > Martin Klapetek | KDE Developer > > > > Regards, > Ben Cooksley > KDE Community Forums Administrator > --f46d041b4a9636a47d04b4fd6b68 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sun, Dec 25, 2011 at 22:39, Ben Cooksley <bcooksley@kde.org> wrote:
On Mon, Dec 26, 2011 at 10:26 AM, Martin Klapetek
<martin.klapetek@gmail.com<= /a>> wrote:
> Hello,

Hi Martin,

=
=C2=A0
>
> We're very short of releasing third version (0.3), which is also f= irst beta.
> We plan to introduce Nepomuk as main contact storage in the next relea= se
> (June or July) and in the meantime we'll maintain 0.3 branch.

Please ensure you store the main copy of the data somewhere out= side
Nepomuk. In a large number of user support scenarios, especially those
involving an inconsistent Akonadi, it is necessary to destroy the
Nepomuk database to ensure ghost entries do not cause problems.

Right now we actually don't store any data. Ev= erytime you open contact list, it fetches "fresh" data right from= Telepathy. There will be a Nepomuk service, which will feed Telepathy data= right into Nepomuk, so when you clear your Nepomuk database, the feeder wi= ll take care of filling it up again. There are some discussions about what = to do with chat history, but this will most probably be the same case - Tel= epathy already stores it, so the feeder can just feed it to Nepomuk and rec= reate it on clean database. This hasn't been really decided yet though.=
=C2=A0

If KDE Telepathy uses Nepomuk as it's primary store of contacts
information, it will make user support for other areas of KDE which
are still maturing much harder.

We plan= to use it as a primary store, yes, but I also plan to have some discussion= with KDE PIM on this subject as the unified contacts storage and handling = is not exactly clear right now.
=C2=A0

There are also a number of users who have Nepomuk disabled, or a
system where Nepomuk is broken (due to old configurations, corrupt
databases, and the like).

We hope and b= elieve that using Nepomuk as a hard dependency will help move Nepomuk forwa= rd and hopefully make it more lean&clean for production use. In the mea= ntime, users will still be able to use the 0.3 branch, which will be Nepomu= k-free and maintained for some time (especially if Kubuntu will decide to s= hip it in their upcoming LTS release). The interface will stay exactly the = same, only the backend models will change.

--
Martin Klapetek | KDE=C2= =A0Developer
=C2=A0

>
> Thanks for all the support and happy holidays!
> --
> Martin Klapetek | KDE=C2=A0Developer
>

Regards,
Ben Cooksley
KDE Community Forums Administrator

--f46d041b4a9636a47d04b4fd6b68--