--===============0187457148862001847== Content-Type: multipart/signed; boundary="nextPart2548281.bcsDlQxP94"; micalg="pgp-sha1"; protocol="application/pgp-signature" Content-Transfer-Encoding: quoted-printable --nextPart2548281.bcsDlQxP94 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Dear all, True to tradition, we spent a good amount of time talking about when it= would=20 be time to go out and tell the world to give KDE PIM a try. At the spri= nt=20 there was unanimous agreement it is time to dispend with this tradition= . So we agreed that it is time to start countering the impression of "noo= ne is=20 using Kontact productively/successfully/happily" by all of us sharing n= ot only=20 the pain, but also the pleasure we have when KDE PIM does things well. These do not have to be lengthy blog posts or glossy magazines. Short dents/tweets/G+/Facebook postings entirely suffice as long as we = do them. We also agreed that we want to start banging the bigger marketing drum = within=20 the KDE community and without. For this purpose, we want to identify th= e major=20 issues to new user experience. To clarify: This is not about issues or our pet peeves, it is about thi= ngs=20 that are BLOCKERS for end user perception. So we're talking about thing= s that=20 would make someone immediately stop using KDE PIM and never come back.=20= Submission to that list is open until *2013-03-10* to kde-pim@kde.org. Anything sent elsewhere or after that date will *not* make it to the li= st. The list will then be triaged for things that are =09BLOCKER:=09 =09 Data loss, fundamentally broken =09MAJOR:=09=09 Extremely annoying, but not causing irreparable damage= =09NORMAL:=09=09 Must be fixed as soon as possible =09MINOR:=09=09 Nuisance, but not really broken =09IMPROVEMENT: A better way of doing this Then for everything that is classified as MAJOR or BLOCKER, we will the= n make a=20 call between =09(a) FIXING it=20 =09(b) DISABLING it by default until fixed =09(c) WORKING AROUND it for now, until it can be fixed with *KDE 4.10.2* as our target.=20 For example: Loading very large IMAP accounts on older hardware can tak= e a=20 substantial amount of time where the machine uses large amounts of CPU = as it=20 is downloading and caching the data. During that period the machine is = slow,=20 and Kontact is essentially not responsive to user input, nor does it sh= ow data=20 sensibly. FIXING it might mean to have resource usage limited and ensure that use= r=20 interactive requests, e.g. looking at a folder, take priority over the=20= background synchronization so the feedback & application impression is=20= immediate even though it may be incomplete as long as the background pr= ocess=20 is till ongoing. DISABLING it might mean disabling offline IMAP by default. WORKING AROUND it might mean to not display the main UI, but show a win= dow=20 saying "Please wait while we synchronize & index your data. This proces= s may=20 take a while. <12132438> mails synchronized." (with the number spinning= up=20 quickly) Once we have the list of issues that are deemed MAJOR or BLOCKER for us= er=20 impression, and their individual resolution, these become our HIGH PRIO= RITY=20 TARGETS for all of KDE PIM along with other MAJOR (or above) issues. Most important (insert VERY stern face of Kevin Ottens here):=20 =09THIS LIST WILL *NOT* BE ADDED TO! =09AND *NO FEATURES WILL BE ADDED* UNTIL THE LIST IS DONE! When the list is done, and the 4.10.2 release is out, we will work with= the=20 larger KDE community to bang the marketing drum, as well as encourage p= eople=20 to switch (back) to KDE PIM. Thus unanimously adopted at the KDE PIM sprint in Berlin that was Osnab= r=FCck. So, everyone, please think which are the parts that utterly destroy use= r=20 experience to the point of making KDE PIM marketing impossible and then= send=20 them.=20 But please ensure to do so by SUNDAY NEXT WEEK, 10 March 2013. Because submissions afterwards will NOT be accepted. Best regards, Georg --=20 Georg C. F. Greve Chief Executive Officer Kolab Systems AG=09=09=09=09Wondering whether Kolab is for you? Z=FCrich, Switzerland=09=09=09=09Find out at http://kolabsys.com/try e: greve@kolabsys.com t: +41 78 904 43 33 w: http://kolabsys.com pgp: 86574ACA Georg C. F. Greve --nextPart2548281.bcsDlQxP94 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQCVAwUAUTM3cCk9sUy32wQcAQLrPgQAr1NYo2B18OzWwuH4a87c8tbOhYB+P9le v9tZJhIMYhgBhKPbbosmtc0CLxe3tI9GHeNDbJxoQML729rUVBAtoVK52Q9TC6qp tlDjn9hS+gi5zGrdFAAe2uHFzC/oHRtKhczEFP6gw2Y9OUZPuxzKcMpj8lehr4lr dWGk4jTt8cQ= =9hW/ -----END PGP SIGNATURE----- --nextPart2548281.bcsDlQxP94-- --===============0187457148862001847== 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/ --===============0187457148862001847==--