[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] jargon is bad! :)
From:       Thomas McGuire <mcguire () kde ! org>
Date:       2010-03-16 8:46:16
Message-ID: 201003160946.21172.mcguire () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,

On Tuesday 16 March 2010 09:40:20 Paul James Adams wrote:
> On Tuesday 16 Mar 2010 08:06:22 Thomas McGuire wrote:
> > but saying "importing into KMail" would be plain wrong now.
> 
> Technically, yes.
> 
> But think about this from the perspective of the user. All they see is
> KMail/Kontact. And why should they see/comprehend anything else? 

That's the problem. The user might be using Mailody or LionMail. If there was 
only Kontact, I'd agree.

> The
> average user treats their experience like a monolith; they don't know/care
> that the experience is actually delivered by a multitude of components
> with crazy names like "Akonadi". All they /think/ they are experiencing is
> the GUI in front of them.
> 
> What we should be doing when referring to Akonadi to users is to talk about
> it in terms of the utility it brings; referring to it by name is confusing
> at worst (I think we all agree on that) and vapid at best.
> 
> So how about referring to it as "KMail's mail synchronisation component" or
> some shizzle like that? Yes, this is wrong, but it is close /enough/ to the
> truth and it is something that users can understand.
> 
> In that respect, I have no problem with things like "importing into KMail".
> Whilst technically incorrect, it is meaningful to the user and not exactly
> a lie.


Regards,
Thomas

["signature.asc" (application/pgp-signature)]

_______________________________________________
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/

[prev in list] [next in list] [prev in thread] [next in thread]