Skip to content

docs: update license references in README files#165

Merged
mhduiy merged 1 commit intolinuxdeepin:masterfrom
mhduiy:license
Oct 16, 2025
Merged

docs: update license references in README files#165
mhduiy merged 1 commit intolinuxdeepin:masterfrom
mhduiy:license

Conversation

@mhduiy
Copy link
Copy Markdown
Contributor

@mhduiy mhduiy commented Oct 15, 2025

Updated license references in both English and Chinese README files to use consistent GPL-3.0-or-later license identifier. Changed the license reference in README.md from GPLv3 to GPL-3.0-or-later and corrected the license in README.zh_CN.md from LGPL-3.0-or-later to GPL-3.0-or- later to ensure consistency across documentation and accurate license representation.

Influence:

  1. Verify license references are consistent in both language versions
  2. Check that LICENSE file content matches the referenced license
  3. Confirm build and distribution compliance with GPL-3.0-or-later requirements

docs: 更新 README 文件中的许可证引用

更新了英文和中文 README 文件中的许可证引用,使用一致的 GPL-3.0-or-later
许可证标识符。将 README.md 中的许可证引用从 GPLv3 更改为 GPL-3.0-or-
later,并将 README.zh_CN.md 中的许可证从 LGPL-3.0-or-later 更正为 GPL- 3.0-or-later,以确保文档一致性和准确的许可证表示。

Influence:

  1. 验证两个语言版本中的许可证引用是否一致
  2. 检查 LICENSE 文件内容是否与引用的许可证匹配
  3. 确认构建和分发符合 GPL-3.0-or-later 许可证要求

Updated license references in both English and Chinese README files to
use consistent GPL-3.0-or-later license identifier. Changed the license
reference in README.md from GPLv3 to GPL-3.0-or-later and corrected
the license in README.zh_CN.md from LGPL-3.0-or-later to GPL-3.0-or-
later to ensure consistency across documentation and accurate license
representation.

Influence:
1. Verify license references are consistent in both language versions
2. Check that LICENSE file content matches the referenced license
3. Confirm build and distribution compliance with GPL-3.0-or-later
requirements

docs: 更新 README 文件中的许可证引用

更新了英文和中文 README 文件中的许可证引用,使用一致的 GPL-3.0-or-later
许可证标识符。将 README.md 中的许可证引用从 GPLv3 更改为 GPL-3.0-or-
later,并将 README.zh_CN.md 中的许可证从 LGPL-3.0-or-later 更正为 GPL-
3.0-or-later,以确保文档一致性和准确的许可证表示。

Influence:
1. 验证两个语言版本中的许可证引用是否一致
2. 检查 LICENSE 文件内容是否与引用的许可证匹配
3. 确认构建和分发符合 GPL-3.0-or-later 许可证要求
Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @mhduiy, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@deepin-ci-robot
Copy link
Copy Markdown

deepin pr auto review

我来审查这个 Git diff 变更:

变更概述

这个变更主要涉及两个文件(README.md 和 README.zh_CN.md)中的许可证信息更新:

  1. 英文版从 "GPLv3" 改为 "GPL-3.0-or-later"
  2. 中文版从 "LGPL-3.0-or-later" 改为 "GPL-3.0-or-later"

语法逻辑检查

  • 语法没有问题,Markdown 格式正确
  • 链接格式规范,使用了标准的许可证引用方式

代码质量检查

  • 变更内容清晰明了
  • 保持了文档的一致性(两个版本都指向了相同的许可证)

代码性能检查

  • 此变更不影响代码性能,仅涉及文档更新

代码安全检查

  • 不涉及代码安全相关内容

改进建议

  1. 许可证一致性:这个变更将中文版的许可证从 LGPL 更改为 GPL,这是一个重要的法律变更。建议:

    • 确保所有相关源代码文件中的许可证声明也同步更新
    • 检查项目依赖项是否与新许可证兼容
    • 如果这是一个团队项目,建议在变更日志中记录这个重要的许可证变更
  2. 文档完整性

    • 考虑在变更说明中添加一段关于为什么进行这个许可证变更的解释
    • 可以添加一个"Changelog"部分来记录这类重要变更
  3. 链接准确性

    • 确保 LICENSE 文件确实包含 GPL-3.0-or-later 的完整文本
    • 可以考虑在文档中添加许可证文本的摘要或关键条款

总的来说,这是一个简单的文档变更,但涉及法律层面的重要变更,需要确保所有相关文档和代码都保持一致,并且团队中的所有成员都了解这个变更。

@deepin-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BLumia, mhduiy

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mhduiy mhduiy merged commit f39786d into linuxdeepin:master Oct 16, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants