On Saturday 10 June 2006 16:23, you wrote: > On Sat, Jun 10, 2006 at 03:01:37PM -0700, Bastian, Waldo wrote: > > So what can be done to overcome such barrier? I'm inclined to think of > > bi-langual liasion persons, or maybe a liason group whose mission it is > > to facilitate the integration of patches in upstream projects. Not sure > > how scalable that is. The extra indirection would also be a bit of a > > drag on the efficiency of the whole process. What do other people think > > about this?
(warning: talking out the side of my head on a quiet saturday afternoon) taking the precise example of Japan, what would likely work best within the kde project is if we had a few Japanese speakers who could manage bridging between the english and japanese communities, but essentially give the Japanese developers free reign to both work completely in their own language and without a whole lot of interaction with the "main" project. in fact, the idea of a "main project" may end up being pretty broken when trying to engage more Asian involvement. perhaps the liaisons could keep an eye on what is being worked on and developed in the Japanese community and ensure it isn't being overlapped by efforts in the western community. in other words, perhaps it would work best if the Japanese community worked on projects that were easily done in parallel with low amounts of daily/weekly communication needed. things like specific applications or particularly libraries. that way instead of trying to solve the east/west cultural boundary issues, which better people than us have been working on for a couple centuries, we can simply compartmentalize the project along those lines. this is based on my thinking of how much communication happens between, for instance, the amarok team and the kontact team. very, very little =) they could probably have one person on each team that speaks the same language and do just fine. the trick would be in kick starting this and that probably really does require local people that can keep a foot in both camps getting things moving. but we probably don't need many of them. > For Inkscape, we've been successful at involving speakers of other > languages. Examples of steps we as a project have taken to help > facilitate and encourage this involvement: ... > Often we have been approached by the GNOME translation team about moving the interesting thing about translation is that it is a naturally compartmentalized project. you need maybe one person who can communicate occasionally with the central translation coordinator. otherwise, with a mailing list, irc channel, website, etc in their preferred langauge(s) they can coordinate and make progress within their own language community quite effectively. -- Aaron J. Seigo Undulate Your Wantonness GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
pgpOJWXg1QtQe.pgp
Description: PGP signature
_______________________________________________ Desktop_architects mailing list [email protected] https://lists.osdl.org/mailman/listinfo/desktop_architects
