From kde-pim  Sun Jan 05 21:18:39 2014
From: Till Adam <adam () kde ! org>
Date: Sun, 05 Jan 2014 21:18:39 +0000
To: kde-pim
Subject: Re: [Kde-pim] Making Akonadi fit for embedded use
Message-Id: <4727862.B1Vpgc1frB () localhost>
X-MARC-Message: https://marc.info/?l=kde-pim&m=138895674001732
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============2755490361612694132=="


--===============2755490361612694132==
Content-Type: multipart/signed; boundary="nextPart1581879.gphVVag3bQ"; micalg="pgp-sha1"; protocol="application/pgp-signature"


--nextPart1581879.gphVVag3bQ
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Sunday, January 05, 2014 10:10:48 PM Manuel Nickschas wrote:
> On Sunday 05 January 2014 19:42:42 Till Adam wrote:
>=20
> Hi Till,
>=20
> > On Wednesday, October 31, 2012 10:29:27 AM Manuel Sput Nickschas wr=
ote:
> > > As people frequenting #akonadi already know, I'm currently evalua=
ting
> > > the
> > > use of Akonadi for an embedded Linux platform.
> >=20
> > I'm curious, do you have an update on this? Shelved?
>=20
> As it happens, we had some slight change of priorities in the past ye=
ar,
> thus we didn't have time to delve more into the topic of PIM. However=
, for
> the evaluation prototype we managed to get Akonadi (with KDE4 and X11=
...)
> running on our platform and thus were not urgently in need of having =
a
> frameworkified, splitted version of kdepimlibs for doing the major pa=
rt of
> our evaluation. Let's say Akonadi came out favorable compared to the
> alternatives, and with Frameworks now getting close to a release, pro=
bably
> things should look even better if we should happen to revisit the PIM=
 topic
> at some point. There were some open questions in particular regarding=

> per-user encryption that we did not have a solution for. On the plus =
side,
> all developers involved liked the Akonadi architecture and APIs very =
much.
> A final decision, however, was never made, because the architects=E2=84=
=A2
> refocused their attention.
>=20
> My work on splitting kdepimlibs never got finished, as just deploying=
 the
> full version for the prototype proved to be a sufficient short-term
> solution, and I don't think there's any use in upstreaming any of it,=
 since
> the codebase and build system have changed in major ways in the last =
year
> anyway.
>=20
> I'm quite confident that the topic will come back to us at some time,=
 at
> which point we'll re-evaluate things. I'll let you know if there's an=
y
> news, of course.
>=20
> Thanks for your interest and all the help I got from you and various =
other
> people, especially David and Stephen, it was very useful even though =
in the
> end we only got a whitepaper out of it :)

Thanks a lot for the update. And I would love to see that whitepaper at=
 some=20
point :).

Cheers,

Till

--nextPart1581879.gphVVag3bQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEABECAAYFAlLJzC8ACgkQtrsWGirveVtsAQCgxm6pdTsxAN0+NbX/c0JoQbxS
N/AAoOHf06U1nsXFZnG0wrnJDct/ZtBu
=vlJz
-----END PGP SIGNATURE-----

--nextPart1581879.gphVVag3bQ--


--===============2755490361612694132==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============2755490361612694132==--