From: John Snow <jsnow@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] block: Move away from anglo-centricity
Date: Fri, 1 Apr 2016 17:19:46 -0400 [thread overview]
Message-ID: <56FEE5F2.9020100@redhat.com> (raw)
In-Reply-To: <1459522215-13950-1-git-send-email-mreitz@redhat.com>
On 04/01/2016 10:50 AM, Max Reitz wrote:
> In its organizational structure, the qemu project is rather
> decentralized: Many different maintainers manage their own more or less
> secluded subsystems. However, regarding languages, it is still rather
> anglo-centric.
>
> This issue has been brought up multiple times in regards to user-visible
> output such as error messages and has unfortunately generally been
> dismissed, except for some UIs.
>
> Development always flows from the developer community to the user. Our
> developer community is just as diverse (or at least I hope it is) as our
> user base. Therefore, we should reflect this diversity in our
> development process in order for this diversity to reach our users as
> well, so they can benefit from it.
>
> The human-targeted part of that development process are comments in the
> source code, obviously. Thus, in order to exhibit qemu's diversity, it
> makes sense for each subsystem's comments to be translated into the
> maintainer's native language.
>
> Unfortunately, I do not speak Swabian.
>
> However, as a submaintainer under Kevin, I think it will be fine to
> translate the comments into German, as that is supposedly a language we
> both share.
>
> I'm certain that this will not hamper development itself by much. First
> of all, many other developers in the block area are able to speak
> German: Markus Armbruster, Stefan Hajnoczi, Peter Lieven, Stefan Weil,
> just to name a few.
>
> Second, good code is supposed to be self-explanatory, i.e. without
> reading the comments. While it should go without saying that the block
> layer's code quality is simply marvelous, we can now proof that it
> indeed is, by seeing whether people who cannot speak German can still
> understand the code.
>
> (Although some of our code is rumored to be rather hard to understand
> even with the comments. But those rumors are purely unfounded, I am
> sure.)
>
> In the rather improbable event that someone is not able to understand
> the code without being able to read the comments, they will then need to
> learn German. So this is fine, too.
>
> Third, this will surely attract a wave of German developers who were so
> far unable to participate in qemu's development because of the language
> barrier. In order to facilitate this process, the next step will be to
> use German commit messages for every commit in the block layer and to
> allow German variable names.
>
> I am sure if all maintainers follow this process of translating their
> subsystem's comments, variable names and string contents into their
> native language, qemu will become a shining example of what we call
> „Kraut und Rüben“. And everyone knows how much the Krauts like Kraut.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
Acked-by: John Snow <jsnow@redhat.com>
As a follow-up, please consider translating the legacy block devices so
some right-minded developers will be able to understand what's going on
inside of them, because I sure as hell don't.
TIA
--js
next prev parent reply other threads:[~2016-04-01 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 14:50 [Qemu-devel] [PATCH] block: Move away from anglo-centricity Max Reitz
2016-04-01 16:01 ` Paolo Bonzini
2016-04-01 17:56 ` Christian Borntraeger
2016-04-01 21:19 ` John Snow [this message]
2016-04-04 15:11 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=56FEE5F2.9020100@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.