From: Jonathan Corbet <corbet@lwn.net>
To: Chen-Yu Yeh <chenyou910331@gmail.com>
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: Re: [PATCH v2] MAINTAINERS: update Traditional Chinese documentation maintainers
Date: Wed, 05 Aug 2026 12:51:39 -0600 [thread overview]
Message-ID: <8733wspfic.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260804201012.110713-1-chenyou910331@gmail.com>
Chen-Yu Yeh <chenyou910331@gmail.com> writes:
> 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], list 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.
>
> Move Hu Haowen to CREDITS and drop his personal repository links,
> which are no longer reachable. The current translation is built on his
> work, but MAINTAINERS is a list of who to contact, and the listed
> address has not answered zh_TW mail for about two years, which is what
> made zh_TW hard to contribute to in the first place.
>
> 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>
> ---
> Changes in v2:
> - Drop Hu Haowen's M: entry (Jonathan Corbet); a CREDITS patch will
> follow separately.
> - Move the division of responsibilities below --- as suggested by
> Weijie: it will drift over time, and a commit message is the one
> place it cannot be updated.
> - Collected Weijie's Acked-by.
>
> Current split of work, for the record rather than for the git history:
>
> Chen-Yu Yeh - translation and zh_TW terminology decisions
> Weijie Yuan - miscellaneous matters, list monitoring, status reports
> Dongliang Mu - review
>
> The address in the CREDITS entry is the one Hu Haowen asked to be
> listed under in [3].
>
> [3] https://lore.kernel.org/linux-doc/20260220160201.41149-1-srcres258@furdevs.cn/
>
> CREDITS | 4 ++++
> MAINTAINERS | 6 +++---
> 2 files changed, 7 insertions(+), 3 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2026-08-05 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 20:10 [PATCH v2] MAINTAINERS: update Traditional Chinese documentation maintainers Chen-Yu Yeh
2026-08-05 7:01 ` Dongliang Mu
2026-08-05 7:21 ` Weijie Yuan
2026-08-05 13:31 ` Jonathan Corbet
2026-08-05 15:31 ` Weijie Yuan
2026-08-05 18:51 ` Jonathan Corbet [this message]
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=8733wspfic.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=chenyou910331@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.