why kdelibs?

[Aaron J. Seigo]

On Monday, November 1, 2010, Diederik van der Boor wrote:
> I can't stress enough it needs a good plan to limit impact on apps.

this would be absolutely critical indeed.

something that is completely opaque to me in this discussion so far is whether 
the idea is to:

a) grind kdelibs into a fine dust of classes, rename some from KFoo to QFoo 
(and all the Qtification that implies) and reorganize the remainder (which 
should be a minimal set) into a new set of K* libs

or

b) define a new set of granularities for libraries in kdelibs (non-ui, 
desktop, framework, etc.) and split up our existing classes along those new 
lines, keeping names largely in place

or 

c) do a bit of (a) and (b), and if so what the guidelines for deciding when to 
do (a) and when to do (b) are

probably because it isn't a concrete plan yet, but rather a general proposal. 
these are the kinds of details that are needed before we can move on.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20101102/474db38b/attachment.sig>