Misplaced Pages

#710289

88-424: The last version was 2022.7, released 2 September 2023. NeoOffice is no longer active as of December 2023. The project recommends users move to LibreOffice, to which Patrick Luby of NeoOffice is a contributor. Versions of OpenOffice.org for Mac prior to 3.0 did not have a native Mac OS X interface; they required that either X11.app or XDarwin be installed. NeoOffice was the first OpenOffice.org fork to offer

176-512: A database management application (Base). Its default file format was the OpenDocument Format (ODF), an ISO / IEC standard, which originated with OpenOffice.org. It could also read a wide variety of other file formats, with particular attention to those from Microsoft Office. OpenOffice.org was primarily developed for Linux , Microsoft Windows and Solaris , and later for OS X , with ports to other operating systems . It

264-456: A proprietary office suite developed by German company Star Division from 1985 on. In August 1999, Star Division was acquired by Sun Microsystems for US$ 59.5 million, as it was supposedly cheaper than licensing Microsoft Office for 42,000 staff. On 19 July 2000 at OSCON , Sun Microsystems announced it would make the source code of StarOffice available for download with the intention of building an open-source development community around

352-406: A Pathways to Enable Open-Source Ecosystems (POSE) program to support open source innovation. The adoption of open-source software by industry is increasing over time. OSS is popular in several industries such as telecommunications , aerospace , healthcare , and media & entertainment due to the benefits it provides. Adoption of OSS is more likely in larger organizations and is dependent on

440-544: A bug needs to be fixed in their project. This is established by communicating with the OSS community through avenues such as bug reporting and tracking or mailing lists and project pages. Next, OSS developers select or are assigned to a task and identify a solution. Because there are often many different possible routes for solutions in OSS, the best solution must be chosen with careful consideration and sometimes even peer feedback . The developer then begins to develop and commit

528-533: A commercial distribution model via the Mac App Store . As of 2016, the source code is still available for free, but the software package was only available with the purchase of a commercial license. This has changed in 2022 as the code and all commits are released on GitHub . Moreover, the whole application is free of charge. Currently the NeoOffice website has the tag line, "An old fork of LibreOffice", and

616-517: A copy of the license is provided to recipients with the code. One important legal precedent for open-source software was created in 2008, when the Jacobson v Katzer case enforced terms of the Artistic license , including attribution and identification of modifications. The ruling of this case cemented enforcement under copyright law when the conditions of the license were not followed. Because of

704-445: A more usable database; digital signatures; and improved usability . It would also be the first version to default to OpenDocument. Sun released the first beta version on 4 March 2005. On 2 September 2005, Sun announced that it was retiring SISSL to reduce license proliferation , though some press analysts felt it was so that IBM could not reuse OpenOffice.org code without contributing back. Versions after 2.0 beta 2 would use only

792-557: A native Mac OS X experience, with easier installation, better integration into the Mac OS X interface (pull-down menus at the top of the screen and familiar keyboard shortcuts, for example), use of Mac OS X's fonts and printing services without additional configuration, and integration with the Mac OS X clipboard and drag-and-drop functions. Subsequently, both LibreOffice and Apache OpenOffice followed NeoOffice's lead and implemented similarly native Mac OS X interfaces. NeoOffice began as

880-454: A new bug. Early releases : The first version of the software should be released as early as possible so as to increase one's chances of finding co-developers early. Frequent integration: Code changes should be integrated (merged into a shared code base) as often as possible so as to avoid the overhead of fixing a large number of bugs at the end of the project life cycle. Some open-source projects have nightly builds where integration

968-412: A project to investigate methods of creating a native port of OpenOffice.org to Mac OS X. The project now called NeoOffice was originally dubbed "NeoOffice/J", reflecting its use of Mac OS X's Java integration to enable a native application. A related project was NeoOffice/C, which was a simultaneous effort to develop a version using Apple's Cocoa APIs. But NeoOffice/C proved very difficult to implement and

SECTION 10

#1732780223711

1056-508: A public good as it is available to everyone and does not decrease in value for others when downloaded by one person. Open source software is unique in that it becomes more valuable as it is used and contributed to, instead of diminishing the resource. This is explained by concepts such as investment in reputation and network effects . The economic model of open-source software can be explained as developers contribute work to projects, creating public benefits. Developers choose projects based on

1144-599: A significant amount of time." The OpenOffice.org developers said that "a proposal to work together has been made, and NeoOffice developers refused". The NeoOffice developers subsequently expressed support for LibreOffice and the launch of The Document Foundation . OpenOffice.org OpenOffice.org ( OOo ), commonly known as OpenOffice , is a discontinued open-source office suite . Active successor projects include LibreOffice (the most actively developed ) and Collabora Online , with Apache OpenOffice being considered mostly dormant since at least 2015. OpenOffice

1232-422: A victory for OSS supporters. In open-source communities, instead of owning the software produced, the producer owns the development of the evolving software. In this way, the future of the software is open, making ownership or intellectual property difficult within OSS. Licensing and branding can prevent others from stealing it, preserving its status as a public good . Open source software can be considered

1320-523: Is $ 8.8 trillion, as firms would need to spend 3.5 times the amount they currently do without the use of open source software. Open-source code can be used for studying and allows capable end users to adapt software to their personal needs in a similar way user scripts and custom style sheets allow for web sites, and eventually publish the modification as a fork for users with similar preferences, and directly submit possible improvements as pull requests . The Open Source Initiative 's (OSI) definition

1408-710: Is a trademark held by Open Office Automatisering in Benelux since 1999, OpenOffice.org was its formal name. Due to a similar trademark issue (a Rio de Janeiro company that owned that trademark in Brazil), the Brazilian Portuguese version of the suite was distributed under the name BrOffice.org from 2004, with BrOffice.Org being the name of the associated local nonprofit from 2006. (BrOffice.org moved to LibreOffice in December 2010. ) OpenOffice.org 1.0

1496-565: Is a broad software license that makes source code available to the general public with relaxed or non-existent restrictions on the use and modification of the code. It is an explicit "feature" of open source that it puts very few restrictions on the use or distribution by any organization or user, in order to enable the rapid evolution of the software. According to Feller et al. (2005), the terms "free software" and "open-source software" should be applied to any "software products distributed under terms that allow users" to use, modify, and redistribute

1584-404: Is a good or service, what can be considered a modification, governance through contract vs license, ownership and right of use. While there have been developments on these issues, they often lead to even more questions. The existence of these uncertainties in regulation has a negative impact on industries involved in technologies as a whole. Within the legal history of software as a whole, there

1672-417: Is a prominent example of open collaboration , meaning any capable user is able to participate online in development, making the number of possible contributors indefinite. The ability to examine the code facilitates public trust in the software. Open-source software development can bring in diverse perspectives beyond those of a single company. A 2024 estimate of the value of open-source software to firms

1760-556: Is absolutely another terrific way that individuals and organizations choose to contribute to open source projects. Groups like Open Collective provide a means for individuals to contribute monthly to supporting their favorite projects. Organizations like the Sovereign Tech Fund is able to contribute to millions to supporting the tools the German Government uses. The National Science Foundation established

1848-544: Is done automatically . Several versions: There should be at least two versions of the software. There should be a buggier version with more features and a more stable version with fewer features. The buggy version (also called the development version) is for users who want the immediate use of the latest features and are willing to accept the risk of using code that is not yet thoroughly tested. The users can then act as co-developers, reporting bugs and providing bug fixes. High modularization: The general structure of

SECTION 20

#1732780223711

1936-404: Is innovative since open-source programs are the product of collaboration among a large number of different programmers. The mix of divergent perspectives, corporate objectives, and personal goals speeds up innovation. Moreover, free software can be developed in accordance with purely technical requirements. It does not require thinking about commercial pressure that often degrades the quality of

2024-560: Is legal variety in this definition. Some jurisdictions attempt to expand or reduce this conceptualization for their own purposes. For example, The European Court of Justice defines a computer program as not including the functionality of a program, the programing language , or the format of data files. By limiting protections of the different aspects of software, the law favors an open-source approach to software use. The US especially has an open approach to software, with most open-source licenses originating there. However, this has increased

2112-761: Is no known virus "in the wild". As of October 2011, Secunia reported no known unpatched security flaws for the software. A vulnerability in the inherited OpenOffice.org codebase was found and fixed in LibreOffice in October 2011 and Apache OpenOffice in May 2012. The preview, Milestone 638c, was released October 2001. OpenOffice.org 1.0 was released under both the LGPL and the SISSL for Windows, Linux and Solaris on 1 May 2002. The version for Mac OS X (with X11 interface)

2200-658: Is recognized by several governments internationally as the standard or de facto definition. OSI uses The Open Source Definition to determine whether it considers a software license open source. The definition was based on the Debian Free Software Guidelines , written and adapted primarily by Perens . Perens did not base his writing on the "four freedoms" from the Free Software Foundation (FSF), which were only widely available later. Under Perens' definition, open source

2288-446: Is reserved for obvious cases only, for other cases refer to Misplaced Pages:Copyright problems . Open-source software ( OSS ) is computer software that is released under a license in which the copyright holder grants users the rights to use, study, change, and distribute the software and its source code to anyone and for any purpose. Open-source software may be developed in a collaborative, public manner. Open-source software

2376-468: Is theoretically challenging in economic models, it is explainable as a sustainable social activity that requires resources. These resources include time, money, technology and contributions. Many developers have used technology funded by organizations such as universities and governments, though these same organizations benefit from the work done by OSS. As OSS grows, hybrid systems containing OSS and proprietary systems are becoming more common. Throughout

2464-859: The Apache License , at the suggestion of IBM (to whom Oracle had contractual obligations concerning the code), as IBM did not want the code put under a copyleft license. This code drop formed the basis for the Apache OpenOffice project. During Sun's sponsorship, the OpenOffice.org project was governed by the Community Council , comprising OpenOffice.org community members. The Community Council suggested project goals and coordinated with producers of derivatives on long-term development planning issues. Both Sun and Oracle are claimed to have made decisions without consulting

2552-551: The GNU General Public License and had released a free software Java, OpenJDK , by May 2007. In 2006, Lt. Col. Eric Filiol of the Laboratoire de Virologie et de Cryptologie de l'ESAT demonstrated security weaknesses, in particular within macros. In 2006, Kaspersky Lab demonstrated a proof of concept virus, "Stardust", for OpenOffice.org. This showed OpenOffice.org viruses are possible, but there

2640-629: The OpenDocument file format, although this can be changed by the user. The OpenDocument file format is an XML file format standardized by OASIS ( Organisation for the Advancement of Structured Information Standards ). Sun first released OpenOffice.org under both the LGPL and SISSL , later under only the LGPL, with a requirement for copyright assignment for any contributions to the main code base, which allowed Sun to create proprietary versions of

2728-721: The SPARC version of Solaris. The latest versions of OpenOffice.org on other operating systems were: OpenOffice.org included OpenSymbol , DejaVu , the Liberation fonts (from 2.4) and the Gentium fonts (from 3.2). Versions up to 2.3 included the Bitstream Vera fonts. OpenOffice.org also used the default fonts of the running operating system. Fontwork is a feature that allows users to create stylized text with special effects differing from ordinary text with

NeoOffice - Misplaced Pages Continue

2816-889: The distributed version control system (DVCS) are examples of tools, often open source, that help manage the source code files and the changes to those files for a software project in order to foster collaboration. CVCS are centralized with a central repository while DVCS are decentralized and have a local repository for every user. concurrent versions system (CVS) and later Subversion (SVN) and Git are examples of CVCS. The repositories are hosted and published on source-code-hosting facilities such as GitHub . Open-source projects use utilities such as issue trackers to organize open-source software development. Commonly used bug trackers include Bugzilla and Redmine . Tools such as mailing lists and IRC provide means of coordination and discussion of bugs among developers. Project web pages, wiki pages, roadmap lists and newsgroups allow for

2904-462: The Bazaar , open-source influential contributor Eric S. Raymond suggests a model for developing OSS known as the bazaar model. Raymond likens the development of software by traditional methodologies to building a cathedral, with careful isolated work by individuals or small groups. He suggests that all software should be developed using the bazaar style, with differing agendas and approaches. In

2992-669: The Council or in contravention to the council's recommendations, leading to the majority of outside developers leaving for LibreOffice. Oracle demanded in October 2010 that all Council members involved with the Document Foundation step down, leaving the Community Council composed only of Oracle employees. The project and software were informally referred to as OpenOffice since the Sun release, but since this term

3080-426: The LGPL. On 20 October 2005, OpenOffice.org 2.0 was released. 2.0.1 was released eight weeks later, fixing minor bugs and introducing new features. As of the 2.0.3 release, OpenOffice.org changed its release cycle from 18 months to releasing updates every three months. The OpenOffice.org 2 series attracted considerable press attention. A PC Pro review awarded it 6 stars out of 6 and stated: "Our pick of

3168-479: The ODF 1.0 file format; versions 2.3.1–2.4.3 default to ODF 1.1; versions 3.0 onward default to ODF 1.2. OpenOffice.org 1 used OpenOffice.org XML as its native format. This was contributed to OASIS and OpenDocument was developed from it. OpenOffice.org also claimed support for the following formats: OpenOffice.org converted all external formats to and from an internal XML representation. The OpenOffice.org API

3256-641: The Public Interest . Within Europe some notable organizations are Free Software Foundation Europe , open-source projects EU (OSP) and OpenForum Europe (OFE). One Australian organization is Linux Australia while Asia has Open source Asia and FOSSAsia . Free and open source software for Africa (FOSSFA) and OpenAfrica are African organizations and Central and South Asia has such organizations as FLISOL and GRUP de usuarios de software libre Peru . Outside of these, many more organizations dedicated to

3344-582: The United States has focused on national security in regard to open-source software implementation due to the perceived threat of the increase of open-source software activity in countries like China and Russia, with the Department of Defense considering multiple criteria for using OSS. These criteria include: if it comes from and is maintained by trusted sources, whether it will continue to be maintained, if there are dependencies on sub-components in

3432-582: The added features of gradient colour fills, shaping, letter height, and character spacing. It is similar to WordArt used by Microsoft Word. When OpenOffice.org saved documents in Microsoft Office file format, all Fontwork was converted into WordArt. From version 2.0.4, OpenOffice.org supported third-party extensions. As of April 2011, the OpenOffice Extension Repository listed more than 650 extensions. Another list

3520-473: The advancement of open-source software exist. FOSS products are generally licensed under two types of licenses: permissive licensing and copyleft licensing . Both of these types of licenses are different than proprietary licensing in that they can allow more users access to the software and allow for the creation of derivative works as specified by the terms of the specific license, as each license has its own rules. Permissive licenses allow recipients of

3608-688: The application was highly unstable, so the project was set aside in favor of the more promising NeoOffice/J. The "/J" suffix was dropped with version 1.2, since there was no longer another variety of NeoOffice from which to distinguish it. Many of these releases were preceded by a version that only Early Access Members could download; these versions were released about a month before the official release date. All versions from NeoOffice 3.1.1 to NeoOffice 2015 were based on OpenOffice.org 3.1.1, though latter versions included stability fixes from LibreOffice and Apache OpenOffice. NeoOffice 2017 and later versions are fully based on LibreOffice. In 2013, NeoOffice moved to

NeoOffice - Misplaced Pages Continue

3696-402: The bazaar model should exhibit the following patterns: Users should be treated as co-developers: The users are treated like co-developers and so they should have access to the source code of the software. Furthermore, users are encouraged to submit additions to the software, code fixes for the software, bug reports , documentation, etc. Having more co-developers increases the rate at which

3784-429: The beta, was released on 15 December 2010, as was the single release of Oracle Cloud Office (a proprietary product from an unrelated codebase). A beta version of OpenOffice.org 3.4 was released on 12 April 2011, including new SVG import, improved ODF 1.2 support, and spreadsheet functionality. Before the final version of OpenOffice.org 3.4 could be released, Oracle cancelled its sponsorship of development and fired

3872-414: The code. The code is then tested and reviewed by peers. Developers can edit and evolve their code through feedback from continuous integration . Once the leadership and community are satisfied with the whole project, it can be partially released and user instruction can be documented. If the project is ready to be released, it is frozen, with only serious bug fixes or security repairs occurring. Finally,

3960-427: The company's IT usage, operating efficiencies, and the productivity of employees. Industries are likely to use OSS due to back-office functionality, sales support, research and development, software features, quick deployment, portability across platforms and avoidance of commercial license management. Additionally, lower cost for hardware and ownership are also important benefits. Organizations that contribute to

4048-477: The development and expansions of free and open-source software movements exist all over the world. These organizations are dedicated to goals such as teaching and spreading technology. As listed by a former vice president of the Open Source Initiative , some American organizations include the Free Software Foundation , Software Freedom Conservancy , the Open Source Initiative and Software in

4136-523: The different binary formats for each application that had been usual until then. Sun submitted the format to the Organization for the Advancement of Structured Information Standards (OASIS) in 2002 and it was adapted to form the OpenDocument standard in 2005, which was ratified as ISO 26300 in 2006. It was made OpenOffice.org's native format from version 2 on. Many governments and other organisations adopted OpenDocument , particularly given there

4224-461: The distribution of project information that focuses on end users. The basic roles OSS participants can fall into multiple categories, beginning with leadership at the center of the project who have control over its execution. Next are the core contributors with a great deal of experience and authority in the project who may guide the other contributors. Non-core contributors have less experience and authority, but regularly contribute and are vital to

4312-545: The document integrity check determined if an ODF document conformed to the ODF specification and offered a repair if necessary. Calc and Writer both reduced "cold start" time by 46% compared to version 3.0. 3.2.1 was the first Oracle release. Version 3.3, the last Oracle version, was released in January 2011. New features include an updated print form, a FindBar and interface improvements for Impress. The commercial version, Oracle Open Office 3.3 (StarOffice renamed), based on

4400-601: The focus on patent rights within these licenses, which has seen backlash from the OSS community, who prefer other forms of IP protection. Another issue includes technological protection measures (TPM) and digital rights management (DRM) techniques which were internationally legally recognized and protected in the 1996 World Intellectual Property Organization (WIPO) Treaty . Open source software proponents disliked these technologies as they constrained end-users potentially beyond copyright law. Europe responded to such complaints by putting TPM under legal controls, representing

4488-671: The installation of X11.app or XDarwin (though the NeoOffice port supplied a native interface). Versions since 3.0 ran natively using Apple's Aqua GUI . Although originally written in C++, OpenOffice.org became increasingly reliant on the Java Runtime Environment, even including a bundled JVM . OpenOffice.org was criticized by the Free Software Foundation for its increasing dependency on Java, which

SECTION 50

#1732780223711

4576-477: The low-cost office suites has had a much-needed overhaul, and now battles Microsoft in terms of features, not just price." Federal Computer Week listed OpenOffice.org as one of the "5 stars of open-source products", noting in particular the importance of OpenDocument. Computerworld reported that for large government departments, migration to OpenOffice.org 2.0 cost one tenth of the price of upgrading to Microsoft Office 2007 . On 13 October 2008, version 3.0

4664-427: The majority of outside OpenOffice.org developers left the project, due to concerns over Sun and then Oracle's management of the project and Oracle's handling of its open source portfolio in general, to form The Document Foundation (TDF). TDF released the fork LibreOffice in January 2011, which most Linux distributions soon moved to. In April 2011, Oracle stopped development of OpenOffice.org and fired

4752-480: The many benefits provided, a huge issue to be considered is cybersecurity . While accidental vulnerabilities are possible, so are attacks by outside agents. Because of these fears, governmental interest in contributing to the governance of software has become more prominent. However, these are the broad strokes of the issue, with each country having their own specific politicized interactions with open-source software and their goals for its implementation. For example,

4840-560: The mid 2000s, more and more tech companies have begun to use OSS. For example, Dell's move of selling computers with GNU/Linux already installed. Microsoft itself has launched a Linux-based operating system despite previous animosity with the OSS movement. Despite these developments, these companies tend to only use OSS for certain purposes, leading to worries that OSS is being taken advantage of by corporations and not given anything in return. While many governments are interested in implementing and promoting open-source software due to

4928-541: The notice: "The NeoOffice project is no longer active. As a replacement, you may want to try LibreOffice". Listed here, in the order of appearance in the Save As dialogue box, are the file formats supported for saving documents in NeoOffice 3.1.2. In cases where NeoOffice is used to edit a document originally in a Microsoft format, NeoOffice can save to that format without loss of formatting. (*Pre-chosen save default format.) By default, NeoOffice loads and saves files in

5016-508: The number of people employed in the IT sector. OSS can be highly reliable when it has thousands of independent programmers testing and fixing bugs of the software. Open source is not dependent on the company or author that originally created it. Even if the company fails, the code continues to exist and be developed by its users. OSS is flexible because modular systems allow programmers to build custom interfaces, or add new abilities to it and it

5104-435: The perceived benefits or costs, such as improved reputation or value of the project. The motivations of developers can come from many different places and reasons, but the important takeaway is that money is not the only or even most important incentivization . Because economic theory mainly focuses on the consumption of scarce resources, the OSS dynamic can be hard to understand. In OSS, producers become consumers by reaping

5192-404: The potential to quicken innovation and create of social value. In France for instance, a policy that incentivized government to favor free open-source software increased to nearly 600,000 OSS contributions per year, generating social value by increasing the quantity and quality of open-source software. This policy also led to an estimated increase of up to 18% of tech startups and a 14% increase in

5280-574: The project is fully released and only changed through minor bug fixes. Open source implementation of a standard can increase adoption of that standard. This creates developer loyalty as developers feel empowered and have a sense of ownership of the end product. Moreover, lower costs of marketing and logistical services are needed for OSS. OSS can be a tool to promote a company's image, including its commercial products. The OSS development approach has helped produce reliable, high quality software quickly and inexpensively. Open source development offers

5368-759: The project's development. New contributors are the least experienced but with mentorship and guidance can become regular contributors. Some possible ways of contributing to open-source software include such roles as programming , user interface design and testing, web design , bug triage , accessibility design and testing, UX design , code testing, and security review and testing. However, there are several ways of contributing to OSS projects even without coding skills. For example, some less technical ways of participating are documentation writing and editing, translation , project management , event organization and coordination, marketing, release management, community management, and public relations and outreach. Funding

SECTION 60

#1732780223711

5456-512: The remaining Star Division development team. Open-source software This is an accepted version of this page Note to admins : In case of doubt, remove this template and post a message asking for review at WT:CP .   With this script , go to the history with auto-selected revisions . Note to the requestor : Make sure the page has already been reverted to a non-infringing revision or that infringing text has been removed or replaced before submitting this request. This template

5544-487: The remaining Star Division development team. Its reasons for doing so were not disclosed; some speculate that it was due to the loss of mindshare with much of the community moving to LibreOffice while others suggest it was a commercial decision. In June 2011, Oracle contributed the trademarks to the Apache Software Foundation . It also contributed Oracle-owned code to Apache for relicensing under

5632-431: The rewards of contributing to a project. For example, a developer becomes well regarded by their peers for a successful contribution to an OSS project. The social benefits and interactions of OSS are difficult to account for in economic models as well. Furthermore, the innovation of technology creates constantly changing value discussions and outlooks, making economic model unable to predict social behavior. Although OSS

5720-496: The same license while weak copyleft licenses require the use of the same license only under certain conditions. Examples of this type of license include the GNU family of licenses , and the MPL and EPL licenses. The similarities between these two categories of licensing include that they provide a broad grant of copyright rights, require that recipients preserve copyright notices, and that

5808-500: The similarity of the Artistic license to other open-source software licenses, the ruling created a precedent that applied widely. Examples of free-software license / open-source licenses include Apache licenses , BSD licenses , GNU General Public Licenses , GNU Lesser General Public License , MIT License , Eclipse Public License and Mozilla Public License . Several gray areas exist within software regulation that have great impact on open-source software, such as if software

5896-488: The software "in any manner they see fit, without requiring that they pay the author(s) of the software a royalty or fee for engaging in the listed activities." Despite initially accepting it, Richard Stallman of the FSF now flatly opposes the term "Open Source" being applied to what they refer to as "free software". Although he agrees that the two terms describe "almost the same category of software", Stallman considers equating

5984-474: The software (notably StarOffice ). NeoOffice chose not to assign its code to Sun, which prevented Sun from using NeoOffice code in official OpenOffice.org versions. There were initially some attempts to resolve the licensing differences and foster more direct cooperation and code-sharing between the NeoOffice and OpenOffice.org developers. However, the NeoOffice developers said that they preferred to work separately from OpenOffice.org because "coordination requires

6072-404: The software and of providing a free and open alternative to Microsoft Office. The new project was known as OpenOffice.org, and the code was released as open source on 13 October 2000. The first public preview release was Milestone Build 638c, released in October 2001 (which quickly achieved 1 million downloads ); the final release of OpenOffice.org 1.0 was on 1 May 2002. OpenOffice.org became

6160-401: The software evolves. Linus's law states that given enough eyeballs all bugs are shallow. This means that if many users view the source code, they will eventually find all bugs and suggest how to fix them. Some users have advanced programming skills, and furthermore, each user's machine provides an additional testing environment. This new testing environment offers the ability to find and fix

6248-484: The software should be modular allowing for parallel development on independent components. Dynamic decision-making structure: There is a need for a decision-making structure, whether formal or informal, that makes strategic decisions depending on changing user requirements and other factors. Compare with extreme programming . The process of Open source development begins with a requirements elicitation where developers consider if they should add new features or if

6336-456: The software to implement the author's copyright rights without having to use the same license for distribution. Examples of this type of license include the BSD , MIT , and Apache licenses . Copyleft licenses are different in that they require recipients to use the same license for at least some parts of the distribution of their works. Strong copyleft licenses require all derivative works to use

6424-425: The software. Commercial pressures make traditional software developers pay more attention to customers' requirements than to security requirements, since such features are somewhat invisible to the customer. In open-source software development, tools are used to support the development of the product and the development process itself. Version control systems such as Centralized Version control system (CVCS) and

6512-408: The standard office suite on many Linux distros and spawned many derivative versions. It quickly became noteworthy competition to Microsoft Office, achieving 14% penetration in the large enterprise market by 2004. The OpenOffice.org XML file format – XML in a ZIP archive, easily machine-processable – was intended by Sun to become a standard interchange format for office documents, to replace

6600-597: The terms incorrect and misleading. Stallman also opposes the professed pragmatism of the Open Source Initiative , as he fears that the free software ideals of freedom and community are threatened by compromising on the FSF's idealistic standards for software freedom. The FSF considers free software to be a subset of open-source software, and Richard Stallman explained that DRM software, for example, can be developed as open source, despite that it does not give its users freedom (it restricts them), and thus does not qualify as free software. In his 1997 essay The Cathedral and

6688-514: The traditional model of development, which he called the cathedral model, development takes place in a centralized way. Roles are clearly defined. Roles include people dedicated to designing (the architects), people responsible for managing the project, and people responsible for implementation. Traditional software engineering follows the cathedral model. The bazaar model, however, is different. In this model, roles are not clearly defined. Some proposed characteristics of software developed using

6776-470: Was a free implementation of it readily available. Development of OpenOffice.org was sponsored primarily by Sun Microsystems, which used the code as the basis for subsequent versions of StarOffice. Developers who wished to contribute code were required to sign a Contributor Agreement granting joint ownership of any contributions to Sun (and then Oracle), in support of the StarOffice business model. This

6864-475: Was an open-sourced version of the earlier StarOffice , which Sun Microsystems acquired in 1999 for internal use. Sun open-sourced the OpenOffice suite in July 2000 as a competitor to Microsoft Office , releasing version 1.0 on 1 May 2002. OpenOffice included a word processor (Writer), a spreadsheet (Calc), a presentation application (Impress), a drawing application (Draw), a formula editor (Math), and

6952-566: Was based on a component technology known as Universal Network Objects (UNO). It consisted of a wide range of interfaces defined in a CORBA -like interface description language . OpenOffice.org 1.0 was criticized for not having the look and feel of applications developed natively for the platforms on which it runs. Starting with version 2.0, OpenOffice.org used native widget toolkit , icons, and font-rendering libraries on GNOME , KDE and Windows. The issue had been particularly pronounced on Mac OS X. Early versions of OpenOffice.org required

7040-528: Was controversial for many years. An alternative Public Documentation Licence (PDL) was also offered for documentation not intended for inclusion or integration into the project code base. After acquiring Sun in January 2010, Oracle Corporation continued developing OpenOffice.org and StarOffice, which it renamed Oracle Open Office, though with a reduction in assigned developers. Oracle's lack of activity on or visible commitment to OpenOffice.org had also been noted by industry observers. In September 2010,

7128-702: Was distributed under the GNU Lesser General Public License version 3 (LGPL); early versions were also available under the Sun Industry Standards Source License (SISSL). In 2011, Oracle Corporation , the then-owner of Sun, announced that it would no longer offer a commercial version of the suite and donated the project to the Apache Foundation . Apache renamed the software Apache OpenOffice . OpenOffice.org originated as StarOffice ,

7216-464: Was frequently requested. The OpenOffice.org Groupware project, intended to replace Outlook and Microsoft Exchange Server , spun off in 2003 as OpenGroupware.org, which is now SOGo . The project considered bundling Mozilla Thunderbird and Mozilla Lightning for OpenOffice.org 3.0. The last version, 3.4 Beta 1, was available for IA-32 versions of Windows 2000 Service Pack 2 or later, Linux (IA-32 and x64), Solaris and OS X 10.4 or later, and

7304-506: Was launched under the following mission statement : The mission of OpenOffice.org is to create, as a community, the leading international office suite that will run on all major platforms and provide access to all functionality and data through open-component based APIs and an XML-based file format. The suite contained no personal information manager , email client or calendar application analogous to Microsoft Outlook , despite one having been present in StarOffice 5.2. Such functionality

7392-672: Was maintained by the Free Software Foundation . OpenOffice.org included OpenOffice Basic, a programming language similar to Microsoft Visual Basic for Applications (VBA). OpenOffice Basic was available in Writer, Calc and Base. OpenOffice.org also had some Microsoft VBA macro support. OpenOffice.org could interact with databases (local or remote) using ODBC ( Open Database Connectivity ), JDBC ( Java Database Connectivity ) or SDBC (StarOffice Database Connectivity). From Version 2.0 onward, OpenOffice.org used ISO/IEC 26300:2006 OpenDocument as its native format. Versions 2.0–2.3.0 default to

7480-404: Was much debate on whether to protect it as intellectual property under patent law , copyright law or establishing a unique regulation. Ultimately, copyright law became the standard with computer programs being considered a form of literary work, with some tweaks of unique regulation. Software is generally considered source code and object code , with both being protectable, though there

7568-497: Was not free software . The issue came to the fore in May 2005, when Richard Stallman appeared to call for a fork of the application in a posting on the Free Software Foundation website. OpenOffice.org adopted a development guideline that future versions of OpenOffice.org would run on free implementations of Java and fixed the issues which previously prevented OpenOffice.org 2.0 from using free-software Java implementations. On 13 November 2006, Sun committed to releasing Java under

7656-569: Was released on 23 June 2003. OpenOffice.org 1.1 introduced One-click Export to PDF, Export presentations to Flash (.SWF) and macro recording. It also allowed third-party addons. OpenOffice.org was used in 2005 by The Guardian to illustrate what it saw as the limitations of open-source software. Work on version 2.0 began in early 2003 with the following goals (the "Q Product Concept"): better interoperability with Microsoft Office; improved speed and lower memory usage; greater scripting capabilities; better integration, particularly with GNOME;

7744-417: Was released, featuring the ability to import (though not export) Office Open XML documents, support for ODF 1.2, improved VBA macros , and a native interface port for OS X. It also introduced the new Start Center and upgraded to LGPL version 3 as its license. Version 3.2 included support for PostScript-based OpenType fonts. It warned users when ODF 1.2 Extended features had been used. An improvement to

#710289