Le 2010-10-18 20:22, Jean-Christophe Helary a écrit :
I would like to propose that unlike what existed under Sun and Oracle, the linguistic communities
_including_ the English speaking community, are all identified by a specific language marker and
that all the lists that do not use that language marker are explicitly multilingual.
The status quo under Sun and Oracle came from the fact that both Sun and Oracle were American based
and mostly English speaking structures but we have no reason to reproduce that in the TDF.
That basically means that:
All the English speaking lists are @en.libreoffice.org
And that all the lists @libreoffice.org are multilingual.
This is the only way to ensure that no linguistic community has more power in the decision process
than any other which is a basic requirement for all democratic process.
There are enough multilingual people in the respective communities to ensure that the communication
gap is bridged in all those lists.
I was under the impression that we were all in agreement, that the
"lingua franca" of the mailists is English and that localized mailists
were to encourage users to contribute in their own language.
Therefore, we should then make sure that information/issues from the
localized mailists is passed on to the main English mailist through
either the mailist moderator or some ambassador/spokesperson to the
localized mailists to assure the flow of information to the SC or
appropriate decision making group.
Maybe we should work on improving the process of the reporting of
localized groups' concerns to the main English mailists.
Having a multi-lingual approach to the mailist, IMHO, would not be an
effective way of running the LibO project. Having to translate and
interpret cultural idiosyncrasies would be far more difficult and
confusing than having to deal solely with English as the default
language of communication between groups.
I can well imagine that, if you consider the various cultural/language
backgrounds of SC members, we could also ask that SC members at least
try to frequent mailists that are compatible with their mother-tongue or
language comprehension. For example, if an member of the SC is from
German background, then this SC member could easily frequent the German
localized groups and participate in their discussions as well as help to
report back to the main English mailists of any concerns from the German
groups.
Therefore, the localized groups would have the following to help with
the flow of any concerns to the main English mailist:
1. An ambassador/spokesperson would make sure that the flow of
information/concerns of localized groups would be taken up in the main
English mailists. These ambassadors could also report back, perhaps on a
monthly basis, or the topics of conversations that were taken up in
their localized groups during the month.
2 SC members lurking/participating in their native localized group
mailist could also take part in reporting back to the main English
mailists of any information/concerns of their respective localized group.
The main responsibility would however be shouldered by the
ambassadors/spokespersons of the localized groups. These people would be
the backbone of the reporting process of the localized groups.
Marc
--
E-mail to discuss+help@documentfoundation.org for instructions on how to unsubscribe
List archives are available at http://www.documentfoundation.org/lists/discuss/
All messages you send to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.