--===============7525731958535893149==
Content-type: multipart/signed; boundary=nextPart1709795.DRBYSSfzQ9;
 protocol="application/pgp-signature"; micalg=pgp-sha1
Content-transfer-encoding: 7bit

--nextPart1709795.DRBYSSfzQ9
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Thursday 07 March 2013, Lindsay Mathieson wrote:
> On Thu, 7 Mar 2013 04:24:25 PM Kevin Krammer wrote:
> > Well, yes, as opposed to be a storage. Item data is not stored in
> > the Akonadi  DB, small parts can be cached there, or kept until
> > they could be written back (offline mode).
> >=20
> > Maybe it would have been better to just ignore all the trolls who
> > thought they  knew better but at the time it seemed possible to
> > educate at least interested users that data was still stored on
> > servers or locally in open formats.
> >=20
> > I think it wasn't clear that even those users would then simplify
> > everything  down to just that bit of information and forget every
> > other information available.
>=20
> This is starting to sound like the "KDE 4.0 was not meant to be used
> by users" story.
>=20
> At the beginning of the akonadi roll out  It was extensively posted
> that the db was just a cache. It pretty universal in Internet usage
> that a cache is just a cache and clearing it won't have any bad side
> effects. To blame users for assuming common usage of the term is
> disingenuous, it was a mistake to publicly call it that in the first
>  place.

I'm not 100 % sure, but I think that at the beginning of the Akonadi=20
rollout Akonadi's database indeed contained only cached data. With later=20
versions of Akonadi this has changed. Does this make the initial=20
statement made at the beginning of the rollout wrong? I don't think so.=20
Was the decision to add non-cached data to the DB a mistake? I don't=20
think so either. Could we have stated more clearly that at some point in=20
time Akonadi's database started to contain not just cached data?=20
Probably.

Assuming that statements made in the past stay true forever is=20
dangerous. That's something everybody should keep in mind.

Communicating that statements made in the past are no longer correct is=20
important. That's something we need to keep in mind.


Regards,
Ingo

--nextPart1709795.DRBYSSfzQ9
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iEYEABECAAYFAlE/p4oACgkQGnR+RTDgudhBOACgr2kOA/ueEpOAZelxwRMpKLo2
nLQAn0IYRlFhli9bkMogI+2OogZKZTOe
=o7OJ
-----END PGP SIGNATURE-----

--nextPart1709795.DRBYSSfzQ9--

--===============7525731958535893149==
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/
--===============7525731958535893149==--