Re: What's cooking in zh_CN (Jul 2026)

[Weijie Yuan <wy@wyuan.org>]

On Tue, Jul 14, 2026 at 05:32:12PM +0800, Dongliang Mu wrote:
> On Tue, Jul 14, 2026 at 12:51 AM Weijie Yuan <wy@wyuan.org> wrote:
> >
> > Hi all,
> >
> > Since I made many noise these days on the list, which took up a lot of
> > maintainers' time. This email summarizes the patches for zh_CN that are
> > currently pending on the mailing list.
> 
> This is awesome. Maybe we can establish a dashboard for the activities
> in zh_CN/TW related patches of linux-doc.
> 
> I personally kept a knowledge base in the IMA (an app for storing
> knowledge base in the cloud) in our club to monitor these activities.

I remember kernel.org itself already provides this:

  https://patchwork.kernel.org/

Is this similar to your idea? But I haven't look deep into patchwork
before.

Of source, having our own thing is definitely okay.

> > * Doehyun Baek (2026-07-08) 7 commits
> >   [PATCH v6 0/7] docs/zh_CN: update DAMON translations
> >   [PATCH v6 1/7] docs/zh_CN: update DAMON design translation
> >   [PATCH v6 2/7] docs/zh_CN: add DAMON_STAT usage translation
> >   [PATCH v6 3/7] docs/zh_CN: update DAMON index translation
> >   [PATCH v6 4/7] docs/zh_CN: update DAMON start translation
> >   [PATCH v6 5/7] docs/zh_CN: update DAMON usage translation
> >   [PATCH v6 6/7] docs/zh_CN: update DAMON reclaim translation
> >   [PATCH v6 7/7] docs/zh_CN: update DAMON LRU sort translation
> 
> Maybe I can take a review tomorrow.

No rush of course ;-)

> > Okay, I have checked the 200 most recent messages on the mailing list,
> > going back to 15:09 UTC on February 25, 2026. If I have missed anything,
> > or I made a mistake somewhere, please let me know.
> >
> > As you may have noticed, I borrowed (stole) this idea from Junio C
> > Hamano. Sending this kind of message, somewhat like a weekly status
> > report, not only helps maintainers keep track of outstanding work, but
> > also lets contributors know the current status of their patches.
> 
> As mentioned before, can we have a dashboard to see the status of
> patches in zh_CN/TW? This is more useful in my mind.
> 
> >
> > More importantly, it gives newcomers an overview of the current state of
> > the project. New contributors can begin not only by submitting patches,
> > but also by reviewing patches already posted to the mailing list,
> > thereby learning how our workflow operates. This may also help reduce
> > the review burden on our friendly maintainers.
> >
> > I would like to try this kind of periodic report as an experimental
> > effort, with its frequency adjusted according to the size of the patch
> > backlog and the level of activity on the mailing list. What do you
> > think? Please feel free to make comments.
> 
> I think this is fine since linux-doc or narrowly zh_CN/TW do not have
> many volumes of patches per day.

Exactly. I think Junio C Hamano has a script to do this automaticly, but
I did this manually because our volumes is not that high as Git.

> > By the way, I borrowed the subject line directly from Git's "What's
> > cooking in git.git". Does anyone have a better suggestion for the name? ;-)
> 
> fine with this title

OK, let's keep it now.