For the idea of "open source" in general, see Open source
Open-source software (OSS) is computer software that is available in source code form for which the source code and certain other rights normally reserved for copyright holders are provided under a software license that permits users to study, change, and improve the software. Open source licenses often meet the requirements of the Open Source Definition. Some open source software is available within the public domain. Open source software is very often developed in a public, collaborative manner. Open-source software is the most prominent example of open-source development and often compared to (technically defined) user-generated content or (legally defined) open content movements. The term open-source software originated as part of a marketing campaign for free software. A report by Standish Group states that adoption of open-source software models has resulted in savings of about $60 billion per year to consumers.
 Open Source Definition
The Open Source Definition is used by the Open Source Initiative to determine whether or not a software license can be considered open source.
The definition was based on the Debian Free Software Guidelines, written and adapted primarily by Bruce Perens. They are by no means definitive even as applied to software; Note that clause 3 is the primary legal difference between free software and open source software as such, free software is stricter in interpreting 3. Note also that clauses 5 and 6 are not a condition of any major open content license regimes, which commonly do restrict types of uses and users, for instance, Creative Commons has open content licenses that explicitly forbid commercial use.
- Open source doesn't just mean access to the source code.
1. Free Redistribution
- The distribution terms of open-source software must comply with the following criteria:
2. Source Code
- The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.
3. Derived Works
- The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost preferably, downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the output of a preprocessor or translator are not allowed.
4. Integrity of The Author's Source Code
- The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
5. No Discrimination Against Persons or Groups
- The license may restrict source-code from being distributed in modified form only if the license allows the distribution of "patch files" with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software.
6. No Discrimination Against Fields of Endeavor
- The license must not discriminate against any person or group of persons.
7. Distribution of License
- The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
8. License Must Not Be Specific to a Product
- The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.
9. License Must Not Restrict Other Software
- The rights attached to the program must not depend on the program's being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution.
10. License Must Be Technology-Neutral
- The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software.
- No provision of the license may be predicated on any individual technology or style of interface.
' Open Source Initiative, http://opensource.org/docs/osd
The free software movement was launched in 1983. In 1998, a group of individuals advocated that the term free software should be replaced by open source software (OSS) as an expression which is less ambiguous and more comfortable for the corporate world. Software developers may want to publish their software with an open source license, so that anybody may also develop the same software or understand its internal functioning. Open source software generally allows anyone to create modifications of the software, port it to new operating systems and processor architectures, share it with others or market it.
The Open Source Definition, notably, presents an open source philosophy, and further defines the terms of usage, modification and redistribution of open source software. Software licenses grant rights to users which would otherwise be reserved by copyright law to the copyright holder. Several open source software licenses have qualified within the boundaries of the Open Source Definition. The most prominent and popular example is the GNU General Public License (GPL). While open source distribution presents a way to make the source code of a product publicly accessible, the open source licenses allow the authors to fine tune such access.
The open source label came out of a strategy session held on April 7, 1998 in Palo Alto in reaction to Netscape's January 1998 announcement of a source code release for Navigator (as Mozilla). A group of individuals at the session included Tim O'Reilly, Linus Torvalds, Tom Paquin, Jamie Zawinski, Larry Wall, Brian Behlendorf, Sameer Parekh, Eric Allman, Greg Olson, Paul Vixie, John Ousterhout, Guido van Rossum, Philip Zimmermann, John Gilmore and Eric S. Raymond. They used the opportunity before the release of Navigator's source code to clarify a potential confusion caused by the ambiguity of the word "free" in English.
Many people claimed that the birth of the Internet, since 1969, started the open source movement, while others do not distinguish between open source and free software movements.
The Free Software Foundation (FSF), started in 1985, intended the word 'free' to mean freedom to distribute (or "free as in free speech") and not freedom from cost (or "free as in free beer"). Since a great deal of free software already was (and still is) free of charge, such free software became associated with zero cost, which seemed anti-commercial.
The Open Source Initiative (OSI) was formed in February 1998 by Eric S. Raymond and Bruce Perens. With at least 20 years of evidence from case histories of closed software development versus open development already provided by the Internet developer community, the OSI presented the 'open source' case to commercial businesses, like Netscape. The OSI hoped that the usage of the label "open source," a term suggested by Peterson of the Foresight Institute at the strategy session, would eliminate ambiguity, particularly for individuals who perceive "free software" as anti-commercial. They sought to bring a higher profile to the practical benefits of freely available source code, and they wanted to bring major software businesses and other high-tech industries into open source. Perens attempted to register "open source" as a service mark for the OSI, but that attempt was impractical by trademark standards. Meanwhile, due to the presentation of Raymond's paper to the upper management at Netscape'Raymond only discovered when he read the Press Release, and was called by Netscape CEO Jim Barksdale's PA later in the day'Netscape released its Navigator source code as open source, with favorable results.
There are numerous groups who claim ownership of the term "Open Source", but the term has not been trademarked. The Open Source Initiative's definition is widely recognized as the standard or de facto definition.
The Open Source Initiative (OSI) was formed in February 1998 by Raymond and Perens. With about 20 years of evidence from case histories of closed and open development already provided by the Internet, the OSI continued to present the 'open source' case to commercial businesses. They sought to bring a higher profile to the practical benefits of freely available source code, and wanted to bring major software businesses and other high-tech industries into open source. Perens adapted Debian's Free Software Guidelines to make The Open Source Definition.
 The Open Source Definition
The Open Source Definition is used by the Open Source Initiative to determine whether a software license can be considered open source. The definition was based on the Debian Free Software Guidelines, written and adapted primarily by Bruce Perens. Perens did not base his writing on the "four freedoms" of Free Software from the Free Software Foundation, which were only widely available later.
 Perens' principles
Under Perens' definition, open source describes a broad general type of software license that makes source code available to the general public with relaxed or non-existent copyright restrictions. The principles, as stated, say absolutely nothing about trademark or patent use and require absolutely no cooperation to ensure that any common audit or release regime applies to any derived works. It is an explicit 'feature' of open source that it may put no restrictions on the use or distribution by any organization or user. It forbids this, in principle, to guarantee continued access to derived works even by the major original contributors.
 Proliferation of the term
While the term applied originally only to the source code of software, it is now being applied to many other areas such as open source ecology, a movement to decentralize technologies so that any human can use them. However, it is often misapplied to other areas which have different and competing principles, which overlap only partially.
 Non-software use
The principles of open source have been adapted for many other forms of user generated content and technology, including open source hardware.
Supporters of the open content movement advocate some restrictions of use, requirements to share changes, and attribution to other authors of the work.
This 'culture' or ideology takes the view that the principles apply more generally to facilitate concurrent input of different agendas, approaches and priorities, in contrast with more centralized models of development such as those typically used in commercial companies.
Advocates of the open source principles often point to Wikipedia as an example, but Wikipedia has in fact often restricted certain types of use or user, and the GFDL license it has historically used makes specific requirements of all users, which technically violates the open source principles.
 Business models
There are a number of commonly recognized barriers to the adoption of open source software by enterprises. These barriers include the perception that open source licenses are viral, lack of formal support and training, the velocity of change, and a lack of a long term roadmap. The majority of these barriers are risk-related. From the other side, not all proprietary projects disclose exact future plans, not all open source licenses are equally viral and many serious OSS projects (especially operating systems) actually make money from paid support and documentation.
A commonly employed Business Strategy of Commercial Open Source Software Firms is the Dual-License Strategy, as demonstrated by Ingres, MySQL, Alfresco, and others.
 Widely used open source products
Open source software (OSS) projects are built and maintained by a network of volunteer programmers. Prime examples of open source products are the Apache HTTP Server, the e-commerce platform osCommerce and the internet browser Mozilla Firefox. One of the most successful open source products is the GNU/Linux operating system, an open source Unix-like operating system.
 Development philosophy
In his 1997 essay The Cathedral and the Bazaar, open source evangelist 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, "carefully crafted by individual wizards or small bands of mages working in splendid isolation". He suggests that all software should be developed using the bazaar style, which he described as "a great babbling bazaar of differing agendas and approaches."
In 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. Fred P. Brooks in his book The Mythical Man-Month advocates this model. He goes further to say that in order to preserve the architectural integrity of a system, the system design should be done by as few architects as possible.
The bazaar model, however, is different. In this model, roles are not clearly defined. Gregorio Robles suggests that software developed using 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 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. Note that some users have advanced programming skills, and furthermore, each user's machine provides an additional testing environment. This new testing environment offers that ability to find and fix 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 is done automatically on a daily basis.
- 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 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. Cf. Extreme programming.
A license defines the rights and obligations that a licensor grants to a licensee. Open Source licenses grant licensees the right to copy, modify and redistribute source code (or content). These licenses may also impose obligations (e.g., modifications to the code that are distributed must be made available in source code form, an author attribution must be placed in a program/ documentation using that Open Source, etc.).
Authors initially derive a right to grant a license to their work based on the legal theory that upon creation of a work the author owns the copyright in that work. What the author/licensor is granting when they grant a license to copy, modify and redistribute their work is the right to use the author's copyrights. The author still retains ownership of those copyrights, the licensee simply is allowed to use those rights, as granted in the license, so long as they maintain the obligations of the license. The author does have the option to sell/assign, versus license, their exclusive right to the copyrights to their work; whereupon the new owner/assignee controls the copyrights. The ownership of the copyright (the 'rights') is separate and distinct from the ownership of the work (the 'thing') - a person can own a copy of a piece of code (or a copy of a book) without the rights to copy, modify or redistribute copies of it.
When an author contributes code to an Open Source project (e.g., Apache.org) they do so under an explicit license (e.g., the Apache Contributor License Agreement) or an implicit license (e.g., the Open Source license under which the project is already licensing code). Some Open Source projects do not take contributed code under a license, but actually require (joint) assignment of the author's copyright in order to accept code contributions into the project (e.g., OpenOffice.org and its Joint Copyright Assignment agreement).
Placing code (or content) in the public domain is a way of waiving an author's (or owner's) copyrights in that work. No license is granted, and none is needed, to copy, modify or redistribute a work in the public domain.
Examples of free software license / open source licenses include Apache License, BSD license, GNU General Public License, GNU Lesser General Public License, MIT License, Eclipse Public License and Mozilla Public License.
The proliferation of open source licenses is one of the few negative aspects of the open source movement because it is often difficult to understand the legal implications of the differences between licenses.
An important legal milestone for the open source / free software movement was passed in 2008, when the US federal appeals court ruled that free software licences definitely do set legally binding conditions on the use of copyrighted work, and they are therefore enforceable under existing copyright law. As a result, if end-users do violate the licensing conditions, their license disappears, meaning they are infringing copyright.
Unlike proprietary off-the-shelf software, which comes with restrictive copyright licenses, open-source software can be given away for no charge. This means that its creators cannot require each user to pay a license fee to fund development. Instead, a number of alternative models for funding its development have emerged.
Software can be developed as a consulting project for one or more customers. The customers pay to direct the developers' efforts: to have bugs prioritized and fixed or features added. Companies or independent consultants can also charge for training, installation, technical support, or customization of the software.
Another approach to funding is to provide the software freely, but sell licenses to proprietary add-ons such as data libraries. For instance, an open-source CAD program may require parts libraries which are sold on a subscription or flat-fee basis. Open-source software can also promote the sale of specialized hardware that it interoperates with, as in the case of the Asterisk telephony software, developed by a manufacturer of PC telephony hardware.
Many open-source software projects have begun as research projects within universities, as personal projects of students or professors, or as tools to aid scientific research. The influence of universities and research institutions on open source shows in the number of projects named after their host institutions, such as BSD Unix, CMU Common Lisp, or the NCSA HTTPd which evolved into Apache.
Companies may employ developers to work on open-source projects that are useful to the company's infrastructure: in this case, it is developed not as a product to be sold but as a sort of shared public utility. A larger project such as the Linux kernel may have contributors from dozens of companies which use and depend upon it, as well as hobbyist and research developers.
 Open source vs. closed source
The debate over open source vs. closed source (alternatively called proprietary software) is sometimes heated.
One source of conflict is related to economics: Making money through traditional methods, such as sale of the use of individual copies and patent royalty payment (generally called licensing), is more difficult and in many ways against the very concept of open source software.
Some closed-source advocates see open source software as damaging to the market of commercial software. This is one of the many reasons, as mentioned above, that the term free software was replaced with open source ' because many company executives could not believe in a product that did not participate economically in a free-market or mixed-market economy.
The counter to this argument is the use of open source software to fuel the market for a separate product or service. For example:
- Providing support and installation services; similar to IT Security groups, Linux Distributions, and Systems companies.
- Using the software as a stepping stone to sell a higher-end product or service; e.g., OpenOffice.org vs. StarOffice.
- Cost avoidance / cost sharing: many developers need a product, so it makes sense to share development costs (X Window System and the Apache web server)
Since Open Source software is open, all of the defects and security flaws are easily found. Closed-source advocates argue that this makes it easier for a malicious person to discover security flaws. Further, that there is no incentive for an open-source product to be patched. Open-source advocates argue that this makes it easier also for a patch to be found and that the closed-source argument is security through obscurity, which this form of security will eventually fail, often without anyone knowing of the failure. Further, that just because there is not an immediate financial incentive to patch a product, does not mean there is not any incentive to patch a product. Further, if the patch is that significant to the user, having the source code, the user can technically patch the problem themselves. These arguments are hard to prove. However, research indicates  that open-source software does have a higher flaw discovery, quicker flaw discovery, and quicker turn around on patches.
 Open source software vs. free software
The main difference is that by choosing one term over the other (i.e. either "open source" or "free software") you let others know about what your goals are.
"As one person put it, 'Open source is a development methodology; free software is a social movement.'"
Critics have said that the term 'open source' fosters an ambiguity of a different kind such that it confuses the mere availability of the source with the freedom to use, modify, and redistribute it. Developers have used the alternative terms Free/open source Software (FOSS), or Free/Libre/open source Software (FLOSS), consequently, to describe open source software which is also free software.
The term 'Open Source' was originally intended to be trademarkable; however, the term was deemed too descriptive, so no trademark exists. The OSI would prefer that people treat Open Source as if it were a trademark, and use it only to describe software licensed under an OSI approved license..
OSI Certified is a trademark licensed only to people who are distributing software licensed under a license listed on the Open Source Initiative's list.
Open source software and free software are different terms for software which comes with certain rights, or freedoms, for the user. They describe two approaches and philosophies towards free software. Open source and free software (or software libre) both describe software which is free from onerous licensing restrictions. It may be used, copied, studied, modified and redistributed without restriction. Free software is not the same as freeware, software available at zero price.
The definition of open source software was written to be almost identical to the free software definition. There are very few cases of software that is free software but is not open source software, and vice versa. The difference in the terms is where they place the emphasis. 'Free software' is defined in terms of giving the user freedom. This reflects the goal of the free software movement. 'Open source' highlights that the source code is viewable to all and proponents of the term usually emphasize the quality of the software and how this is caused by the development models which are possible and popular among free and open source software projects.
Free software licenses are not written exclusively by the FSF. The FSF and the OSI both list licenses which meet their respective definitions of free software.
The FSF believes that knowledge of the concept of freedom is an essential requirement, insists on the use of the term free, and separates itself from the open source movement.
 Open source vs. source-available
Although the OSI definition of "open source software" is widely accepted, a small number of people and organizations use the term to refer to software where the source is available for viewing, but which may not legally be modified or redistributed. Such software is more often referred to as source-available, or as shared source, a term coined by Microsoft.
Michael Tiemann, president of OSI, had criticized companies such as SugarCRM for promoting their software as "open source" when in fact it did not have an OSI-approved license. In SugarCRM's case, it was because the software is so-called "badgeware" since it specified a "badge" that must be displayed in the user interface (SugarCRM has since switched to GPLv3). Another example is Scilab, which calls itself "the open source platform for numerical computation" but has a license that forbids commercial redistribution of modified versions. Because OSI does not have a registered trademark for the term "open source", its legal ability to prevent such usage of the term is limited, but Tiemann advocates using public opinion from OSI, customers, and community members to pressure such organizations to change their license or to use a different term.
 Pros and cons
Software experts and researchers on open source software have identified several advantages and disadvantages. The main advantage for business is that open source is a good way for business to achieve greater penetration of the market. Companies that offer open source software are able to establish an industry standard and, thus, gain competitive advantage. It has also helped build developer loyalty as developers feel empowered and have a sense of ownership of the end product. Moreover less costs of marketing and logistical services are needed for OSS. It also helps companies to keep abreast of all technology developments. It is a good 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. Besides, it offers the potential for a more flexible technology and quicker innovation. It is said to be more reliable since it typically has thousands of independent programmers testing and fixing bugs of the software. It is flexible because modular systems allow programmers to build custom interfaces, or add new abilities to it and it 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 accord with purely technical requirements. It does not require to think about commercial pressure that often degrades the quality of 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.
It is sometimes said that the open source development process may not be well defined and the stages in the development process, such as system testing and documentation may be ignored. However this is only true for small (mostly single programmer) projects. Larger, successful projects do define and enforce at least some rules as they need them to make the teamwork possible. In the most complex projects these rules may be as strict as reviewing even minor change by two independent developers.
Not all OSS initiatives have been successful, for example, SourceXchange and Eazel. Software experts and researchers who are not convinced by open source's ability to produce quality systems identify the unclear process, the late defect discovery and the lack of any empirical evidence as the most important problems (collected data concerning productivity and quality). It is also difficult to design a commercially sound business model around the open source paradigm. Consequently, only technical requirements may be satisfied and not the ones of the market. In terms of security, open source may allow hackers to know about the weaknesses or loopholes of the software more easily than closed-source software. It is depended of control mechanisms in order to create effective performance of autonomous agents who participate in virtual organizations.
 Development tools
In OSS development the participants, who are mostly volunteers, are distributed amongst different geographic regions so there is need for tools to aid participants to collaborate in source code development. Often these tools are also available as OSS.
Revision control systems such as Concurrent Versions System (CVS) and later Subversion (svn) and Git are examples of tools that help centrally manage the source code files and the changes to those files for a software project.
Utilities that automate testing, compiling and bug reporting help preserve stability and support of software projects that have numerous developers but no managers, quality controller or technical support. Building systems that report compilation errors among different platforms include Tinderbox. Commonly used bugtrackers include Bugzilla and GNATS.
Tools such as mailing lists, IRC, and instant messaging provide means of Internet communications between developers. The Web is also a core feature of all of the above systems. Some sites centralize all the features of these tools as a software development management system, including GNU Savannah, SourceForge, and BountySource.
 Projects and organizations
Some of the more prominent organizations involved in OSS development include the Apache Software Foundation, creators of the Apache web server; a loose affiliation of developers headed by Linus Torvalds, creators of the Linux operating system kernel; the Eclipse Foundation, home of the Eclipse software development platform; the Debian Project, creators of the influential Debian GNU/Linux distribution; the Mozilla Foundation, home of the Firefox web browser; and ObjectWeb, European-born community developing open-source middleware. New organizations tend to have a more sophisticated governance model and their membership is often formed by legal entity members.
Several Open Source programs have become defining entries in their space, including the GIMP image editing system; Sun's Java programming language and environment; the MySQL database system; the FreeBSD Unix operating system; Sun's 2 OpenOffice.org office productivity suite; and the Wireshark network packet sniffer and protocol analyser.
Open Source development is often performed "live and in public", using services provided for free on the Internet, such as the Launchpad and SourceForge web sites, and using tools that are themselves Open Source, including the CVS and Subversion source control systems, and the GNU Compiler Collection.
Certification can help to build higher user confidence. Certification could be applied to the simplest component that can be used by developers to build the simplest module to a whole software system. There have been numerous institutions involving in this area of the open source software including The International Institute of Software Technology / United Nations University (http://www.iist.unu.edu). UNU/IIST is a non-profit research and education institution of The United Nations. It is currently involved in a project known as "The Global Desktop Project". This project aims to build a desktop interface that every end-user is able to understand and interact with, thus crossing the language and cultural barriers. It is drawing huge attention from parties involved in areas ranging from application development to localization. Furthermore, this project will improve developing nations' access to information systems. UNU/IIST aims to achieve this without any compromise in the quality of the software. It believes a global standard can be maintained by introducing certifications and is currently organizing conferences in order to explore frontiers in the field (http://opencert.iist.unu.edu).
Alternatively, assurance models (such as DO178B) have already solved the "certification" approach for software. This approach is tailorable and can be applied to OSS, but only if the requisite planning and execution, design, test and traceability artifacts are generated.
The criticisms of the specific Open Source Initiative (OSI) principles are dealt with above as part of the definition and differentiation from other terms. The open content movement does not recognize nor endorse the OSI principles and embraces instead mutual share-alike agreements that require commercial use or the preparation of derivative works.
Of the vocal critics, Richard Stallman of the Free Software Foundation (FSF), flatly opposes the term 'Open Source' being applied to what they refer to as 'free software'. Although it's clear that legally free software does qualify as open source, he considers that the category is abusive. They also oppose the professed pragmatism of the Open Source Initiative, as they fear that the free software ideals of freedom and community are threatened by compromising on the FSF's idealistic standards for software freedom.
Increasingly the consensus term Free and Open Source Software is used by the communities at large to describe the common ground between Free Software and Open Source.
 See also
- ^ Verts, William T. (2008-01-13). "Open source software". World Book Online Reference Center. http://www.worldbookonline.com/wb/Article?id=ar751706.
- ^ "Frequently Asked Questions". Open Source Initiative. Archived from the original on 2006-04-23. http://web.archive.org/web/20060423094434/www.opensource.org/advocacy/faq.html. Retrieved 2008-09-08.
- ^ Rothwell, Richard (2008-08-05). "Creating wealth with free software". Free Software Magazine. http://www.freesoftwaremagazine.com/community_posts/creating_wealth_free_software. Retrieved 2008-09-08.
- ^ "Standish Newsroom - Open Source". Press release. 2008-04-16. http://standishgroup.com/newsroom/open_source.php. Retrieved 2008-09-08.
- ^ Raymond, Eric S. (1998-02-08). "Goodbye, "free software"; hello, "open source"". http://www.catb.org/~esr/open-source.html. Retrieved 2008-08-13.
- ^ "Open Source Pioneers Meet in Historic Summit". 1998-04-14. http://press.oreilly.com/pub/pr/796. Retrieved 2010-08-19.
- ^ Muffatto, Moreno (2006). Open Source: A Multidisciplinary Approach. Imperial College Press. ISBN 1860946658.
- ^ Perens, Bruce. Open Sources: Voices from the Open Source Revolution. O'Reilly Media. 1999.
- ^ "The Open Source Definition by Bruce Perens". January 1999. http://www.oreilly.com/catalog/opensources/book/perens.html.
- ^ "The Open Source Definition". http://opensource.org/docs/osd. , The Open Source Definition according to the Open Source Initiative
- ^ http://news.slashdot.org/comments.pl?sid=1129863&cid=26875815
- ^ Stallman, Richard (September 24, 2007). "Why 'Open Source' misses the point of Free Software". Philosophy of the GNU Project. Free Software Foundation. http://www.gnu.org/philosophy/open-source-misses-the-point.html. Retrieved December 6, 2007. "However, not all of the users and developers of free software agreed with the goals of the free software movement. In 1998, a part of the free software community splintered off and began campaigning in the name of 'open source.' The term was originally proposed to avoid a possible misunderstanding of the term 'free software,' but it soon became associated with philosophical views quite different from those of the free software movement."
- ^ "Open Source Ecology". http://www.openfarmtech.org. "...building the world's first replicable open source self-sufficient decentralized high-appropriate-tech permaculture ecovillage..."
- ^ a b c Raymond, Eric S. The Cathedral and the Bazaar. ed 3.0. 2000.
- ^ Michael J. Gallivan, 'Striking a Balance Between Trust and Control in a Virtual Organization: A Content Analysis of Open Source Software Case Studies', Info Systems Journal 11 (2001): 277'304
- ^ Hal Plotkin, 'What (and Why) you should know about open-source software' Harvard Management Update 12 (1998): 8-9
- ^ a b Raymond, Eric S. (2000-09-11). "The Cathedral and the Bazaar". http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/index.html. Retrieved 2004-09-19.
- ^ Robles, Gregorio (2004). "A Software Engineering Approach to Libre Software". in Robert A. Gehring, Bernd Lutterbeck (PDF). Open Source Jahrbuch 2004. Berlin: Technical University of Berlin. http://www.opensourcejahrbuch.de/2004/pdfs/III-3-Robles.pdf. Retrieved 2005-04-20.
- ^ Shiels, Maggie (2008-08-14). "Legal milestone for open source". BBC News. http://news.bbc.co.uk/1/hi/technology/7561943.stm. Retrieved 2008-08-15.
- ^ As a case in point, the study Linux: Fewer Bugs Than Rivals reports that linux source code has 0.17 bugs per 1000 lines of code while non-Open-Source commercial software generally scores 20-30 bugs per 1000 lines
- ^ Nelson, Russell (2007-03-26). "Certification Mark". Open Source Initiative. Archived from the original on 2008-02-06. http://web.archive.org/web/20080206050627/http://www.opensource.org/docs/certification_mark.html. Retrieved 2007-07-22.
- ^ Raymond, Eric S. (1998-11-22). "OSI Launch Announcement". Open Source Initiative. http://www.opensource.org/pressreleases/osi-launch.php. Retrieved 2007-07-22.
- ^ Nelson, Russell (2006-09-19). "Open Source Licenses by Category". Open Source Initiative. http://opensource.org/licenses. Retrieved 2007-07-22.
- ^ a b c d Stallman, Richard (2007-06-16). "Why "Open Source" misses the point of Free Software". Philosophy of the GNU Project. GNU Project. http://www.gnu.org/philosophy/open-source-misses-the-point.html. Retrieved 2007-07-23.
- ^ a b c Stallman, Richard (2007-06-19). "Why "Free Software" is better than "Open Source"". Philosophy of the GNU Project. GNU Project. http://www.gnu.org/philosophy/free-software-for-freedom.html. Retrieved 2007-07-23.
- ^ Tiemann, Michael (2007-06-21). "Will The Real Open Source CRM Please Stand Up?". Open Source Initiative. http://www.opensource.org/node/163. Retrieved 2008-01-04.
- ^ Berlind, David (2006-11-21). "Are SugarCRM, Socialtext, Zimbra, Scalix and others abusing the term "open source?"". ZDNet. http://blogs.zdnet.com/BTL/index.php?p=3430. Retrieved 2008-01-04.
- ^ Vance, Ashlee (2007-07-25). "SugarCRM trades badgeware for GPL 3". The Register. http://www.regdeveloper.co.uk/2007/07/25/sugarcrm_gpl3/. Retrieved 2008-09-08.
- ^ "The open source platform for numerical computation". INRIA. http://www.scilab.org. Retrieved 2008-01-04.
- ^ "SCILAB License". INRIA. http://www.scilab.org/legal/license.html. Retrieved 2008-01-04.
- ^ a b Sharma, Srinarayan; Vijayan Sugumaran and Balaji Rajagopalan (2002). "A framework for creating hybrid-open source software communities" (PDF). Info Systems Journal 12: 7'25. doi:10.1046/j.1365-2575.2002.00116.x. http://www.cin.ufpe.br/~in953/lectures/papers/ISJAFrameworkForCreatingHybrid-OpenSourceSoftwareCommunities.pdf.
- ^ Landry, John; Rajiv Gupta (September 2000). "Profiting from Open Source". Harvard Business Review. doi:10.1225/F00503.
- ^ Plotkin, Hal (December 1998). "What (and Why) you should know about open-source software". Harvard Management Update: 8'9. doi:10.1225/U9812D.
- ^ Payne, Christian (February 2002). "On the Security of Open Source Software". Info Systems Journal 12 (1): 61'78. doi:10.1046/j.1365-2575.2002.00118.x.
- ^ http://www.gnu.org/software/classpath/docs/hacking.html
- ^ Meffert, Klaus; Neil Rotstan (2007). "Brief summary of coding style and practice used in JGAP". Java Genetic Algorithms Package. http://jgap.sourceforge.net/doc/codestyle.html. Retrieved 2008-09-08.
- ^ Tripp, Andy (2007-07-16). "Classpath hackers frustrated with slow OpenJDK process". Javalobby. http://www.javalobby.org/java/forums/t98834.html.
- ^ Gallivan, Michael J. (2001). "Striking a Balance Between Trust and Control in a Virtual Organization: A Content Analysis of Open Source Software Case Studies". Info Systems Journal 11 (4): 277'304. doi:10.1111/j.1365-2575.2001.00108.x.
- ^ François Letellier (2008), Open Source Software: the Role of Nonprofits in Federating Business and Innovation Ecosystems, AFME 2008.
- ^ Stallman, Richard (June 16, 2007). "Why 'Open Source' misses the point of Free Software". Philosophy of the GNU Project. Free Software Foundation. http://www.gnu.org/philosophy/open-source-misses-the-point.html. Retrieved July 23, 2007. "As the advocates of open source draw new users into our community, we free software activists have to work even more to bring the issue of freedom to those new users' attention. We have to say, 'It's free software and it gives you freedom!''more and louder than ever. Every time you say 'free software' rather than 'open source,' you help our campaign."
- ^ Stallman, Richard (June 19, 2007). "Why 'Free Software' is better than 'Open Source'". Philosophy of the GNU Project. Free Software Foundation. http://www.gnu.org/philosophy/free-software-for-freedom.html. Retrieved July 23, 2007. "Sooner or later these users will be invited to switch back to proprietary software for some practical advantage. Countless companies seek to offer such temptation, and why would users decline? Only if they have learned to value the freedom free software gives them, for its own sake. It is up to us to spread this idea'and in order to do that, we have to talk about freedom. A certain amount of the 'keep quiet' approach to business can be useful for the community, but we must have plenty of freedom talk too."
- ^ Stallman, Richard (June 16, 2007). "Why 'Open Source' misses the point of Free Software". Philosophy of the GNU Project. Free Software Foundation. http://www.gnu.org/philosophy/open-source-misses-the-point.html. Retrieved July 23, 2007. "Under the pressure of the movie and record companies, software for individuals to use is increasingly designed specifically to restrict them. This malicious feature is known as DRM, or Digital Restrictions Management (see DefectiveByDesign.org), and it is the antithesis in spirit of the freedom that free software aims to provide. ['] Yet some open source supporters have proposed 'open source DRM' software. Their idea is that by publishing the source code of programs designed to restrict your access to encrypted media, and allowing others to change it, they will produce more powerful and reliable software for restricting users like you. Then it will be delivered to you in devices that do not allow you to change it. This software might be 'open source,' and use the open source development model; but it won't be free software, since it won't respect the freedom of the users that actually run it. If the open source development model succeeds in making this software more powerful and reliable for restricting you, that will make it even worse."
 Further reading
 Legal and economic aspects
- Benkler, Yochai (2002), 'Coase's Penguin, or, Linux and The Nature of the Firm." Yale Law Journal 112.3 (Dec 2002): p367(78) (in Adobe pdf format)
- v. Engelhardt, Sebastian (2008) (PDF). "The Economic Properties of Software", Jena Economic Research Papers, Volume 2 (2008), Number 2008-045. http://ideas.repec.org/p/jrp/jrpwrp/2008-045.html.
- Lerner, J. & Tirole, J. (2002): 'Some simple economics on open source', Journal Of Industrial Economics 50(2), p 197'234
- Välimäki, Mikko (2005) (PDF). The Rise of Open Source Licensing: A Challenge to the Use of Intellectual Property in the Software Industry. Turre Publishing. http://pub.turre.com/openbook_valimaki.pdf.
- Polley, Barry (2007-12-11) (PDF). Open Source Discussion Paper ' version 1.0. New Zealand Ministry of Justice. http://nzoss.org.nz/system/files/moj_oss_strategy_1.0.pdf. Retrieved 2007-12-12.
- Rossi, M. A. (2006): Decoding the free/open source software puzzle: A survey of theoretical and empirical contributions, in J. Bitzer P. Schröder, eds, 'The Economics of Open Source Software Development', p 15'55.
 External links
- Computerworld article: Does the open-source development model work for business users?
- The Open Source Initiative's definition of open source
- Open Sources: Voices from the Open Source Revolution ' an online book containing essays from prominent members of the open source community
- Free / Open Source Research Community ' Many online research papers about Open Source
- FreeOpenSourceSoftware.org - Wiki on Open Source history, organizations, licenses, people, software.
- KDE developer Aaron Siego's presentation "How OSS Improves Society" at the 2nd Trans-Pacific Open Source Software Conference in Honolulu, Hawaii, January 2006.
- Whence The Source: Untangling the Open Source/Free Software Debate, essay on the differences between Free Software and Open Source, by Thomas Scoville
- Berry, D M (2004). The Contestation of Code: A Preliminary Investigation into the Discourse of the Free Software and Open Software Movement, Critical Discourse Studies, Volume 1(1).
- EU study on adopting FLOSS
- Open Source Observatory and Repository
- Calls for open source government