Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp514620iob; Wed, 18 May 2022 07:09:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw+z7oRJhFjeRbAN06bDzmu552PPWnpb/MME+HSl8Q1m0PzJwhYwRYtrUbIycOsvVnBbHUN X-Received: by 2002:a17:90b:1bca:b0:1dd:1f36:dc2a with SMTP id oa10-20020a17090b1bca00b001dd1f36dc2amr157290pjb.119.1652882987734; Wed, 18 May 2022 07:09:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652882987; cv=none; d=google.com; s=arc-20160816; b=J6q/rlcCXFQOPfsUKxFYBNsVoAwXN2WfPuZxk6YVGQkDWTrraP3e0EdvaAxqdqqzHe kBCc+nXuQlQYHTtMwtZPPBRdOVR6dDkxDrFo74LI2P1vPR0GtV2DpS15r7E9UnBtoovW GyMTdsJTkmnsof1hMSzxImzrntKNCq3iziw699dx5kvvKZMhgX5ZqbotY9x6FHtCchcA lKW3vaRGacdfHMC4VIQFHvAwXIoMv7jRlnMB3Bp8/Fc9/0pgyr5kdyfuK7FGy2sLpOsk NtI8Bp5TaXdhVeM00RZOlVhOrDuA4EwlQzZ09EgAyAUZ8dM0mklih8r2iCjvnqhjK8lt 2qYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=Pg9cHDfOmQbKA6sIGv2JPMMr6K3pv/vo5Tu+jGJ0f+A=; b=v+6XrvZK+ydV3K3i1UA91D9ITIXpgLTaGc4jth3+d4ghz5457j5quedix2S5qx3Hm+ pWu1QuQfRsXLN4hINAUEp3Z3s997IF9Sp9sdRlfZN5/92djDTXuKBmL2ycDxvkvsETPF 5BOHIL4F5q63LVoBC7WMZlVDIGcGiQN2NFU4QZI1myEfRQ+exu1gJiyhFrfp2tBQsnXG B2iws2BYyqQHu6sNtoGhgM2v1MeIcT1RxIJqJyy4eySI6X2ePZnlqthNQQstJGwQ/7A6 2ZEwTv15Eah9riZGviBSL9Fd40q1XdUYg+d1hGlz2Vv/epCV2HxE0xNgkEN+6A6f5WJ0 DyYA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="e6/AhQfY"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id ng15-20020a17090b1a8f00b001d98efcb4dbsi2986469pjb.186.2022.05.18.07.09.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 May 2022 07:09:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="e6/AhQfY"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 76D9030F5A; Wed, 18 May 2022 07:05:52 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238431AbiEROFo (ORCPT + 99 others); Wed, 18 May 2022 10:05:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35688 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231747AbiEROFn (ORCPT ); Wed, 18 May 2022 10:05:43 -0400 Received: from mail-yw1-x1130.google.com (mail-yw1-x1130.google.com [IPv6:2607:f8b0:4864:20::1130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 04B09187DAC; Wed, 18 May 2022 07:05:42 -0700 (PDT) Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-2fee9fe48c2so25773907b3.3; Wed, 18 May 2022 07:05:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Pg9cHDfOmQbKA6sIGv2JPMMr6K3pv/vo5Tu+jGJ0f+A=; b=e6/AhQfYrT8846Hg+aIPVzaVNoSL5XsanMKp811Mrs9WvxdjaycBT017rBix3zEiGm TlvUgokaIm0K6peenTPOV5Ao6qQL5/D+u/4MWTUKSpxKnpuBEt3BR9axyNsMFMyrZj+v ey+zthjQY63V86f9OZHFh+GpFlqMdOfccOiv7C+pzQJbWG3tRMkDFCQqFYLfcODly9NM j7Pkzpo9rEAIxXDdu+xQeuP5y7iE7HC9oidLejvRrPNl8OgpjI2UoXjr4ItMpnam5NUy JJapsiATGADzMGfya24pgCtEJo/LSp/aPzQpJvTvuErsZhuoYCREpg4lcUHMH9s3UJ/t oBJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Pg9cHDfOmQbKA6sIGv2JPMMr6K3pv/vo5Tu+jGJ0f+A=; b=DprFq9kExwc1QyirZTH8cVen0FMwZX/+VB3wgJdYlnUeKkcbQZjxoHbKB0mgxtHL76 u0U3IeABez4ad89gOohTBIdJrO9+p4z80hnZ+nUWr4457VkdrNPQq4apnYnpJOq8X4fq Bmyl3ema0O6rxWHywqpL2+IndzZB9JiUfT/EFXd88ibVl1GSJrDTkMBmAk7rDE2qNfNf lBz+yDuho5+FnluLxiuLeMU7lyN8owmfDhRkeRfU+0UOdJRBhoQ1pxcntgqya1mUC0mu mpmBaMfqE34jul1h9IdfDzt2/oVoMcncrh3EbIT2ESaIZNiUSqkOKPxHgbON1biFlIMm Tv0g== X-Gm-Message-State: AOAM532JNqRBOko1nzcERMNRMCErb4ZBfLrX+UeBtdoAlZUArOh40pff HqFK+Tz71/DZDXZ3thPqc8aGkq8eAoWQ2q/IY78= X-Received: by 2002:a81:4f0b:0:b0:2ff:2770:c267 with SMTP id d11-20020a814f0b000000b002ff2770c267mr8566295ywb.212.1652882741213; Wed, 18 May 2022 07:05:41 -0700 (PDT) MIME-Version: 1.0 References: <8735h8vu0x.fsf@meer.lwn.net> In-Reply-To: <8735h8vu0x.fsf@meer.lwn.net> From: yanteng si Date: Wed, 18 May 2022 22:05:29 +0800 Message-ID: Subject: Re: [PATCH v2 1/1] MAINTAINERS: Become the docs/zh_CN maintainer To: Jonathan Corbet Cc: Yanteng Si , Alex Shi , Alex Shi , Wu XiangCheng , Yeechou Tang , Huacai Chen , Jiaxun Yang , Linux Doc Mailing List , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jonathan Corbet =E4=BA=8E2022=E5=B9=B45=E6=9C=8818=E6=97= =A5=E5=91=A8=E4=B8=89 03:28=E5=86=99=E9=81=93=EF=BC=9A > > Yanteng Si 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 > > Reviewed-by: Alex Shi > > --- > > 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 > > +M: Yanteng Si > > 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