Re: KDE PIM marketing

Bernhard Reiter <[email protected]>
Newsgroups gmane.comp.kde.events
Message-ID <201203061614.55733.bernhard__7365.16911206326$1331046917$gmane$org@intevation.de>
Am Montag 05 März 2012 17:29:59 schrieb Jos Poortvliet:
> > I think that it would be a mistake to say that 4.7 was our FIRST
> > release. It feels a little like rewriting history. Why don't we just
> > say what happened? A decision was made by smart, caring people to move
> > from KMail to KMail2, because ____________. 

My personal aim is to avoid the second term and only talk about
the old KMail and old Kontact, and then about the new Kontact,
which is only a think layer on the KDE PIM backend. Kontact Mail also
is one. Aliases can be provided for users that were accustomed to the old 
names, but this product does technically not exist anymore, it got
refactored to be Kontact Mail. And new users should only see "Kontact Mail",
so the old name may dimish a bit over time.

> > It was ambitious and hard, 
> > but it eventually would have been required. We tried to keep
> > everything running okay, but that didn't work for some people. In
> > retrospect, there was a lot of learning. We apologize.
>
> It feels like rewriting history, but it IS the truth. That is the problem
> here - the first release of the KDE PIM stack which was properly Akonadi
> based was 4.7.0 -

http://en.wikipedia.org/wiki/Kontact has this sentence:
   The first stable version of KDE PIM using Akonadi has been released 
together with KDE S.C. 4.6.4 in June 2011 [*].
  [*] http://kde.org/announcements/announce-4.6.4.php

Until then, developers knew what to do next to get this large change done.
So not until 4.8.0 there was really room for developers to look at issues 
from the user's perspective. 

I believe this the real and most important story: There is now time
to fix simple problems from the user perspective - for the first
time after the big architectual change. And this is a unique point in time.
   
> and admittedly it had some issues, but (almost) nothing 
> that didn't get fixed in the subsequent 6 months. In 4.8 it's quite stable
> for the majority of users, something the KDE PIM team notices as they see
> an influx of new users in their pim user mailing list who are quite happy
> with it all.

> The stuff delivered between 4.0 and 4.4 (with 4.5 and 4.6 being based on
> 4.4) was a rather horribly hybrid which always broke *something* in each
> release. It was a kludge needed to bridge the gap (which turned out to be
> far longer than the team had expected) but NOT what was meant to be the
> 'new KDE PIM'. I really think we lost the majority of our users due to
> that. Yes, 4.7.0 was not perfect, but as a first release, and with most
> issues fixed in the bugfix releases after that, it was not that horrible.
> You have to release at some point...


-- 
Managing Director + Owner: www.Intevation.net <- A Free Software Company
Kolabsys.com: Board Member          FSFE.org: Founding GA Member
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.
signature.asc (application/pgp-signature, 490 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAABAgAGBQJPVinqAAoJEDxD9Mjv9dQqBKYH/AtMkfFkO3aOcezBLeNbaVrW
tdkpL+Smvqu4uJOYaVbYwVSIXPmORjIj0MzWIMKgWbDRbH68GmCCPhokUQXfyEzn
zzyyP7PuOUxmsRmQ/ReBYoIC0AUkrHuuBg3ruYs1A0yrfkew2j8IUIGskYQd01nO
aO7OPntD0i5SHEv117RFsm1FhlYnSfecWlQbHJ+/qANI+mlibHorbY7SmaWAQd0B
RMoW+TtQu1sX9Su5S6h615Jkwl0PN6X+Nl3uCwyluPfrrFoNeuBDxmXTCnLMyxgO
l1rn1HikvOmDM0CgAuqRc7AJNZlIU55d0FxUegsdJ96n71YCXasDJWPYvoOOs/A=
=w7Zh
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.