What to do with potential workflow-changing / breaking changes?

Luca Beltrame lbeltrame at kde.org
Mon Feb 20 06:53:38 UTC 2017


in recent days we have seen a few commits that change how applications behave, 
such as copy-paste disabled in lock screen[1] and an attempt to block GUI 
applications running as root[2] (also detailed in [3]).  

These will (and have already, in fact) raised quite a bit of controversy. Some 
people in openSUSE proposed a local revert of [1], but in the interest of a 
good relationship between KDE and distributions I suggested to open a 
discussion here to prevent a) bad surprises upstream; and b) ensure a proper 
discussion of the differing waypoints.

To the developers: for the future would it be possible to communicate such 
things in advance?

To the other fellow distributors: what you don't like about these changes? Why 
do you think a change back is needed? (Let's not go over the *technical* 
alternatives, for that let's use the development lists; this is mainly to 
discuss how to handle such changes)

P.S: As I have seen in Martin's blog certain heated individuals have already 
badly commented, I would suggest them, should they want to reply, to do it in 
*a civil manner*. 

[1] https://commits.kde.org/kscreenlocker/

[2] https://commits.kde.org/kate/9adcebd3c2e476c8a32e9b455cc99f46b0e12a7e

[3] https://blog.martin-graesslin.com/blog/2017/02/editing-files-as-root/

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/distributions/attachments/20170220/2ece1a33/attachment.sig>

More information about the Distributions mailing list