Hi

"accepted as language in software development"

is as long as the person able to speak English at first place, persons
are not able to speak English are automatically excluded in the
mailling list, so opinions here(only from people able to speak
English) seems will be limited as well.

But just a very interesting thoughts, no one said about language
restrictions anyway, and English is not always be the first language
for many of us.

On Tue, Jun 19, 2012 at 2:55 PM, Wido den Hollander <w...@widodh.nl> wrote:
> On 06/19/2012 02:50 PM, Robert Schweikert wrote:
>>
>> On 06/19/2012 05:43 AM, Lu Heng wrote:
>>>
>>> Hi
>>>
>>> One very interesting question raised by my Chinese tech today, can we
>>> use Chinese in the mailling list.
>>>
>>> 1. Seems there is no language restriction about in the mailling list,
>>> and all language should be equal.
>>>
>>> 2. As I read and touched these days in the mailling list, a lot guy
>>> from crixi developing CS are in fact Chinese.
>>>
>>> Any thoughts?
>>>
>>
>> If this is needed then we should have a language specific list. However,
>> from a development point of view that'll put a big dent into
>> collaboration.
>
>
> I'd see a cloudstack-users-cn mailinglist earlier then a Chinese developer
> list.
>
> My €0,02 says we should stick to English on the development list to keep
> collaboration consistent. English isn't my native language either, but it
> seems to be accepted as the language in software development?
>
> As far as I know English is harder to learn for Chinese people due to the
> huge language differences. I wouldn't vote against a Chinese development
> list, but I wouldn't endorse it either, due to the above reasons.
>
> Wido
>
>>
>> My $0.02
>> Robert
>>
>



-- 
--
Kind regards.
Lu

This transmission is intended solely for the addressee(s) shown above.
It may contain information that is privileged, confidential or
otherwise protected from disclosure. Any review, dissemination or use
of this transmission or its contents by persons other than the
intended addressee(s) is strictly prohibited. If you have received
this transmission in error, please notify this office immediately and
e-mail the original at the sender's address above by replying to this
message and including the text of the transmission received.

Reply via email to