It won't be a community if people are unable to follow the discussions. I think that it would be fine to handle user@ traffic in whatever language, but we need to enforce English as the language of community decision making.
On Mon, Nov 23, 2015 at 1:44 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > On Mon, Nov 23, 2015 at 10:39 AM, Alex Harui <aha...@adobe.com> wrote: >> On 11/21/15, 7:06 PM, "William A Rowe Jr" <wr...@rowe-clan.net> wrote: >> >>>That was my reaction. A dev-cn@community.apache. org could be a useful >>>discussion vehicle to engage prospects and help with facilitating that >>>engagement. It wouldn't look all that much different than the usual >>>English Q&A here on dev@c a o. >> >> My initial instinct is that per-language mailing lists aren't a good idea. >> But I would not require that folks post in English either. Otherwise it >> feels like saying at ApacheCon that you have to go another room to have a >> conversation in your native language. Even if I can't read what is being >> written by others, I can probably pick out a few keywords and at least >> have an idea that certain topics are being discussed. > > There's also http://translate.google.com ;-) > > Thanks, > Roman.
