Community Articles: Opinions, Interviews, 分析
24 July 2001周年記念日 報告（する）／憶測
Arguably the most important Open Source 会合 of the year, the Third 年次の O'Reilly Open Source 条約 began yesterday, 23 July, in San Diego, California, with the 主題 of "燃料ing the Open Source 代案／選択肢." The O'Reilly 条約 draws everyone who is anyone in the Open Source and 解放する／自由な ソフトウェア movements. The 推論する／理由 is simple: smart people go and things happen there. In fact, it was at the 1998 Freeware 首脳会議 組織するd by Tim O'Reilly (and out of which this 現在の 会議／協議会 has 発展させるd) that the very 称する，呼ぶ／期間／用語 "Open Source" was coined, by Christine Peterson, as an 代案／選択肢 to "解放する／自由な ソフトウェア" that would be friendlier to the pragmatic needs of 商売／仕事.
And it was at the O'Reilly 会議／協議会 last year that Sun 発表するd the 創造 of OpenOffice.org. At that time, the 告示 was more a 宣言 of beautiful 意向 than anything else, for OpenOffice.org was not yet a true Open Source 事業／計画（する）, as it is now. It wasn't until three months later, on October 13, 2000 (a Friday, as some have 公式文書，認めるd), that the code, all 7.6 million lines of it (if not more), was 現実に 解放（する）d to the public under a 二重の licensing 計画／陰謀, LGPL and SISSL. As 法案 Roth, Group 製品 Marketing 経営者／支配人, Sun Microsystems 述べるd at the time, "This will be programming in the large made public for the first time. This is nine times the size of Mozilla."
No other company has "解放するd" so much code, so ambitiously, and so 全く under the 幅の広い 準備／条項s of true Open Source licenses. Yes, there is Mozilla.org: But it is smaller. Apple had a year before 解放するd its OS X code, but it had no choice, as it was working with already-解放する／自由な code (BSD). And its license has never, にもかかわらず latter-day tweaking, 伸び（る）d the vaunted 尊敬（する）・点 of 解放する／自由な ソフトウェア creator, Richard M. Stallman, who 認可するd of OpenOffice.org's license.
OpenOffice.org is and remains one of the largest Open Source 事業／計画（する）s. But its importance does not only 嘘（をつく） in the often-touted size of its code base. Rather, it lies in the fact that OpenOffice.org has proven, by its continuing and growing success, the 実現可能 of 法人組織の／企業の-sponsored 事業／計画（する）s, and the real 可能性 that the most 効果的な model for large-規模 ソフトウェア 創造 and popularization is that 供給するd by Open Source.
But success in what sense? OpenOffice.org has not produced any finished 製品. Rather, it has produced, routinely and 定期的に, builds of its code. These are "snapshots" of the code as it is 存在 put together. To a greater or lesser extent, these builds, which can be thought of as "pre-alpha" and as challenges to the community, are usable by 非，不，無-technical persons--but that's incidental. To put it bluntly, OpenOffice.org is not here to produce a finished 製品. Sun Microsystems is doing that with StarOffice 6, which will have been built using code derived from OpenOffice.org. Rather, OpenOffice.org's far more ambitious goal is to create a 維持できる 過程 of code making and community building.
And, as our most 最近の 統計（学） 示す, we are 後継するing. (週刊誌 統計（学） are 地位，任命するd on the homepage.) Over 3000 加入者s to our 名簿（に載せる）／表（にあげる）s; nearly 32,000 source and binary downloads in the last week alone (not even counting those of the most 最近の build), with almost 350,000 so far; and an active and growing base of 事業／計画（する） leads 監督するing new, community-組織するd 事業／計画（する）s such as the Documentation and Groupware, to 指名する but two.
Our code, moreover, is developed by a community that （期間が）わたるs the globe and 作品 together にもかかわらず a variety of languages and cultures; the 事業／計画（する）, understood as the code and community, is, in the model of Linux, superlatively international. Indeed, OpenOffice.org community members have 熱望して taken upon themselves the 使節団 of creating 事業／計画（する）s 充てるd to 供給するing （警察などへの）密告，告訴（状） and 援助 in a developer's native language. So far, the Francophone module has been our first, 実験の module in the Native Language 開発 事業／計画（する）.
公式文書，認める: I join the community to the code because OpenOffice.org cannot be understood as one or the other. In fact, both are encompassed by our "使節団 声明," which was 共同で （手先の）技術d by many in the OpenOffice.org community:
"To create, as a community, the 主要な international office 控訴 that will run on all major 壇・綱領・公約s and 供給する 接近 to all functionality and data through open-構成要素 based APIs and an XML-based とじ込み／提出する 判型."
As is （疑いを）晴らす from the 声明, the 過程 of code making 暗黙に 伴う／関わるs community and 副／悪徳行為 versa. The point--and it is a quintessentially Open Source one--is to create ソフトウェア that people can easily use and easily 修正する for their uses, not ソフトウェア that, in pretending to cater to every whim, beds the 使用者 into a procrustean nightmare of 軍隊d choices that only 結局最後にはーなる hobbling him.
Okay, the image may be a little much. But it does go to the heart of the OpenOffice.org's difference from ソフトウェア produced by the likes of Microsoft. OpenOffice.org is a community 成果／努力; the ソフトウェア 暗黙に 答える／応じるs to and articulates community 願望（する）s and needs. Microsoft, disdains the importance of Open Source communities and shrugs off their 力／強力にする as unimportant, if not downright harmful. In contrast, it is 利益／興味d in producing essentially static and one-size fits-all 製品s that 限界 the choices of the 使用者 and, more important, 軍隊 him into thinking of the ソフトウェア as always already something he can only use, never really 修正する. And of course the ソフトウェア is fatally expensive, bloated, and very often 簡単に annoying.
Of course no code is perfect. That's not the point; rather, the point is to create a 過程 so that code can be made to fit the person, the 商売／仕事, the community: the 使用者, and not the other way around. OpenOffice.org does this. Build 633 is out there: join us in building it for everyone.
