From kde-pim Tue May 07 08:13:39 2013 From: "Georg C. F. Greve" Date: Tue, 07 May 2013 08:13:39 +0000 To: kde-pim Subject: Re: [Kde-pim] Marketing blocker collection, DEADLINE: 2013-03-10 Message-Id: <22441239.IFO5AGv9a4 () katana ! lair> X-MARC-Message: https://marc.info/?l=kde-pim&m=136791444006823 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============8878678907774088738==" --===============8878678907774088738== Content-Type: multipart/signed; boundary="nextPart2494518.hYOH9fv4n2"; micalg="pgp-sha1"; protocol="application/pgp-signature" --nextPart2494518.hYOH9fv4n2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Hi Martin, On Monday 06 May 2013 21.42:17 Martin Steigerwald wrote: > > True to tradition, we spent a good amount of time talking about whe= n it > > would be time to go out and tell the world to give KDE PIM a try. A= t the > > sprint there was unanimous agreement it is time to dispend with thi= s > > tradition. >=20 > Whats the current state with this marketing blocker collection? Someone would have to find time to go through the list and see what has= been=20 resolved. I know that at least the major issue I reported remains, and = suspect=20 it is true for some others. Unfortunately I lack the time to go through the list right now. Volunteers would be rather welcome. > I wouldn=B4t use it as a mail solution in a company right now for exa= mple. Actually I think it's the other way around. I would perhaps *only* use it in a company, or follow the same practice= s. This is how my wife is using it for years now, in production, with only= minor=20 issues. Let me explain: > And I think main show stopper are still correctness, consistency issu= es, > unhelpful error messages / notifications during daily use - like mail= cannot > be moved or deleted with a maildir mail file name and no reason as to= *why* > or way to fix it up. In my experience, maildir is hardly a corporate feature, it's all in IM= AP for=20 the same reasons filtering is done on the server (see below). Likewise = POP3 is=20 largely irrelevant in a properly set up and maintained corporate instal= lation. > 1) No automatic filtering at all. > 2) No CRM114 spam filter rules, also not manually. In a company, that would largely be done server side as you would *not*= want=20 to rely on desktop-side filtering due to the fact that you're also push= ing mail=20 to mobile and want filtering to have taken place before that. Sieve editing is definitely not good in KDE PIM right now, but then oft= en=20 companies would deploy server side Sieve editors - Kolab for instance h= as a=20 pretty good one. We're looking into also providing this kind of editing for KDE PIM, but= for=20 the moment there is a workaround which is corporate friendly, as many=20= companies lock down the Sieve port for good reasons: They do not want u= sers to=20 use anything but the officially supported path to edit Sieve scripts, a= s there=20 are too many ways to generate support requests otherwise. Likewise spam filtering is done on the server through Sieve. > I am also asking due to "kde-pim hopeless?" thread in kdepim-users. I= do not > think it is. But I see that it has only few developers who work reall= y > hard. I think about how users can help, maybe some bug triaging. I tr= y to > isolate repeatable testcases for the gravest bugs I found as time per= mits. > Testing and reproducing takes quite some time too. I realize that, and understand, even share, some of the frustration. The problem is that "every feature gets in" and "every feature needs to= be=20 enterprise ready" are impossible goals to pursue simultaneously.=20 And the desire to use KDE PIM professionally in corporate environments = puts=20 the priority on those features that are used in the corporate environme= nt.=20 Others will necessarily mature slower. You can only speed up the entire cycle, which happens through adoption,= which=20 is what we're working on. What the KDE PIM community can do to that end= is to=20 help get rid of the worst showstoppers and experience blockers, which i= s=20 exactly what people are working on. But then KDE PIM is the most powerful of all the clients. By some margi= n. That means there is just a lot of work. But then: KDE PIM has matured noticeably. So there is progress. It's ju= st that=20 all of us would like it to be faster, a feeling we share with most user= s.=20 Best regards, Georg --=20 Georg C. F. Greve Chief Executive Officer Kolab Systems AG=09=09=09=09Make it your Kolab @ http://mykolab.com Z=FCrich, Switzerland=09=09=09=09or try it out at http://kolabsys.com/t= ry e: greve@kolabsys.com t: +41 78 904 43 33 w: http://kolabsys.com pgp: 86574ACA Georg C. F. Greve --nextPart2494518.hYOH9fv4n2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQCVAwUAUYi3syk9sUy32wQcAQI8jgP/SKbX3yrhxx8hwdEIMnhnwTzz1M0GOzJo HoX/vcvIEWxLSbZCVOw6pBwstqvPHfxiUNukNT0u7M7fCHQlbgDIKDQv34gT+4lV q6m0U2FuAMEKO4eYTVnmzHEfVdAv2cqmTAbho1Fn655yGLZmhfZ9IHvICKeJU9hq tlT+txlhonU= =+6NR -----END PGP SIGNATURE----- --nextPart2494518.hYOH9fv4n2-- --===============8878678907774088738== 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/ --===============8878678907774088738==--