[Kde-pim] Akonadi: single database design mistake?

ianseeks ianseeks at yahoo.co.uk
Wed May 1 12:51:42 BST 2013


On Monday 29 Apr 2013 18:42:55 Andras Mantia wrote:
> ianseeks wrote:
> > My take on it would be that it should have been a configurable option to
> > use Akonadi etc or to keep PIM working as it used to
> 
> That would require maintainers for the old and new pim applications. Take a
> look at the number of active pim developers and think about if this would
> work or not. :)
I appreciate the number of developers problem and i sympathise. 
My guess is that Akonadi built-in is overkill for most of the users, 
especially non-developers and people who don;t have that much data where a few 
aptly named folders would suffice.  If it ran as a separate service that users 
could have a choice of using, I'm sure life would be easier for the PIM 
developers because they could separate the problems and keep concentrating 
only on PIM issues.

> Andras
> _______________________________________________
> 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/
_______________________________________________
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