I know these are just two examples and, yes, I am closely involved in both, but, I wonder how the localisation groups hear of these projects and whether they understand that they may join these regardless of the language barriers.
I wonder if there is a method in place where these projects can be piped and announced directly into each localised mailists where members can decide whether to join in or not. I am sure there are Drupal experts in Spain or S.America who could join the team. I am sure there are members in Russia, Portugal, Costa Rica, Japan that could host a release party and etc. What about the dev's mailist? I am sure the are some competent non-English-speaking coders who could join in.
I am concerned that, right at the very start of LO community building, there seems, to me, no method to inform the mailists of projects that have gone through the rigours of discussion, consensus, formulation and adoption. We are all working in our own little islands.
Even worse, we are completely blind as to what is being debated and decided in the localisation groups. For example, I am on the French mailist, and, by and large, there is a certain amount of discussion going on. I am also on the Spanish mailist, but there is very little discussion going on this mailist, which, to me, is surprising given the amount of Spanish speaking population/countries on earth. Is this pretty typical of the past OOo mailist banter?
Christoph's Work Items wiki page is a step in the right direction, but it still doesn't address the problem with communicating to the different localised mailists of these projects. They need to know that they may participate in larger non-localised projects and we will try to deal with the language barrier (google translate is a good choice).
Would there be any idea on how to do this efficiently? Marc -- E-mail to marketing+help@libreoffice.org for instructions on how to unsubscribe List archives are available at http://www.libreoffice.org/lists/marketing/ All messages you send to this list will be publicly archived and cannot be deleted