From: Weijie Yuan <wy@wyuan.org>
To: Chen-Yu Yeh <chenyou910331@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.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
Subject: Re: [PATCH] MAINTAINERS: update Traditional Chinese documentation maintainers
Date: Fri, 31 Jul 2026 14:56:33 +0800 [thread overview]
Message-ID: <amxHIcHC0vjcp5bG@wyuan.org> (raw)
In-Reply-To: <20260731032101.7244-1-chenyou910331@gmail.com>
On Fri, Jul 31, 2026 at 11:21:01AM +0800, Chen-Yu Yeh wrote:
> 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
Monitoring the list is the plan I made before touching MAINTAINERS file,
(in case there are patches land on the list but not in our mailbox). So
if this patch applied, I guess it would be no long needed for me to
monitor the list? (Although I always go through the archives)
I do some review, and wish to handle all miscellaneous matters, leaving
enough energy for the other two to do the work they are good at.
I thought for a while to find a better wording here..
Weijie - Miscellaneous matters? Or I leave the question to you ;-)
Or we could leave the division of responsibilities out of commit message
and instead write it after '---', To prevent any future changes from
going unnoticed and not being explicitly mentioned in the commit message
again. (perhaps years later)
However, those who are interested can still find our original division
of responsibilities under '---' in the archive.
But this is just a minor issue, not a big deal. It can be handled in any
way.
> 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.
Yup, and I would also love to maintain our own tree on git.kernel.org
(and mirrors?) so that we don't need to bother Alex every time.
In general I guess it would be more efficient, what do you think?
> [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?
Absolutely ;-)
Acked-by: Weijie Yuan <wy@wyuan.org>
>
> 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>
Agreed: Haowen is always welcomed :-)
I remembered Haowen sent a patch here [1] aiming to change his name and
address to:
Haowen Hu <srcres258@furdevs.cn>
Can we pick it up here?, while it may also needs Haowen's double check..
[1] https://lore.kernel.org/linux-doc/20260220160201.41149-1-srcres258@furdevs.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/
next prev parent reply other threads:[~2026-07-31 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 3:21 [PATCH] MAINTAINERS: update Traditional Chinese documentation maintainers Chen-Yu Yeh
2026-07-31 6:56 ` Weijie Yuan [this message]
2026-07-31 13:02 ` Jonathan Corbet
2026-07-31 15:45 ` Weijie Yuan
2026-07-31 17:45 ` 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=amxHIcHC0vjcp5bG@wyuan.org \
--to=wy@wyuan.org \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=chenyou910331@gmail.com \
--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 \
/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