2022-05-17 01:20:41

by Yanteng Si

[permalink] [raw]
Subject: [PATCH v2 0/1] docs/zh_CN: add Yanteng to zh_CN maintainer

V2:
* Pick Alex's Reviewed-by tag.

V1:
* Add Yanteng Si into MAINTAINERS.

Yanteng Si (1):
MAINTAINERS: Become the docs/zh_CN maintainer

MAINTAINERS | 1 +
1 file changed, 1 insertion(+)

--
2.27.0



2022-05-17 06:32:50

by Yanteng Si

[permalink] [raw]
Subject: [PATCH v2 1/1] MAINTAINERS: Become the docs/zh_CN maintainer

It's time to become a maintainer of Chinese documentation, and Yanteng's plan
is to help everyone with the utmost enthusiasm and patience.

Signed-off-by: Yanteng Si <[email protected]>
Reviewed-by: Alex Shi <[email protected]>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 9ce78f2275dc..ff1364d9f7cc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4649,6 +4649,7 @@ F: Documentation/dev-tools/checkpatch.rst

CHINESE DOCUMENTATION
M: Alex Shi <[email protected]>
+M: Yanteng Si <[email protected]>
S: Maintained
F: Documentation/translations/zh_CN/

--
2.27.0


2022-05-18 00:37:26

by Jonathan Corbet

[permalink] [raw]
Subject: Re: [PATCH v2 1/1] MAINTAINERS: Become the docs/zh_CN maintainer

Yanteng Si <[email protected]> writes:

> It's time to become a maintainer of Chinese documentation, and Yanteng's plan
> is to help everyone with the utmost enthusiasm and patience.
>
> Signed-off-by: Yanteng Si <[email protected]>
> Reviewed-by: Alex Shi <[email protected]>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9ce78f2275dc..ff1364d9f7cc 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4649,6 +4649,7 @@ F: Documentation/dev-tools/checkpatch.rst
>
> CHINESE DOCUMENTATION
> M: Alex Shi <[email protected]>
> +M: Yanteng Si <[email protected]>
> S: Maintained
> F: Documentation/translations/zh_CN/

I've applied this. I am curious, though: what is your sense for what
being designated a "maintainer" means? Do you envision something beyond
reviewing patches (for which an "R:" entry would be most appropriate)?

In any case, you help with the documentation is appreciated!

Thanks,

jon

P.S. There is normally no need to send a new version of a patch just to
pick up a tag; b4 makes that just work.

2022-05-18 14:09:47

by yanteng si

[permalink] [raw]
Subject: Re: [PATCH v2 1/1] MAINTAINERS: Become the docs/zh_CN maintainer

Jonathan Corbet <[email protected]> 于2022年5月18日周三 03:28写道:
>
> Yanteng Si <[email protected]> writes:
>
> > It's time to become a maintainer of Chinese documentation, and Yanteng's plan
> > is to help everyone with the utmost enthusiasm and patience.
> >
> > Signed-off-by: Yanteng Si <[email protected]>
> > Reviewed-by: Alex Shi <[email protected]>
> > ---
> > MAINTAINERS | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 9ce78f2275dc..ff1364d9f7cc 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -4649,6 +4649,7 @@ F: Documentation/dev-tools/checkpatch.rst
> >
> > CHINESE DOCUMENTATION
> > M: Alex Shi <[email protected]>
> > +M: Yanteng Si <[email protected]>
> > S: Maintained
> > F: Documentation/translations/zh_CN/
>
> I've applied this. I am curious, though: what is your sense for what
> being designated a "maintainer" means? Do you envision something beyond
> reviewing patches (for which an "R:" entry would be most appropriate)?
>
> In any case, you help with the documentation is appreciated!

Jonathan Corbet, Alex Shi, and guys in the mail list.

We, all kernel developers who love Chinese documentation, are now
involved in a very interesting project: the localization of kernel
documentation into Chinese.

For a long time, we have been working on translating as much of the
English documentation into Chinese as possible, while neglecting to
maintain the growing amount of Chinese documentation, which is
becoming progressively more difficult to maintain. It's not just the
quantity that is difficult, but also the time. For example, if a
document is not updated in a timely manner, developers who have
difficulty with English will get old or even wrong guidelines, which
is not only a waste of time and effort for developers, but may also
result in the kernel not getting the code contributed by developers in
a timely manner.

During the translation, we found ourselves disagree on the translation
of some terms from time to time, especially on terms being translated
into Chinese for the first time; and sometimes it might not be easy to
reach agreement on such circumstances and provide a translation that
is trustworthy, up-to-date, and elegant in a short time.

At the same time, I've noticed that the translating kernel
documentations is a great entry point to many newbies, which is a
good thing, but adds to the burden of reviewing Chinese documentation
patches, as most of them tend to have great enthusiasm but are
unfamiliar with the patch creation and submission process. Of course,
we have very detailed documentation guidelines and they are translated
into Chinese, but they still need some help from us in their practice
process.

But that is the past. And now we are looking only to the future.

I will do my best to keep all the Chinese documentation as up-to-date
as the English documentation, and I will keep an eye on the latest
changes to each original document and quickly sync them to the Chinese
documentation. At the same time, I will work to move forward with a
plan to produce a glossary of terms, and to revise the current
documentation where a single English word is translated into multiple
Chinese words. Finally, I will provide every developer with as much
help as I can with my utmost enthusiasm and patience.


Thanks,
Yanteng