From: Chen-Yu Yeh <chenyou910331@gmail.com>
To: Alex Shi <alexs@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Weijie Yuan <wy@wyuan.org>, Dongliang Mu <dzm91@hust.edu.cn>,
Yanteng Si <si.yanteng@linux.dev>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Chen-Yu Yeh <chenyou910331@gmail.com>
Subject: [PATCH 14/25] docs/zh_TW: process: sync kernel-enforcement-statement.rst with the English original
Date: Fri, 6 Nov 2026 19:31:29 +0800 [thread overview]
Message-ID: <20261106113142.706783-15-chenyou910331@gmail.com> (raw)
In-Reply-To: <20261106113142.706783-1-chenyou910331@gmail.com>
The translation carries no "update to commit" marker. A comparison
against the current English text shows the content is complete: the
signer list matches all 109 names, including the later additions such as
Arnaldo Carvalho de Melo, Kees Cook and Luis R. Rodriguez. But the file
still begins its label line with the byte order mark that
commit 9e255e2b9afe ("Documentation: drop optional BOMs") removed from
the original, and the prose was converted from zh_CN:
- drop the byte order mark, as in the original
- retranslate sentences whose meaning had drifted: the additional
permissions apply "with respect to any non-defensive assertion of
rights under the license" (rendered as "as any non-defensive
assertion"), and the uncertainty to eliminate is "about our
expectations regarding compliance or enforcement" (rendered as our
own uncertainty about regulatory compliance)
- rewrite the two quoted GPL-3.0 provisions so that the conditions
read in order, without the duplicated "reinstated permanently" in
(b), and use 版權持有人 for "copyright holder" throughout
- localize terminology (內核→核心, 社區→社群, 用戶→使用者, 項目→專案,
分發→散布, 爲→為), and translate "Except where noted below" as
such instead of "except as mentioned below"
- wrap the :Original: line to stay within 80 columns and drop the
blank line at the end of the file
update to commit 9e255e2b9afe ("Documentation: drop optional BOMs")
Signed-off-by: Chen-Yu Yeh <chenyou910331@gmail.com>
---
.../process/kernel-enforcement-statement.rst | 59 ++++++++++---------
1 file changed, 31 insertions(+), 28 deletions(-)
diff --git a/Documentation/translations/zh_TW/process/kernel-enforcement-statement.rst b/Documentation/translations/zh_TW/process/kernel-enforcement-statement.rst
index d54d20529294..9a518ce322c2 100644
--- a/Documentation/translations/zh_TW/process/kernel-enforcement-statement.rst
+++ b/Documentation/translations/zh_TW/process/kernel-enforcement-statement.rst
@@ -1,45 +1,49 @@
.. SPDX-License-Identifier: GPL-2.0
-.. _tw_process_statement_kernel:
+.. _tw_process_statement_kernel:
.. include:: ../disclaimer-zh_TW.rst
-:Original: :ref:`Documentation/process/kernel-enforcement-statement.rst <process_statement_kernel>`
+:Original: :ref:`Documentation/process/kernel-enforcement-statement.rst
+ <process_statement_kernel>`
-Linux 內核執行聲明
+Linux 核心執行聲明
------------------
-作爲Linux內核的開發人員,我們對如何使用我們的軟體以及如何實施軟體許可證有著
-濃厚的興趣。遵守GPL-2.0的互惠共享義務對我們軟體和社區的長期可持續性至關重要。
+作為Linux核心的開發人員,我們對我們的軟體如何被使用,以及我們軟體的許可證
+如何被執行,有著濃厚的興趣。遵守GPL-2.0的互惠共享義務,對我們軟體和社群的
+長期永續發展至關重要。
-雖然有權強制執行對我們社區的貢獻中的單獨版權權益,但我們有共同的利益,即確保
-個人強制執行行動的方式有利於我們的社區,不會對我們軟體生態系統的健康和增長
-產生意外的負面影響。爲了阻止無益的執法行動,我們同意代表我們自己和我們版權
-利益的任何繼承人對Linux內核用戶作出以下符合我們開發社區最大利益的承諾:
+雖然對貢獻給我們社群的內容中各自獨立的版權權益,確實有權強制執行,但我們
+共同關心的是,確保個別的執行行動以有利於我們社群的方式進行,而不會對我們
+軟體生態系統的健康與成長造成意料之外的負面影響。為了遏止無益的執行行動,
+我們同意代表我們自己以及我們版權權益的任何繼受者,向Linux核心的使用者作出
+以下承諾,這符合我們開發社群的最大利益:
- 儘管有GPL-2.0的終止條款,我們同意,採用以下GPL-3.0條款作爲我們許可證下的
- 附加許可,作爲任何對許可證下權利的非防禦性主張,這符合我們開發社區的最佳
- 利益。
+ 儘管有GPL-2.0的終止條款,我們同意,對於依本許可證所提出的任何非防禦性
+ 權利主張,採用以下GPL-3.0條款作為我們許可證下的額外許可,這符合我們開發
+ 社群的最大利益。
- 但是,如果您停止所有違反本許可證的行爲,則您從特定版權持有人處獲得的
- 許可證將被恢復:(a)暫時恢復,除非版權持有人明確並最終終止您的許可證;
- 以及(b)永久恢復, 如果版權持有人未能在你終止違反後60天內以合理方式
- 通知您違反本許可證的行爲,則永久恢復您的許可證。
+ 但是,如果您停止所有違反本許可證的行為,則您從特定版權持有人處
+ 獲得的授權將會恢復:(a)暫時恢復,除非且直到該版權持有人明確並
+ 最終終止您的授權;以及(b)永久恢復,如果該版權持有人未能在您
+ 停止違反後60天內,以某種合理方式通知您違反的情事。
- 此外,如果版權所有者以某種合理的方式通知您違反了本許可,這是您第一次
- 從該版權所有者處收到違反本許可的通知(對於任何作品),並且您在收到通知
- 後的30天內糾正違規行爲。則您從特定版權所有者處獲得的許可將永久恢復.
+ 此外,如果版權持有人以某種合理方式通知您違反的情事,而這是您
+ 第一次從該版權持有人處收到違反本許可證的通知(就任何作品而言),
+ 並且您在收到通知後30天內糾正違反行為,則您從該特定版權持有人處
+ 獲得的授權將永久恢復。
-我們提供這些保證的目的是鼓勵更多地使用該軟體。我們希望公司和個人使用、修改和
-分發此軟體。我們希望以公開和透明的方式與用戶合作,以消除我們對法規遵從性或強制
-執行的任何不確定性,這些不確定性可能會限制我們軟體的採用。我們將法律行動視爲
-最後手段,只有在其他社區努力未能解決這一問題時才採取行動。
+我們提供這些保證的目的是鼓勵更多人使用該軟體。我們希望公司和個人使用、修改和
+散布此軟體。我們希望以公開和透明的方式與使用者合作,消除外界對我們在遵循或
+執行許可證方面之期望的任何不確定性,以免這些不確定性限制我們軟體的採用。
+我們將法律行動視為最後手段,只有在社群的其他努力未能解決問題時才會採取。
-最後,一旦一個不合規問題得到解決,我們希望用戶會感到歡迎,加入我們爲之努力的
-這個項目。共同努力,我們會更強大。
+最後,一旦不合規的問題得到解決,我們希望該使用者會感到受歡迎,加入我們在這個
+專案上的努力。攜手合作,我們會更強大。
-除了下面提到的以外,我們只爲自己說話,而不是爲今天、過去或將來可能爲之工作的
-任何公司說話。
+除下文另有註明者外,我們僅代表自己發言,而非代表我們目前、過去或將來可能任職
+的任何公司。
- Laura Abbott
- Bjorn Andersson (Linaro)
@@ -150,4 +154,3 @@ Linux 內核執行聲明
- Wei Yongjun
- Lv Zheng
- Marc Zyngier (Arm Ltd)
-
--
2.43.0
next prev parent reply other threads:[~2026-11-06 11:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 11:31 [PATCH 00/25] docs/zh_TW: process: resync translations with the English originals Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 01/25] docs/zh_TW: process: sync 1.Intro.rst with the English original Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 02/25] docs/zh_TW: process: sync 2.Process.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 03/25] docs/zh_TW: process: sync 4.Coding.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 04/25] docs/zh_TW: process: sync 5.Posting.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 05/25] docs/zh_TW: process: sync 6.Followthrough.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 06/25] docs/zh_TW: process: sync 7.AdvancedTopics.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 07/25] docs/zh_TW: process: sync 8.Conclusion.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 08/25] docs/zh_TW: process: sync code-of-conduct-interpretation.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 09/25] docs/zh_TW: process: sync code-of-conduct.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 10/25] docs/zh_TW: process: sync gdb-kernel-debugging.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 11/25] docs/zh_TW: process: sync development-process.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 12/25] docs/zh_TW: process: sync email-clients.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 13/25] docs/zh_TW: process: sync kernel-driver-statement.rst " Chen-Yu Yeh
2026-11-06 11:31 ` Chen-Yu Yeh [this message]
2026-11-06 11:31 ` [PATCH 15/25] docs/zh_TW: process: sync management-style.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 16/25] docs/zh_TW: process: sync security-bugs.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 17/25] docs/zh_TW: process: sync volatile-considered-harmful.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 18/25] docs/zh_TW: process: sync 3.Early-stage.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 19/25] docs/zh_TW: process: sync coding-style.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 20/25] docs/zh_TW: process: sync embargoed-hardware-issues.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 21/25] docs/zh_TW: process: sync howto.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 22/25] docs/zh_TW: process: sync license-rules.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 23/25] docs/zh_TW: process: sync stable-api-nonsense.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 24/25] docs/zh_TW: process: sync submit-checklist.rst " Chen-Yu Yeh
2026-11-06 11:31 ` [PATCH 25/25] docs/zh_TW: process: sync submitting-patches.rst " Chen-Yu Yeh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261106113142.706783-15-chenyou910331@gmail.com \
--to=chenyou910331@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=wy@wyuan.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®