[BUG] no dedicated licence in standards repository for (some) code (tests)

[artificial-intelligence]

Hi,

depending on your point of view you can view this as a bug report or a feature request 🙂

I also took the liberty to add this to tomorrow's SIGs Agenda:

https://input.scs.community/2024-scs-sig-standardization?both#no-dedicated-licence-in-standards-repository-for-some-code-tests

What is the problem?

There does not seem to be a dedicated source code licence for code inside
the standards repository.

I think this is a problem because the general licence for this repo is a CC licence and these are generally not a good fit for code (I am not a lawyer, so please correct me if this is a non-issue!)

• I would therefore suggest to either add a second licence text to the whole repository or add individual SPDX Licence Identifiers to each test file (I personally prefer the latter, while we could still add the former as well).
• Further investigation revealed that some scripts do indeed have an SPDX Header, but far from all: https://github.com/search?q=repo%3ASovereignCloudStack%2Fstandards%20SPDX-License-Identifier&type=code
• Proposal: add a linter that checks the presence of an SPDX Header in all code, a tool that can check for this is e.g. https://github.com/github/go-spdx

[mbuechse]

This issue shall be talked about again on 2024-05-16 in SIG Std/Cert

[fkr]

Proposed PR #1012.

Checked the minutes for the mentioned call on 2024-05-16. There it was delayed to 2024-05-30 (https://github.com/SovereignCloudStack/minutes/blob/4b204d8b4d740566d57855474d9c04a58e64f8aa/sig-standardization/20240516.md?plain=1#L24) - On 2024-05-30 was no meeting - well, at least no recorded minutes in github. And the meeting afterwards (2024-06-13 has no mentions of it anymore.