<table><tr><td style="">cordlandwehr added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D27364">View Revision</a></tr></table><br /><div><div><p><a href="https://phabricator.kde.org/p/mart/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@mart</a> the main argument chain here is: we need machine readable license identifiers to enable tooling -> SPDX markers are the way to go -> having both license statements and SPDX markers in the same file will ultimately lead to ambiguous licenses, since people will forget updating always both -> thus only use the SPDX markers<br />
for making those markers easier to understand, there probably will be (in the near future) a generic licensing readme file (possibly as a replacement for the COPYING & COPYING.LIB files) that explains to the license users the meaning of the SPDX markers and where they can find the full license texts inside the repository; though, such a explanatory file is not yet in draft and thus have to be added in a later commit.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R169 Kirigami</div></div></div><br /><div><strong>BRANCH</strong><div><div>spdx</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D27364">https://phabricator.kde.org/D27364</a></div></div><br /><div><strong>To: </strong>cordlandwehr, mart, jriddell<br /><strong>Cc: </strong>plasma-devel, fbampaloukas, GB_2, domson, dkardarakos, ngraham, apol, ahiemstra, davidedmundson, mart, hein<br /></div>