From: Jonathan Corbet <corbet@lwn.net>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: On global citations, URLs and translations
Date: Thu, 14 Nov 2019 06:22:55 -0700 [thread overview]
Message-ID: <20191114062255.4f4ffc2f@lwn.net> (raw)
In-Reply-To: <25c9ec73-64d3-a5dc-2f64-863c04dad22d@darmarit.de>
On Wed, 13 Nov 2019 10:37:21 +0100
Markus Heiser <markus.heiser@darmarit.de> wrote:
> I have a doubt that translating has to be a part of the kernel development.
>
> Minimal English is one of the prerequisites to be a part of the community.
> Maintainers do not master foreign languages, they are forced to commit
> blindly without quality assurance. APIs will never be translated and
> the translation of articles is at random.
We've had this particular discussion before. My own feeling is that
translated documentation can make an easier entry point for developers
who did not grow up speaking English; that, in turn, makes our community
just a little bit more inclusive. We certainly can't *require* any sort
of translation work, but I'm happy to encourage it where the interest
exists.
Thanks,
jon
next prev parent reply other threads:[~2019-11-14 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 6:54 On global citations, URLs and translations Miguel Ojeda
2019-11-12 14:17 ` Jani Nikula
2019-11-12 15:42 ` Jonathan Corbet
2019-11-12 15:59 ` Jani Nikula
2019-11-13 9:37 ` Markus Heiser
2019-11-13 21:49 ` Federico Vaga
2019-11-14 13:22 ` Jonathan Corbet [this message]
2019-11-14 0:54 ` Miguel Ojeda
2019-11-14 8:35 ` Federico Vaga
2019-11-14 9:25 ` Jani Nikula
2019-11-13 21:07 ` Federico Vaga
2019-11-14 9:28 ` Jani Nikula
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=20191114062255.4f4ffc2f@lwn.net \
--to=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=miguel.ojeda.sandonis@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).