Postings by Roman Gilg

KScreen/libkscreen commit message policies


I just pushed commit message policies to KScreen [1] and libkscreen
[2] (linked below from GitHub so they can be read with Markdown

I intend to revert in the future all manual commits to KScreen and
libkscreen deliberately ignoring the policies.

Taking over maintainership of libkscreen / KScreen


since I am the only person responsible for bigger changes to
libkscreen and KScreen over months now I propose to take over
maintainership of libkscreen / KScreen. Actually I changed the
maintainership information already in code for KScreen with
<a href="" title=""></a>,
but I remembered that there are other areas needed for official
transfer (for example default assigne and repo metadata),
so that's what this email is for.

If there are questions please let me know.


Unified git commit message guideline

For KWin we think about a message guideline because our current best
practice that we got used to over time is just sometimes putting tags
in square brackets at the beginning of the subject line for indicating
the location of the change in code but somebody noted having a square
bracket in the beginning leads to problems with certain git log parser

Asking around on IRC it seems we should expand the scope. Apparently
also other KDE projects could profit from a policy and some tooling
around it.

Review Request 125097: Icons for hiding/unhiding files

Review request for kde-workspace and Emmanuel Pescosta.

Repository: breeze

Icon is based on 'edit-copy.svg'.