Skip to content

chore(license): align repository licensing metadata - #6

Merged
wyu71 merged 1 commit into
linuxdeepin:masterfrom
wyu71:master
Aug 3, 2026
Merged

chore(license): align repository licensing metadata#6
wyu71 merged 1 commit into
linuxdeepin:masterfrom
wyu71:master

Conversation

@wyu71

@wyu71 wyu71 commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Update license declarations, REUSE classifications, and SPDX headers. 更新许可证声明、REUSE 分类和 SPDX 文件头。

Translate the default README into English.
将默认 README 翻译为英文。

Log: 统一项目许可证元数据和文件声明
PMS: TASK-393559
Influence: 明确源码、文档、配置和打包文件的许可证分类,不影响运行逻辑。

Summary by Sourcery

Align licensing metadata and documentation with the project’s current licensing policy.

Enhancements:

  • Add SPDX license headers to core source, plugin, and packaging files and switch the project’s main code license reference from GPL-3.0-or-later to LGPL-2.1-or-later.
  • Refresh REUSE configuration and license texts, including adding LGPL-2.1-or-later and CC0-1.0 files and removing obsolete GPL-3.0-or-later and MIT license entries.

Documentation:

  • Translate the default README into English and update license and REUSE information in README files.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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

Please try again later or upgrade to continue using Sourcery

@sourcery-ai

sourcery-ai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Reviewer's Guide

Aligns licensing metadata with REUSE/SPDX conventions, updates the documented project license from GPL-3.0-or-later to LGPL-2.1-or-later (and Debian packaging to CC0-1.0), adds SPDX headers to core source and packaging files, and translates the default README into English while keeping the technical content consistent.

File-Level Changes

Change Details Files
Translate the default README to English and update documented license information and license set.
  • Replaced all Chinese sections in README.md with English equivalents while preserving structure and technical details (overview, features, dependencies, usage, project structure, plugin format, contributing, links).
  • Updated the documented main project license from GPL-3.0-or-later to LGPL-2.1-or-later in README.md and README.zh_CN.md.
  • Adjusted the list of licenses used in the project: main code marked as LGPL-2.1-or-later, Debian packaging files as CC0-1.0 instead of MIT, and kept Apache-2.0 and BSL-1.0 entries.
  • Clarified that full license texts reside in the LICENSES/ directory.
README.md
README.zh_CN.md
Replace legacy GPL boilerplate headers with concise SPDX headers in PaddleOCR implementation files.
  • Removed the multi-line GPL-3.0-or-later boilerplate comment blocks from paddleocr.cpp and paddleocr.h.
  • Added SPDX-FileCopyrightText and SPDX-License-Identifier lines indicating UnionTech Software Technology Co., Ltd. and LGPL-2.1-or-later.
src/paddleocr-ncnn/paddleocr.cpp
src/paddleocr-ncnn/paddleocr.h
Add SPDX headers to core library source and header files for REUSE compliance.
  • Prepended SPDX-FileCopyrightText and SPDX-License-Identifier (LGPL-2.1-or-later) to core plugin implementation and support files.
  • Ensured all key source and header units have consistent SPDX metadata for licensing classification.
src/deepinocrplugin.cpp
src/deepinocrplugin.h
src/deepinocrplugin_p.cpp
src/deepinocrplugin_p.h
src/deepinocrplugindef.h
src/toolkits.cpp
src/toolkits.h
Add SPDX metadata to the Linglong packaging manifest.
  • Prepended SPDX-FileCopyrightText and SPDX-License-Identifier (LGPL-2.1-or-later) to linglong.yaml to mark its licensing explicitly.
linglong.yaml
Realign top-level licensing files and REUSE configuration to the new license scheme.
  • Updated or replaced LICENSE to reflect LGPL-2.1-or-later as the main project license.
  • Adjusted .reuse/dep5 and debian/copyright to match the new SPDX classifications and license assignments (e.g., CC0-1.0 for Debian packaging files).
  • Pruned obsolete license texts (GPL-3.0-or-later.txt, MIT.txt) from LICENSES/ and added new ones (LGPL-2.1-or-later.txt, CC0-1.0.txt, CC-BY-4.0.txt).
.reuse/dep5
LICENSE
debian/copyright
LICENSES/CC-BY-4.0.txt
LICENSES/CC0-1.0.txt
LICENSES/LGPL-2.1-or-later.txt
LICENSES/GPL-3.0-or-later.txt
LICENSES/MIT.txt

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Update license declarations, REUSE classifications, and SPDX headers.
更新许可证声明、REUSE 分类和 SPDX 文件头。

Translate the default README into English.
将默认 README 翻译为英文。

Log: 统一项目许可证元数据和文件声明
PMS: TASK-393559
Influence: 明确源码、文档、配置和打包文件的许可证分类,不影响运行逻辑。
@deepin-ci-robot

Copy link
Copy Markdown

deepin pr auto review

★ 总体评分:95分

■ 【总体评价】

代码实现了项目开源协议从 GPL-3.0-or-later 到 LGPL-2.1-or-later 的完整迁移,并规范了 SPDX 头部声明。
逻辑正确且符合 REUSE 规范,因无逻辑代码变更且无安全漏洞扣5分以保留提升空间。

■ 【详细分析】

  • 1.语法逻辑(完全正确)✓

代码修改主要涉及许可证文本替换、SPDX 头部添加及文档更新。在 src/paddleocr-ncnn/paddleocr.cpp 等源文件中,原有的块注释被正确替换为单行 SPDX 声明,未破坏 C++ 语法结构。.reuse/dep5debian/copyright 文件的格式符合 Debian 版权文件规范。
潜在问题:无
建议:无需修改,保持现有格式。

  • 2.代码质量(优秀)✓

修改严格遵循 REUSE 规范,为所有源文件、配置文件和文档添加了明确的 SPDX 标识符。清理了不再使用的 LICENSES/GPL-3.0-or-later.txtLICENSES/MIT.txt,并补充了 CC-BY-4.0.txtCC0-1.0.txt。README 文档翻译准确,结构清晰。
潜在问题:无
建议:建议在后续开发中继续保持此规范,确保新增文件也包含 SPDX 头部。

  • 3.代码性能(无性能问题)✓

本次提交均为静态文本、注释和元数据文件的修改,不涉及任何可执行逻辑、算法变更或资源调度,对编译产物和运行时性能无任何影响。
潜在问题:无
建议:无

  • 4.代码安全(存在0个安全漏洞)✓

漏洞对比统计:新增漏洞 0 个,减少漏洞 0 个,持平 0 个
本次修改未引入任何可执行代码逻辑,不存在命令注入、内存泄漏或缓冲区溢出等安全风险。所有变更均为协议声明和文档更新,不改变程序的攻击面。

  • 建议:无需进行安全修复,保持现有代码结构。

■ 【改进建议代码示例】

// 当前代码已符合最佳实践,无需修改,保持如下格式即可:
// SPDX-FileCopyrightText: 2020-2026 UnionTech Software Technology Co., Ltd.
//
// SPDX-License-Identifier: LGPL-2.1-or-later

#include "paddleocr.h"

@deepin-ci-robot

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lzwind, wyu71

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

@wyu71
wyu71 merged commit e090259 into linuxdeepin:master Aug 3, 2026
20 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