D22973: docs: introduce commit message guideline

[Vlad Zagorodniy]

zzag added a comment.


  Scopes are a bit tricky. KWin core contains lots of stuff, so it'll be difficult to figure out what one should use as a scope.
  
  We could put component name for example
  
    fix(core): Prevent dangling pointers in the stacking order
    feat(colorcorrect): Add gamma and brightness options
    fix(core): Calculate correct visible bounds of ShellClient
    fix(core): Keep the outline below visual parent
    core: Rework frame skipping logic
    platfroms-x11: Require XI2
    platforms-wayland: Forward axis_source to platform
    (platforms: or nothing?) Drop fbdev platform
  
  Alternatively, we could put "topic," e.g.
  
    fix(core): Prevent dangling pointers in the stacking order
    fix(nightcolor): Add gamma and brightness options
    fix(wayland): Calculate proper visible bound of xdg_surface
    fix(core): Keep the outline below visual parent
    compositor: Rework frame skipping logic
    (x11: or platforms-x11:) Require XI2
    (wayland: or platforms-wayland:) Forward axis_source to platform
    (platforms: or nothing?) Drop fbdev platform

REPOSITORY
  R108 KWin

REVISION DETAIL
  https://phabricator.kde.org/D22973

To: romangg, #kwin
Cc: zzag, ngraham, kwin, LeGast00n, sbergeron, jraleigh, fbampaloukas, GB_2, mkulinski, ragreen, jackyalcine, Pitel, iodelay, crozbo, bwowk, ZrenBot, alexeymin, himcesjf, lesliezhai, ali-mohamed, hardening, romangg, jensreuterberg, abetts, sebas, apol, mart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kwin/attachments/20190808/ef37f214/attachment-0001.html>