RFC: Dropping (for real) KTP from Applications 17.12

[Luca Beltrame]

NOTE: this mail comes from a downstream (distributor / integrator) point of 
view. Feel free to correct possible errors. Also please try to keep both lists 
in CC.

Hello,

a recent message[1] to the release-team mailing list suggested that KDE 
Telepathy is de facto dead, due to lack of maintenance with the exception of 
infrequent contributions. Now, the problem seems also to affect the upstream 
Telepathy project, which is mostly dormant. Recently, a component used by KTP 
(the Qt bindings for Telepathy) broke with CMake 3.9 (and a fix or a release is 
not in sight; there has been no significant activity since 2015). At this 
point, with many parts of the stack that are likely bitrotting, and even a 
mostly dead upstream, it is the time to wonder whether KTP should be still 
part of Applications. It was suggested to keep it if it didn't break, but as I 
mentioned, some dependencies *are* already broken.

Therefore, I would suggest for it to be dropped from the next Applications 
release (17.12). For what it's worth, it's being already dropped from openSUSE 
Tumbleweed (and the future stable versions as well), unless, of course, the 
impasse can be solved, but IMO it would just move the line to the next 
breakage (which is going to happen, sooner or later),

[1] https://mail.kde.org/pipermail/release-team/2017-August/010494.html

-- 
Luca Beltrame - KDE Forums team
GPG key ID: A29D259B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20170823/3322249e/attachment.sig>