incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin" <>
Subject Re: accommodate non-native-English-writing developers
Date Sat, 01 Nov 2008 08:16:13 GMT
On Sat, Nov 1, 2008 at 2:00 AM, David Crossley <> wrote:
> Luciano Resende wrote:


>> In Tuscany, our experience with having a non-English mailing list has
>> been very interesting, the forum has been created just a month or two
>> ago and the number of subscribers and the activity on it has been
>> growing very rapidly, this makes me think that there is indeed a
>> language barrier that would prevent some individuals to participate in
>> the english discussion lists, although these members are very
>> technically skilled and willing to consume and become a contributor of
>> your project.
>> In order to allow others to be aware of what's going on in this forum,
>> we have Raymond, our Chinese speaking community member, watching the
>> forum, and communicating issues back to our official English list. We
>> also found it very useful to use Google infrastructure to perform
>> automatic-translation of the forum [1], this allows anyone to lurk
>> around and have a feeling of what's being discussed.
>> [1]
> I wonder if it would be appropriate to modify mod_mbox to
> add a footer option to translate. That way any of our
> mail lists could be immediately translated via
> Also all english-speaking developers could translate any
> posting and reply in english.

big +1

this could be taken a lot further: translation links could be added to
the mail archives . i like the idea of routinely adding translation
links to all our web content.

IMHO the time is right for apache to start reconsidering the policy
towards translations. ATM canonical content is created in english and
unofficial translations are hosted off shore. IIRC the reasons were
about supervision (in particular, ensuring that illegal or abusive
content wasn't hosted) given the small number of multi-lingual

AIUI httpd is the exception. as part of it's documentation effort, it
hosts onshore translations. i think that apache can learn from the way
this works and start something similar on an apache-wide basis.

i think that the improved quality of automatic translations means that
this decision should be reviewed and (quite possibly) reversed. commit
emails for translations could be automatically linked to an automated
translation of the new document. this may not be good enough for
working out whether the prose is a good translation but should be good
enough to allow basic supervision.

- robert

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message