ervin at kde.org
Tue Aug 26 09:50:50 UTC 2014
On Tuesday 26 August 2014 11:20:25 laurent Montel wrote:
> I will split kdepimlibs as it
> akonadi (need to find another name because it's still used)
To me it sounds like some of those things could be regrouped now. What about
also bringing the akonadi server on board? Having a bigger akonadi framework
containing server (right now in kdesupport), some access libs and a few
default plugins would make sense (it looks like a KIO like framework).
This one looks like a dumping ground of random things. Maybe some of it should
move in other frameworks?
Definitely not a framework. Are all the ioslaves in there still used? I think
at least some of them can be let go. The others could go in kio-extras I
Probably should go in kdepim or kontact itself. Similarly the content of the
kdelibs/interfaces folder moved out of KF5.
Maybe deserves a better name? kidentitymanagement?
I suspect it could get a better name, but couldn't decide yet. :-)
Also I wonder if some of it could/should go in ktexteditor? But I don't know
the respective feature sets enough to be sure.
Looks like another dumping ground of random classes. Each class should likely
find a new home.
Couldn't that be merged with gpgme++? This one already builds several variants
depending what it finds on the platform, why not treat the Qt integration in
the same way?
> is it ok for you ?
I tried to point out things which would be harder to address after the split.
So I think we should have discussions and decisions about the points above
before being able to proceed.
Kévin Ottens, http://ervin.ipsquad.net
KDAB - proud supporter of KDE, http://www.kdab.com
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part.
More information about the Kde-frameworks-devel