From: Tsugikazu Shibata <tshibata@ab.jp.nec.com>
To: leo@zh-kernel.org
Cc: rob@landley.net, gh@us.ibm.com, hpa@zytor.com,
kunai@linux-foundation.jp, holzheu@linux.vnet.ibm.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
lf_kernel_messages@linux-foundation.org, tshibata@ab.jp.nec.com
Subject: Re: [PATCH] Chinese Language Maintainer
Date: Fri, 20 Jul 2007 03:06:36 +0900 (JST) [thread overview]
Message-ID: <20070720.030636.68037027.tshibata@ab.jp.nec.com> (raw)
On Wed, 18 Jul 2007 00:24:07 +0800, leo wrote:
(snip)
> Here is the helper process I propose to help more people to participate.
> Suggestions and comments are welcomed.
I think this seems mostly good. I will try to comment a bit.
> 1) Developer who can't speak English or has a problem going through the
I think early stage of developer may have "difficulty of using
English". I think this may better than "can't speak".
> submission process sends patches to the Language maintainer and cc the
> local mail list provided.
> 2) Language maintainer and experienced Linux developer on the local mail
> list can review the patch and give comments in native language.
In the review process, translated document of HOWTO,
SubmittingPatches, CodingStyle and SummitChecklist are used in the
local mail list.
> 3) When the language maintainer thinks the patch is good in general, he
> will pass the patch onto corresponding subsystem maintainer and mail
> list for further review, cc the author and local list.
> 4) The author communicates directly with the community.
> 5) If the author has a problem understanding the comments or expressing
> himself in English, he can ask for help in native language on the local
> list. The language maintainer and the developers on the list are
> responsible to help out.
> 6) When the developer gets familiar with the submission process and can
> go through it with no problem, he can then submit patch directly without
> the helper process and probably join the mail list to help other new
> developer.
>
> - Leo
>
next reply other threads:[~2007-07-19 18:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 18:06 Tsugikazu Shibata [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-12 13:53 Documentation of kernel messages (Summary) Li Yang-r58472
2007-07-12 16:05 ` [PATCH] Chinese Language Maintainer Rob Landley
2007-07-12 19:52 ` Geert Uytterhoeven
2007-07-12 20:02 ` Pavel Machek
2007-07-13 7:42 ` Geert Uytterhoeven
2007-07-13 16:06 ` Rob Landley
2007-07-13 12:43 ` Li Yang
2007-07-13 17:52 ` Rob Landley
2007-07-15 14:42 ` Li Yang
2007-07-15 18:12 ` H. Peter Anvin
2007-07-15 18:50 ` Alan Cox
2007-07-15 19:11 ` H. Peter Anvin
2007-07-15 20:25 ` Rik van Riel
2007-07-16 4:40 ` Ganesan Rajagopal
2007-07-16 21:43 ` Alan Cox
2007-07-17 7:19 ` Ganesan Rajagopal
2007-07-15 18:53 ` Li Yang
2007-07-15 20:25 ` Rene Herman
2007-07-16 9:17 ` Dr. Keith G. Bowden
2007-07-16 2:49 ` Tsugikazu Shibata
2007-07-16 3:03 ` H. Peter Anvin
2007-07-17 16:24 ` Li Yang
2007-07-17 21:06 ` Rob Landley
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=20070720.030636.68037027.tshibata@ab.jp.nec.com \
--to=tshibata@ab.jp.nec.com \
--cc=akpm@linux-foundation.org \
--cc=gh@us.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=kunai@linux-foundation.jp \
--cc=leo@zh-kernel.org \
--cc=lf_kernel_messages@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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
all inboxes | Powered by JetHome®