Conversation
Signed-off-by: CPiccini <47435428+CPiccini@users.noreply.github.com>
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
The PR title indicates a support-section clarity update, but this change adds a GPL-2.0 license file instead. Please align the PR title/description with the actual change set (or include the intended SUPPORT/README edits in this PR).
There was a problem hiding this comment.
The LICENSE file includes added headings/usage guide and Markdown formatting. For GPLv2, the license text should be included verbatim (and many scanners expect the canonical text in LICENSE). Consider moving the SPDX/usage guidance to a separate doc and keeping LICENSE as the unmodified GPL-2.0-only/or-later text.
There was a problem hiding this comment.
The SPDX identifiers listed here include deprecated/ambiguous forms (e.g., GPL-2.0 and GPL-2.0+). Prefer the current SPDX IDs (GPL-2.0-only or GPL-2.0-or-later) and avoid introducing nonstandard tags like Valid-License-Identifier: which tooling may not recognize.
There was a problem hiding this comment.
This sentence says the license must be distributed verbatim and "changing it is not allowed", but the file has already been modified (headings/typography/formatting). This creates a legal/compliance risk; please replace the body with the exact canonical GPL v2 text (byte-for-byte) and avoid smart quotes/en dashes and Markdown styling within the license body.
There was a problem hiding this comment.
Repo docs currently point to LICENSE.md (e.g., README/CONTRIBUTING), but this PR adds LICENSE. To avoid broken references and confusion, either rename/add the file to match (LICENSE.md) or update the documentation to reference the actual license filename.
No description provided.