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

List:       kde-pim
Subject:    Re: [Kde-pim] jargon is bad! :)
From:       Ingo =?iso-8859-15?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2010-03-24 20:58:44
Message-ID: 201003242158.45576 () thufir ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday 23 March 2010, Sven Burmeister wrote:
> Am Montag, 22. März 2010 21:38:46 schrieb Ingo Klöcker:
> > On Monday 22 March 2010, Sven Burmeister wrote:
> > > I would not avoid using the term akonadi, since it is kind of a
> > > trademark to promote. But one should use it as such, i.e. add it
> > > to the non-jargon expression like: your email will be imported
> > > into the central kde data storage (akonadi)...
> > 
> > Akonadi is no data storage. Moreover, it's completely independent
> > of KDE.
> > 
> > Akonadi is a desktop agnostic PIM data access
> > API/service/layer/whatever.
> 
> That's not the point.

Okay. Sorry, for my nitpicking.


> The point is to have a description the user

Who is The User (tm)? Is it my fellow KDE PIM hacker Thomas McGuire? Is 
it my co-worker Michael (who is a software developer)? Is it my brother 
who has fair knowledge of computers? Is it my co-worker's wife who is a 
teacher for non-technical subjects? Is it my mom or my dad? Is it a Mac 
user? Is it a Windows user?


> understands, even though it might not be 100% accurate or complete.
> Akonadi stores data, so it's a storage, that's a word people
> understand, service as well, layer/API not. And adding to that
> description the trademark name in order to have a unique keyword
> that is connected to the simplified description, in case uniqueness,
> e.g. for google searches or bug reports is needed.

I think we have to differentiate between two different scenarios:

a) User visible texts that occur in the normal user interface - Those 
should not spell out Akonadi. What those texts should say instead 
depends. The more I think about it, the more I think that "personal 
information service" probably isn't that bad. On could throw in 
"management" and/or "storage" between "information" and "service", but I 
don't think it would make the term clearer/easier to understand.

b) Error messages - IMHO those should (additionally) spell out Akonadi 
because, as you write above, it will make searching and asking for help 
much easier.


Regards,
Ingo

["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]