I am assisting a new project to potentially come to the Incubator. It will be producing an implementation of a multi-part ISO standard. Hence the strong country-based nature, means that international language issues will be paramount.
My initial question was about how to conduct the mailing list discussions. Of course the issues are much wider. Some feeling for how to handle these issues will help us to make a better proposal to the Incubator. For example, some key parts of its puzzle are developed by Japanese people. Other parts by English-speaking people. Some of these people can read/write English, but others are not at all comfortable. Some code contributions would have Japanese variable names and internal code documentation. I understand that the code documentation could be augmented with English. However, i don't see how to deal with actual code and ongoing contributions. Obviously the non-English speaking people need to interpret any English changes to the code, and vice-versa. Mail lists: Should people just partipipate on the podling's dev mail list in their own languages? Then expect that someone summarises the outcomes and decisions into English/Japanese. Or would it be better to have separate dev language lists, with the same summarising outcome. The former would enable replies to be threaded with the other language. In any case, i reckon that it would be desirable to have these lists at apache.org Documentation has similar issues. Likewise the svn commit log messages. Does anyone here have some tips for conducting an open development project that accommodates multi-lingual developer participation? -David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
