Rename ktp-common-internals (and make it part of kf5/public)?

[Martin Klapetek]

Hey all,

so now with all the porting to frameworks, the question arises again -
should we make ktp-common-internals public and stable API?  And make it a
proper framework? And if so, should it maybe be renamed as the purpose of
the name was to reflect the fact that it's meant only as an internal common
code for other KTp components...so rename it to something more sensible?

KTelepathy comes to mind...

Cheers
-- 
Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-telepathy/attachments/20141029/dd37ea17/attachment.html>