mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
translated
This commit is contained in:
parent
698673aab7
commit
c597a83de4
@ -1,99 +0,0 @@
|
||||
[#]: subject: "A brief history of LibreOffice"
|
||||
[#]: via: "https://opensource.com/article/23/2/libreoffice-history"
|
||||
[#]: author: "Italo Vignoli https://opensource.com/users/italovignoli"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "onionstalgia"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
A brief history of LibreOffice
|
||||
======
|
||||
|
||||
In early 2009, OpenOffice.org was the main competitor to Microsoft Office in the individual office productivity suites market. The popular open source office suite's community looked forward to a November conference in Orvieto, Italy. Things were going well, and the future looked bright.
|
||||
|
||||
And then, in April of that year, Oracle announced its plans to acquire Sun Microsystems.
|
||||
|
||||
Personally, I knew it was bad news for OpenOffice.Org. Oracle had no interest in the open source suite, and I felt confident it would abandon the project. Of course, I hoped to be proved wrong at the upcoming conference. Instead, a single representative from Oracle, with no budget to speak of, arrived in Orvieto and talked vaguely about monetization and re-branding. I felt that my worst fears were confirmed, and my fellow community members agreed.
|
||||
|
||||
The community returned home from Orvieto that year and resolved to take action. The time had finally come to turn into reality what the OpenOffice.Org project had promised. We were determined to create an independent foundation to manage the project's assets and promote the development of the suite under the umbrella of the community. OpenOffice.org would no longer belong to a company but to its users and individual contributors.
|
||||
|
||||
### Building the foundation
|
||||
|
||||
At the time, the OpenOffice.org project had a presence on every continent, with language communities helping to localize and promote it. The four most important:
|
||||
|
||||
- German: The software was born in Germany, and StarDivision was based in Hamburg, so there was a natural link between the group of developers and German-speaking supporters.
|
||||
- French: The government supported the open source software.
|
||||
- Italian: The group to which I belonged.
|
||||
- Brazilian
|
||||
|
||||
At the beginning of 2010, at the initiative of the French and German language communities, the most active volunteers—together with some independent and SUSE developers—started working on a fork project. The aim was to launch an alternative project involving both the global community and the companies invested in OpenOffice.org.
|
||||
|
||||
I have over 30 years of experience working in international business and consultancy agencies. The project brought me in to manage the marketing and communication strategy.
|
||||
|
||||
In the months that followed, activity became increasingly hectic. There was a weekly teleconference meeting, as the news coming in from Star Division (the department responsible for OpenOffice.org) was increasingly negative.
|
||||
|
||||
Even with the dissolution of OpenOffice.org seemingly imminent, a conference in Budapest was confirmed by the publication of a CFP (Call for Papers). Of course, the fork project members also did nothing different from previous years. They presented their talk proposals and made travel plans.
|
||||
|
||||
### A safe place for documents
|
||||
|
||||
At the beginning of the summer, the fork was almost ready. Our group met in Budapest to gauge the situation from the OpenOffice.org side and for a first face-to-face organizational meeting.
|
||||
|
||||
The Budapest conference ran smoothly, with meetings, keynotes, and technical sessions taking place over the three-day event. Everything seemed more or less normal.
|
||||
|
||||
Everything was not normal.
|
||||
|
||||
Some attendees were a little suspicious when several leading figures failed to attend the conference's main social event, an overnight cruise on the Danube. We didn't participate in this event because we were meeting in a restaurant to discuss the final details of a new foundation. There was a lot to get right. We had to determine an announcement date and the composition of the Steering Committee that would coordinate the tasks required to bring the foundation to life.
|
||||
|
||||
### LibreOffice
|
||||
|
||||
The three weeks between the conference and the announcement of LibreOffice were hectic. I prepared the launch strategy and the text of the press release. The developers prepared the software. The application's name had just been decided a few days earlier during a teleconference (which I'd joined from Grosseto, where I was attending the Italian open source software community meeting).
|
||||
|
||||
On September 28, 2010, I distributed the press release announcing The Document Foundation and LibreOffice to a global mailing list of about 250 journalists, which I painstakingly put together using input from the public relations agencies where I worked.
|
||||
|
||||
Here is the release:
|
||||
|
||||
> The community of volunteers developing and promoting OpenOffice.Org announces an independent foundation to drive the further growth of the project. The foundation will be the cornerstone of a new ecosystem where individuals and organisations can contribute to and benefit from the availability of a truly free office suite. It will generate increased competition and choice for the benefit of customers and drive innovation in the office suite market. From now on the OpenOffice.Org community will be known as The Document Foundation.
|
||||
|
||||
We invited Oracle to become a member of the foundation and donate the brand the community had grown during the previous ten years. Pending the decision, we chose the brand LibreOffice for the software going forward.
|
||||
|
||||
Reactions to the announcement from the press were very positive. On the other hand, companies and analysts tended to be suspicious of an office suite governed by a community, an entity they never fully understood because of its flat, meritocratic organization.
|
||||
|
||||
In the two weeks following the announcement, 80 new developers joined the project, disproving the predictions of those who considered it unrealistic to launch a fork relying only on SUSE and Red Hat developers. Unsurprisingly, most of the language communities switched to LibreOffice.
|
||||
|
||||
LibreOffice is built from the source code of OpenOffice.org. The new functionalities are integrated in the source code of Go-OO and not on OOo.
|
||||
|
||||
For this reason, the first version of LibreOffice—announced on January 25, 2011—was 3.3 to maintain consistency with OpenOffice.org. This was useful for users who had migrated to the new suite since the first version. The software was still a little immature due to significant technical debt that had to be accounted for. This caused problems and instability that would largely be corrected through code cleaning and refactoring throughout the 3.x and 4.x versions. By versions 5.x and 6.x, the source code was considered stable, which allowed the user interface to be improved and the development of mobile and cloud versions.
|
||||
|
||||
In the spring of 2011, Oracle transferred the OpenOffice.org source code to the Apache Software Foundation. The project lasted for three years. The last new version was nearly a decade ago.
|
||||
|
||||
### The future is open
|
||||
|
||||
The formation process of The Document Foundation ended in early 2012, with registration by the Berlin authorities on February 17, 2012. This was a lengthy process because the founders wanted volunteer members of the project also to be members of the foundation based on contributions. This detail hadn't been foreseen for foundations under German law, so it required several revisions of statutes to comply with this condition.
|
||||
|
||||
The foundation's first two activities were the membership committee's election. This is the structure that decides on the transition from mere volunteer to member of The Document Foundation on the basis of contributions. There are five members and three deputies. Finally, there's a Board of Directors, which steers the foundation administratively and strategically, consisting of seven members and three deputies.
|
||||
|
||||
At the end of 2012, the foundation hired its first employee. This employee was Florian Effenberger, who was later promoted to executive director. Today, the team has a dozen members who take care of day-to-day activities such as coordinating projects, administration, network infrastructure management, software releases, mentoring of new developers, coordination of quality assurance, user interface evolution, and marketing and communications.
|
||||
|
||||
Right now, the foundation is looking for developers to handle tasks that do not fit the objectives of enterprise customers, such as RTL language management and accessibility. These features aren't developed by the companies in the LibreOffice ecosystem, which offer them feature development services, Level 3 support, and Long Term Support versions of the software optimized for enterprise needs.
|
||||
|
||||
More than 12 years after the announcement of LibreOffice and The Document Foundation, we can say that we have achieved our goal of developing an independent free and open source (FOSS) project. Our project is based on an extended community of individual volunteers and companies contributing according to their abilities. These participants help create the unmatched free office suite and support open standards by adopting and evolving the only true standard office document format on the market (Open Document Format, or ODF) while also ensuring excellent compatibility with the proprietary OOXML format.
|
||||
|
||||
The sustainability of this model is a day-to-day problem. There's severe competition from big tech firms. We're always searching for a balance between those who would like everything to be cost-free and those who would like each user to contribute according to their ability. No matter what, though, LibreOffice is an open source office suite, providing added value above and beyond its competition.
|
||||
|
||||
Try LibreOffice. Donate. Support it at home and work. Tell your friends about it. LibreOffice is the open source office solution that ensures you always have access to your data and control over your creativity.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/23/2/libreoffice-history
|
||||
|
||||
作者:[Italo Vignoli][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/italovignoli
|
||||
[b]: https://github.com/lkxed/
|
||||
|
@ -0,0 +1,103 @@
|
||||
[#]: subject: "A brief history of LibreOffice"
|
||||
[#]: via: "https://opensource.com/article/23/2/libreoffice-history"
|
||||
[#]: author: "Italo Vignoli https://opensource.com/users/italovignoli"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "onionstalgia"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
LibreOffice 简史
|
||||
======
|
||||
|
||||
在 2009 年初,OpenOffice.org 还是微软 Office 在个人办公生产力套件市场的主要竞争对手。这个流行的开源办公套件的社区,期待着 11 月在意大利奥尔维耶托举行的研讨会。事情进展顺利,未来看起来很光明。
|
||||
|
||||
可这之后,同年 4 月,<ruby>甲骨文公司<rt>Oracle</rt></ruby>宣布了对<ruby>太阳计算机系统公司<rt>Sun Microsystems</rt></ruby>的收购计划。
|
||||
|
||||
就个人而言,我觉得这对 OpenOffice.org 来说是个坏消息。甲骨文对开源套件没有兴趣,我料想它会放弃这个项目。当然,我更希望在研讨会上被证明是我想错了。但到最后,甲骨文只派了一名代表来到奥尔维耶托,乏善可陈,含糊其辞地谈论了盈利和品牌重塑。我和其他社区成员们都觉得,最担心的事情成真了。
|
||||
|
||||
那一年,社区成员从奥尔维耶托返程之后决定采取行动。是时候兑现 OpenOffice.org 项目的承诺了。我们决心创建一个独立的基金会来管理项目的资产,在社区的保护下促进套件的开发。OpenOffice.org 将不再隶属于哪一家公司,而是属于它的用户和个人贡献者们。
|
||||
|
||||
### 建立基金会
|
||||
|
||||
当时,OpenOffice.org 项目覆盖各个大洲,在语言社区帮助下进行本地化和推广,其中最主要的四个依次是:
|
||||
|
||||
- 德国:软件是诞生于德国的,而且 StarDivision 的总部也在汉堡,因此开发者群体和德语支持者之间沟通顺畅。
|
||||
|
||||
- 法国:政府支持开源软件。
|
||||
- 意大利:我所在的小组。
|
||||
- 巴西
|
||||
|
||||
2010 年初,在法国和德国语言社区的倡议下,最活跃的志愿者——连同一些独立开发者和 SUSE 的开发者们——着手建立了一个分支项目,旨在作为一个额外的选择,让全球社区和投资 OpenOffice.org 的企业能够同时参与进来。
|
||||
|
||||
|
||||
我在国际商业咨询机构已有超过 30 年的工作经验了。在这个项目中负责市场营销和战略沟通。
|
||||
|
||||
|
||||
随后的几个月里,活动越发忙碌。由于从 Star Division(负责 OpenOffice.org 的部门)传来的消息越来越负面,每周都得召开一次电话会议。
|
||||
|
||||
即使 OpenOffice.org 的解散似乎迫在眉睫,我们还是通过发布文章征稿的方式,确认了位于布达佩斯的研讨会仍将举办。当然,分支项目的成员在做的也和往年别无二致。他们提交了演讲提案并制定了旅行计划。
|
||||
|
||||
### 一个安全的文件存放处
|
||||
|
||||
夏初,分支项目几乎要完成了。我们的小组在布达佩斯开会评估 OpenOffice.org 方面的境况,并召开了第一次面对面的组织会议。
|
||||
|
||||
布达佩斯的研讨会进行得很顺利,为期三天日程中举行了会议、主题演讲和技术研讨。一切似乎还算平常。
|
||||
|
||||
可其实并不平常。
|
||||
|
||||
当几位领头人没去参加会议的主要社交活动——多瑙河上过夜巡游的时候,一些与会者开始有些疑虑了。其实我们没参加这次活动,是因为我们在餐厅开会敲定新基金会的最终细节,有太多事情要确保万无一失。我们必须定下公告日期,并且,为了协调基金会落地的各项任务,需要确定指导委员会的人员组成。
|
||||
|
||||
### LibreOffice
|
||||
|
||||
这次会议和 LibreOffice 发布之间间隔三周,我们紧锣密鼓地准备。我拟好了发布策略和新闻稿,开发者们为软件做准备。应用的名字甚至是在发布的前几天的一次电话会议上敲定的,那时我在格罗塞托,正在参加意大利开源软件社区会议。
|
||||
|
||||
2010 年 9 月 28 日,我把宣布「<ruby>文档基金会<rt>The Document Foundation</rt></ruby>」和 LibreOffice 的新闻稿分发到一个包含全球约 250 名记者的发信列表中,这列表可是我根据供职过的公共关系机构的来信,花了很大力气整理的。
|
||||
|
||||
发布文档是这样的:
|
||||
|
||||
> 开发和推广 OpenOffice.org 的志愿者社区宣布将成立一个独立的基金会,推动项目的进一步发展。基金会将成为一个新的生态系统的基石,在这里,个人和组织都可以为一个真正免费的办公套件做出贡献,并从中受益。从用户的利益出发,这将带来更多的竞争和选择,并推动办公套件市场的创新。从现在开始,OpenOffice.org 社区将被称为「<ruby>文档基金会<rt>The Document Foundation</rt></ruby>」。
|
||||
>
|
||||
|
||||
我们邀请过 Oracle 成为基金会的成员并捐赠社区在过去十年中发展起来的品牌。而在他们做出决定之前,我们选择了 LibreOffice 作为即将到来的软件的品牌。
|
||||
|
||||
媒体界对公告的反应非常积极。但另一方面,企业和分析师则倾向于对由社区管理的办公套件表示质疑,这是他们从未完全理解的实体,因为这个组织很扁平、任人唯贤。
|
||||
|
||||
公告发布后的两周内,就有 80 位新开发者加入这个项目,推翻了那些认为"仅凭 SUSE 和 Red Hat 的开发者来启动分支项目并不现实"的预测。不出所料,大多数语言社区都转向了 LibreOffice。
|
||||
|
||||
LibreOffice 是基于 OpenOffice.org 的源代码构建的。但新的功能被集成在 <ruby>Go-OO<rt>Go-Open Office</rt></ruby> 的源代码中,而不是在 OpenOffice.org 上了。
|
||||
|
||||
出于这个原因,LibreOffice 的第一个版本(于 2011 年 1 月 25 日发布)为 3.3,以保持与 OpenOffice.org 的一致性。我们认为这对于从第一个版本迁移到新套件的用户很有帮助。由于还有必须解决的明显技术欠缺,软件目前仍不成熟,这导致的问题和不稳定预计将很大程度上通过 3.x 和 4.x 版本的代码清理和重构得到纠正。到 5.x 和 6.x 版本,我们认为源代码将是稳定的,并有条件改进用户界面以及开发移动和云版本。
|
||||
|
||||
2011 年春天,甲骨文将 OpenOffice.org 源代码转移到 Apache 软件基金会。项目仅持续了三年,上一个新版本已经是将近十年前的事了。
|
||||
|
||||
### 未来是开放的
|
||||
|
||||
文档基金会的组建过程于 2012 年初结束,并于 2012 年 2 月 17 日在柏林有关部门完成注册。因为创始人希望该项目的志愿者成员们也可以根据贡献成为基金会成员,这让注册过程十分漫长。德国的法规并未考虑到基金会的这一细节,因此需要对法规进行多次修订才能满足现有状况。
|
||||
|
||||
基金会成立之初的前两项活动都是委员会成员的选举。这是从单纯的志愿者过渡到基于贡献的文档基金会成员所必经的规程。委员五人,副委员三人。最后,负责在行政和战略方面领导基金会的董事会,由七名成员和三名副手组成。
|
||||
|
||||
2012 年底,基金会聘请了第一位雇员,Florian Effenberger,在后来他被提升为执行董事。今天,这个团队有十几个成员,他们负责日常活动,例如协调项目、行政管理、网络基础设施管理、软件发布、指导新的开发人员、协调质量保证、用户界面的演进、以及营销和沟通。
|
||||
|
||||
目前,基金会正在寻找开发人员满足企业客户需求,例如 RTL 语言管理和辅助功能。这些功能不是由那些,能提供功能开发服务、3 级支持和针对企业需求优化的软件长期支持版本,的 LibreOffice 生态系统中的公司开发的。
|
||||
|
||||
在 LibreOffice 和文档基金会宣布成立超过 12 年后,我们可以说,我们已经实现了开发独立的「<ruby>自由和开源软件<rt>FOSS</rt></ruby>」的项目目标。我们的项目基于一个由个人志愿者和公司量力而行做出贡献的扩展社区。参与者们帮助创建了无与伦比的免费办公套件,并通过采用和发展现有市场上唯一真正的<ruby>标准办公文档格式<rt>ODF</rt></ruby>来支持开放标准。同时,套件也确保了与专有的 OOXML 格式的出色兼容性。
|
||||
|
||||
这种模式的可持续性是一个日常问题。身处于与大型科技公司的激烈竞争下,我们一直在尝试,试图在“希望一切都免费”,和“希望每个用户都能力所能及做出贡献”之间达成一种平衡。不过无论如何,LibreOffice 都会是开源的办公套件,这提供了竞争之上的额外价值。
|
||||
|
||||
尝试LibreOffice,捐赠,不论是工作还是业余,支持它,向你的朋友介绍它。LibreOffice 是一个开源的办公解决方案,它确保你总是能够访问你的数据,并掌控你的创造力。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/23/2/libreoffice-history
|
||||
|
||||
作者:[Italo Vignoli][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[onionstalgia](https://github.com/onionstalgia)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/italovignoli
|
||||
[b]: https://github.com/lkxed/
|
||||
|
Loading…
Reference in New Issue
Block a user