Interview: Sophie Gautier
2004-09-12
Sophie Gautier is the lead of the French Native Language 事業／計画（する） and a member of the Community 会議, OpenOffice.org's 治める／統治するing board. She has been 伴う／関わるd in developing and 主要な OpenOffice.org almost since the beginning. Sophie lives in and 作品 out of Burkina Faso, a habitation which has 現在のd unique 適切な時期s.
Sophie, I'll start with the basic question: How did you 最初 get 伴う／関わるd in OpenOffice.org?
I first was 伴う／関わるd in the Documentation 事業／計画（する）, 令状ing how-tos and working on the FAQ. And I also lurked on the discuss 名簿（に載せる）／表（にあげる） and and gave my opinion いつかs. Then the native-lang 事業／計画（する） was discussed and the Francophone 事業／計画（する） created, so I worked for it. But I still belonged to the Documentation 事業／計画（する） and, in 新規加入, became a member of Marketing 事業／計画（する） at its beginning, several years ago.
You have been the lead of the French Native-Language 事業／計画（する） (FR), the first Native-Language 事業／計画（する）, since 2002. Can you 述べる the work you do, as lead? In particular, what are the goals of the 事業／計画（する）?
述べるing the work I do would be too long, there are a lot of different things that I do, in fact, which make for the richness and the 利益／興味 of the work, but I feel the most important ones are : to catalyse energies, 組織する the different ideas and make them cohere enough to become 事業／計画（する）s, 追求する and encourage 作品 in 進歩 and make 完結するd work 認めるd troughout the whole community. I try to make the members of our 事業／計画（する） happy to be there and proud of what they have 遂行するd.
The goals of the 事業／計画（する） are mostly :
- To 伸び（る） more 使用者s...
- But also to 伸び（る） more developers to help to 改善する the 製品 and to 与える／捧げる third-party work (such as documentation, 追加する-ons, etc...).
- And to make those people aware of the community (the French speaking one and the whole OOo 事業／計画（する）), so as to create a synergy between them, the language 障壁 存在 a not-insignificant 障壁, いつかs. That is, I want for the さまざまな groups to 共同製作する and try to find ways of 打ち勝つing the language differences.
One feature of the Native-Lang 連合 事業／計画（する）s (NLC 事業／計画（する）s) that 耐えるs some discussion is, How is 開発 work (特に 核心 開発) articulated?
Yes this is a difficult part of the 仕事. OpenOffice.org is very large and not 平易な to 人物／姿／数字 out, and doing so 要求するs a lot of energy. 存在 in the 事業／計画（する） from the beginning is of 広大な／多数の／重要な help for me, because I know where to find what I'm searching for. To 最小限に減らす the difficulty for a developer wanting to join the community, and make him feel inside, even if his English is difficult, we have arranged it in FR so that the developer is …を伴ってd in his first steps by some members of the FR 事業／計画（する）, 実験（する）ing is done in French on the dev@fr.openoffice.org 名簿（に載せる）／表（にあげる）, and when the 開発 is 円熟した enough, 提案するd to the 関連した 核心 事業／計画（する）. In the same way, to try to attract developers, most of the important （警察などへの）密告，告訴（状） sent to the 核心 開発 名簿（に載せる）／表（にあげる）s are mirrored on the French-speaking 開発 名簿（に載せる）／表（にあげる） and translated.
This sounds やめる effortful! Who helps with this 過程?
Several members of our 事業／計画（する）, some of them are doing the 実験（する）s, others are 参加するing to 事業／計画（する）s like DBA, or API.
同様に, the FR 事業／計画（する） has been a leader in helping to 組織する 地元の (地域-based as …に反対するd to language-based) 使用者 groups and marketing 努力するs. Can you tell us about these? and, What have been the difficulties 遭遇（する）d in setting them up? In managing them?
FR 事業／計画（する） has the 利益 of having a good welcome in the French open -source community already in place, and lot of our members have helped us to keep good relations with them. We have 伸び（る）d visibility with their help.
The difficulty was to find a real 身元 and not be another LUG. We 手配中の，お尋ね者 to be an OpenOffice.org group (something like marketing an fr.openoffice.org label. This 強要するs us to be いつか strict on the way the community is 代表するd, but in the same time it gives 信用性 and consistency to the 事業／計画（する）. This is also possible because a large part of the french community is strong, and engaged in OOo evangelization.
How many such 地元の groups are there? Would you know?
I don't know really, but some 協会s like ADULLACT (協会 for the 開発 and use of 解放する／自由な ソフトウェア in the 行政) or AFUL (協会 for the use of 解放する／自由な ソフトウェア) for example, have been of 広大な／多数の／重要な help.
The FR 事業／計画（する） has recently （人命などを）奪う，主張するd 非常に／多数の 重要な 業績／成就s in getting French 政府 offices to use OpenOffice.org. These can be said to 含む the Inland 歳入 Service's move to open source 同様に as the City of Paris' consideration of it. A 重要な point 存在 that OpenOffice.org in French is 決定的な to any serious consideration of the open-source desktop, 特に the Linux desktop. Can you (a)手の込んだ／(v)詳述する on these 業績／成就s? In particular, what were the deciding factors? What were the arguments used? And the 反対する 問題／発行するs?
The first deciding factors was the cost, I must 自白する. Then several 連合させるd factors. First the 乗り気 of some スパイ／執行官 who was really 動機づけるd to make the 移住 happen in their 行政. It was 必須の and that individual is responsible, by his work, for these 業績／成就s. Then we must consider the 質 of the documentation (Fred Labbe's 論題／論文 for example), the 質 of the support 供給するd on our 名簿（に載せる）／表（にあげる）s, and the 関係s and the good communication 設立するd の中で several persons with 影響（力） in their organizations. And of course, a lot of follow up and physical presence anytime it was needed, all these things helped to make the 移住 feasible. I should also について言及する the work of the ADAE which has been of 広大な／多数の／重要な help in making people aware of what is our 製品. [ADAE is the 機関 for Electronic 行政 開発 http://www.adae.gouv.fr/.]
And as to 反対する-問題／発行するs.... The 反対する 問題／発行するs are always the same, "you'll have to change the way you work" and "why should I learn a new ソフトウェア ?" etc. The 証拠不十分s of Calc in 1.1.x, too, makes the 交替／補充 of Excel difficult or impossible for some departments. [Ed., 2.0 解決するs most of those 証拠不十分s.]
In 新規加入 to 存在 lead of FR, you are of course, a member of the Community 会議, OpenOffice.org's 治める／統治するing 団体／死体. What sort of 問題／発行するs are discussed there? How does your 役割 there 影響する／感情 your standing in FR?
治める／統治するing supposes 管理／経営, so 管理／経営 問題／発行するs like binary 鮮明度／定義 [what defines the OpenOffice.org 使用／適用 取り付け・設備 始める，決める?] licensing, 基金ing ... are discussed and worked there [, in CC 会合s]. I learned a lot through the discussions happening here. My 役割 is 影響する／感情d by the fact that, speaking of OOo 事業／計画（する）, I say "we" instead of "they". 本気で, it gives me a more 正確な 見通し of what developing a 製品 is like, and the reflection needed to engage the community in this 過程.
Your leadership of OpenOffice.org for the last two years has given you 価値のある insight into the 事業／計画（する）'s workings and its 未来. So: prognosticate for us. Where do you see OpenOffice.org 後継するing? Where failing? How will the 近づいている 2.0 影響する／感情 things, in your estimation?
OpenOffice.org is a 広大な／多数の／重要な community. It 利益s from having a good image outside 予定 to the work of several persons like 事業／計画（する） leads or our community 経営者／支配人. Since two years, what was really 欠如（する）ing through the 事業／計画（する）, I 指名するd "communication", is mostly 演説（する）／住所d by the 成果／努力 of all. We should stay vigilant with it as we become larger, speak with a 統一するd 発言する／表明する and remain the welcoming 事業／計画（する） we have been until now. This is to say that OOo is really 後継するing as a community.
I think that we should 押し進める for the 未来, with more and more 成果／努力s in 伸び（る）ing 核心 developers. It is is really 決定的な for our 事業／計画（する） to reach a point of balance between 使用者s and contributors.
For me, 2.0 is an 利益／興味ing challenge, it 約束s to be a more 円熟した 製品, with lot of new functionalities to answer the 使用者 needs. But it has also lot of differences with the previous 解放（する）s, so in one 手渡す we will have a better fitting with the 使用者 asks, but in another 手渡す, the differences will get them a bit lost. This is up to us to make it a success, and I'm sure the community will make it so.
You are 現在のing on 2.0 at the 近づいている 会議／協議会. What are the biggest changes? Or must we wait until the 会議／協議会 to find out?
The biggest changes are the OASIS とじ込み／提出する 判型s 採択, the Data Base 接近, the large work that have been done on 輸入する/輸出（する） filters 改善するing MS interoperability. During the 会議／協議会, you'll discover lot of nice functionalities that have been 改善するd upon or developed to 緩和する the use of the 控訴.
