You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 27, 2024. It is now read-only.
Reading the REUSE spec 2.0 carefully shows that when there are more than one licenses in a repository/package, there are three options on how to store license text in a file (in §1):
Copy the license text from a LICENSE file or from SPDX license list) and (re)name it accordingly to its SPDX license shorthand (or LicenseRef-*, if there is none or the text is modified).
If you cannot or want not to rename the license file (e.g. because you want to keep it as LICENSE or COPYING), add the Valid-License-Identifier tag followed by the License-Text tag.
If you cannot or want not to even edit the (existing) license file, create a new file with a .license extension (e.g. COPYING.license or perhaps even Cool Custom License.pdf.license) and insert the Valid-License-Identifier and License-Text tags there.
Solution 3 has a problem already that it clashes with how §2 says you can add copyright and license info to files (e.g. icon.png) you cannot insert comment headers into by creating a separate file with .license extension appended to the filename (e.g. icon.png.license). If nothing else, this double-use of *.license files could confuse license scanning tools.
Solution 3 is also missing from the “Keep in mind” summary at the end of the §1.
Unless there are good reasons for Solution 3 to stay, I would suggest removing it. If there are reasons for it to stay, we should work on refining it and explaining more prominently that it introduces an exception to the general use of *.license.
In any case, I think adding more structure to this part of §1 would benefit clarity that there are three options that may be used.
The text was updated successfully, but these errors were encountered:
Reading the REUSE spec 2.0 carefully shows that when there are more than one licenses in a repository/package, there are three options on how to store license text in a file (in §1):
LICENSE
file or from SPDX license list) and (re)name it accordingly to its SPDX license shorthand (or LicenseRef-*, if there is none or the text is modified).LICENSE
orCOPYING
), add theValid-License-Identifier
tag followed by theLicense-Text
tag..license
extension (e.g.COPYING.license
or perhaps evenCool Custom License.pdf.license
) and insert theValid-License-Identifier
andLicense-Text
tags there.Solution 3 has a problem already that it clashes with how §2 says you can add copyright and license info to files (e.g.
icon.png
) you cannot insert comment headers into by creating a separate file with.license
extension appended to the filename (e.g.icon.png.license
). If nothing else, this double-use of*.license
files could confuse license scanning tools.Solution 3 is also missing from the “Keep in mind” summary at the end of the §1.
Unless there are good reasons for Solution 3 to stay, I would suggest removing it. If there are reasons for it to stay, we should work on refining it and explaining more prominently that it introduces an exception to the general use of
*.license
.In any case, I think adding more structure to this part of §1 would benefit clarity that there are three options that may be used.
The text was updated successfully, but these errors were encountered: