[Kde-pim] Marketing blocker collection, DEADLINE: 2013-03-10
Volker Krause
vkrause at kde.org
Sun Mar 3 15:22:07 GMT 2013
On Sunday 03 March 2013 13:04:15 Wolfgang Rohdewald wrote:
> Am Sonntag, 3. März 2013, 12:43:44 schrieb Georg C. F. Greve:
> > AND NO FEATURES WILL BE ADDED UNTIL THE LIST IS DONE!
>
> my congratulations to this decision! It was long overdue.
>
> (I hope with DONE you mean that all blockers are dealt with,
> and not that the list is defined)
>
> May I propose bug 282891 ( searching) - it probably needs to
> be broken up into smaller bugs with different priorities. When
> maildir is stable (by my own perception), I might try to
> some of this.
>
> And as long as removing the akonadi db is recommended to
> fix problems,
Deleting the Akonadi database is *not* *recommended*, nor has it ever been
recommended officially.
It's a wrong conclusion from the statement that Akonadi is a cache for data
stored in its respective backends. Breaking the cache means data in the
backends is safe, not that there will be no side-effects of an inconsistent
local state if you keep going with that. Completely removing all local state
is also safe (ie. including filter and application configurations).
Yes, I am aware it's suggested regularly "on the internet", just as breaking
your configuration to "disable Akonadi" (StartServer=false does not mean
Akonadi is disabled, it means Akonadi tries to connect to a remote database
server).
There is one valid way to run into this, when using the (hopefully still
hidden?) server KCM to change the backend. We probably should remove that
entirely, changing the backend after you started using Akonadi gets you into
the same mess.
> please think about how to recover filters after
> that. Maybe save not only the id of the folder but also its name
> (of course renaming the folder would have to update filter
> settings). Now if a folder id is not found, try to find a folder
> with the same name and use its id. Warning on stdout/stderr
> would be OK, but GUI feedback should be at most one
> message. Do that when the mailfilter agent starts.
This makes sense for syncing filter configurations between different
instances, ie. also useful for users that don't have a damaged local cache.
> With kmail1 I had about 100 filters - since kmail2 I do
> not filter anymore at all. And I unsubscribed from many
> mailing lists.
>
> As a third point - there are too many error messages or
> warnings the user simply cannot understand, they only
> make him feel unsafe. I think this got better with 4.10 and
> the fixes since then, but still ...
I have seen "akonaditray" enabled by default on some distros, which exposes a
whole lot of internal warnings, we probably should get rid of that entirely as
well.
regards,
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20130303/9fec94b7/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
More information about the kde-pim
mailing list