Community Articles: Opinions, Interviews, 分析
2001 October 2
On Builds and Community 参加
The 統計（学） from two weeks ago are （疑いを）晴らす: over 62,000 downloads of the code, a number that 含むs both binaries and source. The other 人物／姿／数字s, which 手段 mail 名簿（に載せる）／表（にあげる） 加入者s and 参加, are 平等に 断言するing. But why? Why so many downloads? Why so much activity? Yes, the code is more usable than ever before. And, yes, the community has become large enough that any growth is geometric, meaning that we will 推定する／予想する to see big 増加するs in downloads and 参加. But these 原因（となる）s don't seem fully to explain the 影響s.
The numbers, of course, need some 解釈／通訳. Some people may be downloading more than once, for instance. But it seems 圧倒的に the 事例／患者 that OpenOffice.org is now reaching a large number of endusers. Doubtless, one （疑いを）晴らす 推論する／理由 is because OpenOffice.org is more usable now than ever before. Build 638 is solid and 機能の; it 作品--and it is 解放する／自由な. These are strong 誘導s. And, its 即座の 後継者, the 現在の download, Build 638c, has 直す／買収する，八百長をするd some bugs and is even better. What is more, and 全く unique to OpenOffice.org, Kevin Hendricks' and the Mac group have put together a Linux PPC build (for Macintoshes), which will run on Yellow Dog Linux and probably other Linuxes for the Macintosh. （警察などへの）密告，告訴（状） on where to download this build will be 利用できる on the Mirrors page.
Build 638c, which 含む／封じ込めるs much of the same code as StarOffice 6.0 Beta, needs hard 実験（する）ing beginning now, so that the next build (641) can reasonably （人命などを）奪う，主張する the status of 存在 ready for daily use. (Build 641 will likely be a more finished 見解／翻訳／版 of StarOffice 6.0.) A point of distinction: StarOffice 6.0 is Sun's 製品 that uses code taken from OpenOffice.org source. But OpenOffice.org code is not fully congruent with StarOffice; there are 重要な differences, not the least of which is that OpenOffice.org code is Open Source and therefore open by the community for 改良. (Recently, the 問題／発行する of 指名するing the 解放（する）s and 明らかにするing the 身元 of the community was raised; I 勧める readers to go to the page and review the 提案.)
So, I encourage all members to download the build and とじ込み／提出する 問題／発行するs using IssueZilla when you come across problems. Remember, that to とじ込み／提出する an 問題／発行する you must first be a 登録（する）d 使用者 of OpenOffice.org. There'll be more 告示s regarding how to send in bug 報告（する）／憶測s later on this week and the next, but 使用者s can learn now how to use IssueZilla by going to the Bugs and 問題／発行するs page.
とじ込み／提出するing 問題／発行するs will enable the 事業／計画（する）'s developers to 改善する the code; it is also a way in which all 使用者s can 参加する--and the way, やめる honestly, in which we can bring those 使用者s who 簡単に want to use the code into the OpenOffice.org community. For the number of downloads far 越えるs the number of 登録（する）d 使用者s (between four and five thousand) and mail-名簿（に載せる）／表（にあげる） 加入者s (around 3600). The 控訴 明確に 控訴，上告s to 使用者s who are not actual 関係者s in the community. This is to be 推定する／予想するd; and it is a 調印する of our so-far success, that OpenOffice.org has gone from まず第一に／本来 存在 "pre-alpha" to something 認めるd as usable by tens of thousands of people outside the 狭くする circumference of our community. But we need all those "eyeballs" (as Linus Torvalds has 述べるd the 正規の／正選手 使用者) to send in all the bugs they find and 問題／発行するs they have with the ソフトウェア. さもなければ, にもかかわらず our growing 人気 and 増加するd visibility, the code will not develop as quickly.
And--get this--OpenOffice.org has done 事実上 no marketing, 行為／行うd no expensive advertising （選挙などの）運動をするs, 雇うd no strategists to get the word out. But Microsoft has, and it is my guess that in 新規加入 to 申し込む／申し出ing a 製品 that 作品 beautifully, we are also 申し込む／申し出ing something--a 製品 and 態度 and community--that is also beautiful. Not 厳しく 怪しげな of its clientele, not burdensome. Rather an 環境 that is friendly and by and large supportive of people's ideas and work (however いつかs contentious!): a community.
So, if you have not already 登録（する）d with OpenOffice.org, please do so. We need your help in perfecting the coming build, which will not only be ready for every-day use, but may also 機能（する）／行事 as a beta for Sun's 星／主役にする Office. And if you want things 含むd in 未来 builds of OpenOffice.org, there is no better way to 表明する your 願望（する）s than to join the 事業／計画（する）s building the code.
Along these, lines, our 人気 誘発するs some evaluation of our 現在の structure and relation to the enduser. To this end, we now have a marketing 事業／計画（する） in the Whiteboard (where community-sponsored 事業／計画（する）s are 位置を示すd), and a recently created 使用者 Interface 事業／計画（する）. I 勧める members to visit the 事業／計画（する）, which was created and is managed by Oliver Specht, and to join in, if they can.
Both 事業／計画（する）s point to the 承認 の中で community members that OpenOffice.org is 円熟したing. Given that our 周年記念日 is より小数の than two weeks away, the タイミング is apt. We will be able to 発表する to the world that we have 後継するd in ways that decisively trounce any 懐疑心 about Open Source 開発 事業／計画（する）s and about the ability to build an office ソフトウェア 控訴 that doesn't just try to copy what Microsoft's Office does but rather builds something new: code and community that 作品 together
