From: Chen-Yu Yeh <chenyou910331@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alex Shi <alexs@kernel.org>, Weijie Yuan <wy@wyuan.org>,
Dongliang Mu <dzm91@hust.edu.cn>,
Yanteng Si <si.yanteng@linux.dev>,
Hu Haowen <2023002089@link.tyut.edu.cn>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Chen-Yu Yeh <chenyou910331@gmail.com>
Subject: [PATCH] MAINTAINERS: update Traditional Chinese documentation maintainers
Date: Fri, 31 Jul 2026 11:21:01 +0800 [thread overview]
Message-ID: <20260731032101.7244-1-chenyou910331@gmail.com> (raw)
The zh_TW translation has been unmaintained for about two years: the
listed maintainer has been unreachable, and because no active
maintainer was listed, get_maintainer.pl did not point contributors at
anyone who could actually pick up a patch. My own zh_TW patch sat on
the list for five weeks for exactly that reason.
Following the discussion in [1] and the plan in [2], add the people
who have stepped up to carry zh_TW forward, with a shift in focus
towards Taiwanese Mandarin terminology rather than a plain
simplified-to-traditional conversion:
Chen-Yu Yeh - translation and zh_TW terminology decisions
Weijie Yuan - process, list monitoring and status reports
Dongliang Mu - review
Hu Haowen is kept in the list; his earlier work is the basis of the
current translation and he is welcome back at any time. His personal
repository links are dropped, as they are no longer reachable.
zh_TW stays a separate entry and is maintained separately from zh_CN;
the two may share a tree for pull requests, but the review and
terminology work is independent.
[1] https://lore.kernel.org/linux-doc/20260603082531.263115-1-chenyou910331@gmail.com/
[2] https://lore.kernel.org/linux-doc/amcZ5SI3-Hzw4HkJ@wyuan.org/
Signed-off-by: Chen-Yu Yeh <chenyou910331@gmail.com>
---
This comes earlier than the trial period I mentioned when I first
offered to help with zh_TW [1]. Weijie raised the MAINTAINERS question
off-list because the lack of a reachable maintainer has been the main
bottleneck so far, and both he and Dongliang have confirmed they are
willing to be listed. Happy to hold this until after the v2 series
lands if you would prefer to see that first.
Weijie, Dongliang: we settled this off-list, but could you ack here so
the agreement is on the record?
MAINTAINERS | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2f9472c1a090..60f77e7fd3f5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -27460,10 +27460,11 @@ F: kernel/trace/trace_osnoise.c
F: kernel/trace/trace_sched_wakeup.c
TRADITIONAL CHINESE DOCUMENTATION
+M: Chen-Yu Yeh <chenyou910331@gmail.com>
+M: Weijie Yuan <wy@wyuan.org>
M: Hu Haowen <2023002089@link.tyut.edu.cn>
+M: Dongliang Mu <dzm91@hust.edu.cn>
S: Maintained
-W: https://github.com/srcres258/linux-doc
-T: git https://github.com/srcres258/linux-doc.git doc-zh-tw
F: Documentation/translations/zh_TW/
TRIGGER SOURCE
--
2.43.0
next reply other threads:[~2026-07-31 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 3:21 Chen-Yu Yeh [this message]
2026-07-31 6:56 ` [PATCH] MAINTAINERS: update Traditional Chinese documentation maintainers Weijie Yuan
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=20260731032101.7244-1-chenyou910331@gmail.com \
--to=chenyou910331@gmail.com \
--cc=2023002089@link.tyut.edu.cn \
--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