Jumat, 15 Juni 2018

Sponsored Links

src: www.snowbound.com

Open source software ( OSS ) is a type of computer software whose source code is released under a license in which the copyright holder grants the user the right to learn, change, and distribute software to anyone and for any purpose. Open source software can be developed in a collaborative, general way. According to scientists who study it, open-source software is a real example of open collaboration. The term is often written without hyphens as "open source software".

Open source software development, or collaborative development among some independent contributors, results in a wider range of design perspectives than any company capable of developing and sustaining the long term. A 2008 report by Standish Group states that adoption of open-source software models has resulted in savings of approximately $ 60 billion ($ 48 billion) per year to consumers.


Video Open-source software



Histori

Akhir 1990-an: Fondasi Inisiatif Open Source

In the early days of computing, programmers and developers shared software to learn from each other and develop computing fields. Eventually the idea of ​​open source moved to the street side of software commercialization in 1970-1980. However, academics still often develop collaborative software, such as Donald Knuth in 1979 with the typesetting system TeX or Richard Stallman in 1983 with the GNU operating system. In 1997, Eric Raymond published The Cathedral and the Bazaar , a reflective analysis of the hacker community and the principle of free software. This paper received significant attention in early 1998, and was a factor in motivating Netscape Communications Corporation to release their popular Netscape Communicator Internet software as free software. This source code then becomes the basis behind SeaMonkey, Mozilla Firefox, Thunderbird and KompoZer.

Netscape's actions encourage Raymond and others to figure out how to bring the Free Software Foundation software idea and the perceived benefits to the commercial software industry. They conclude that FSF's social activism does not appeal to companies like Netscape, and is looking for ways to change the brand of free software movement to emphasize the potential of business sharing and collaborating on software source code. The new term they chose was "open source", which was soon adopted by Bruce Perens, publishers Tim O'Reilly, Linus Torvalds, and others. The Open Source Initiative was established in February 1998 to encourage the use of new terms and evangelize open source principles.

While the Open Source Initiative seeks to encourage the use of new terms and evangelize the principles it adheres to, commercial software vendors find themselves increasingly threatened by freely distributed software concepts and universal access to application source code. A Microsoft executive openly declared in 2001 that "open source is an intellectual property destroyer.I can not imagine something that could be worse than this for the software business and the intellectual property business." However, while free and open source software has historically played a role outside the mainstream of private software development, large companies like Microsoft have begun to develop an official open-source presence on the Internet. IBM, Oracle, Google, and State Farm are some companies that have serious public shares in today's competitive open-source market. There was a significant shift in the company's philosophy of FOSS development.

The free software movement was launched in 1983. In 1998, a group of individuals suggested that the term free software should be replaced with open-source software (OSS) as a less ambiguous and more convenient expression for the business world. Software developers may want to publish their software with open source licenses, so anyone can develop the same software or understand its internal functionality. With open-source software, generally anyone is allowed to make modifications, port it to a new operating system and instruction set architecture, share it with others or, in some cases, market it. Scholar Casson and Ryan have pointed out several policy-based reasons for open source adoption - in particular, the increased value proposition of open source (when compared to the most exclusive formats) in the following categories:

  • Security
  • Affordability
  • Transparency
  • Perpeting
  • Interoperability
  • Flexibility
  • Localization - especially in the context of local government (which makes software decisions). Casson and Ryan argue that "the government has an inherent responsibility and fiduciary duty to taxpayers" which includes a careful analysis of these factors when deciding to purchase proprietary software or implementing open-source options.

The Open Source Definition , primarily, presents an open-source philosophy, and further defines the terms of use, modification and redistribution of open-source software. Software licenses grant the rights to users who should be protected by copyright law. Some open-source software licenses are qualified within the Open Source Definition limits. The most prominent and popular example is the GNU General Public License (GPL), which "allows free distribution on condition that further development and apps are placed under the same license", thus also free.

The open source label came out of a strategy session held on 7 April 1998 in Palo Alto in reaction to Netscape's January 1998 announcement of the source code release for the Navigator (such as Mozilla). A group of people in 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 Eric S. Raymond. They used the opportunity before the release of the Navigator source code to clarify potential confusion caused by the ambiguity of the word "free" in English.

Many people claim that the birth of the Internet, since 1969, started the open source movement, while others do not distinguish between open source and free software movement.

The Free Software Foundation (FSF), started in 1985, means "free" to mean freedom to distribute (or "free as in free speech") and not freedom from cost > (or "free as in free beer"). Since many free software is already (and still is) free, such free software becomes associated with zero cost, which seems anti-commercial.

The Open Source Initiative (OSI) was formed in February 1998 by Eric Raymond and Bruce Perens. With at least 20 years of evidence of a closed-versus open-source software development case that has been provided by the Internet developer community, OSI presents an "open source" case for commercial businesses, such as Netscape. The OSI hopes that the use of the "open source" label, a term advised by Christine Peterson of the Foresight Institute on strategy sessions, will eliminate ambiguity, especially for individuals who consider "free software" as anti-commercial. They try to bring a higher profile to the practical benefits of free source code available, and they want to bring the mainstream software business and other high-tech industries into open source. Perens attempted to register "open source" as a service mark for the OSI, but the effort was not practical with trademark standards. Meanwhile, because Raymond's paper presentation for upper management in Netscape - Raymond was only discovered when he read the press release, and was called by Netscape CEO Jim Barksdale's PA in the future - Netscape released the Navigator source code as an open source, with profitable results.

Maps Open-source software



Definition

The Open Source Initiative (OSI) definition is recognized by the government internationally as a standard de fi nition or de facto . In addition, many of the projects and contributors of the world's largest open source software, including Debian, Drupal Associations, FreeBSD Foundation, Linux Foundation, Mozilla Foundation, Wikimedia Foundation, WordPress Foundation have committed to uphold OSI missions and Open Source Definitions through OSI Affiliation Approvals.

OSI uses the Open Source Definition to determine if it considers open source software licenses. This definition is based on the Debian Free Software Guide, written and adapted primarily by Perens. Perens does not base his writing on the "four freedoms" of the Free Software Foundation (FSF), which is only widely available later.

By Perens definition, open source describes a wide range of general software licenses that make source code available to the general public with casual or non-existent restrictions on code usage and modification. It is an explicit "feature" of open source that places very few restrictions on the use or distribution by organizations or users, to allow for the rapid evolution of the software.

Despite initially accepting it, Richard Stallman of the FSF is now firmly opposed to the term "Open Source" applied to what they call "free software". Although he agrees that the two terms describe "almost the same software category", Stallman considers equating the wrong and misleading terms. Stallman also opposes the recognized pragmatism of the Open Source Initiative, as he fears that freedom-free software freedom and society are threatened by a compromise on the FSF's ideal standard for software freedom. The FSF considers free software as part of open source software, and Richard Stallman explains that DRM software, for example, can be developed as open source, although it does not give users freedom (it limits them), and thus does not qualify as free software.

Open source software license

When an author contributes code to an open source project (eg Apache.org) they do so under an explicit license (eg, the Apache Contributor License Agreement) or an implicit license (eg open source licenses where this project is already a license code). Some open-source projects do not take the contribution code under license, but actually require the mutual assignment of the author's copyright to receive code contributions into the project.

Examples of free software licenses/open source licenses include Apache License, BSD license, GNU General Public License, GNU Low General Public License, MIT License, Eclipse Public License, and Mozilla Public License.

The development of open-source licenses is a negative aspect of the open-source movement because it is often difficult to understand the legal implications of the differences between licenses. With over 180,000 open-source projects available and over 1400 unique licenses, the complexity of deciding how to manage open source usage in commercial "closed-source" companies has increased dramatically. Some are home-grown, while others are modeled after major FOSS licenses such as Berkeley Software Distribution ("BSD"), Apache, MIT-style (Massachusetts Institute of Technology), or the GNU General Public License ("GPL"). In this view, open-source practitioners begin to use a classification scheme in which FOSS licenses are grouped (usually based on the presence and liability imposed by the copyleft provision; the strength of copyleft provision).

An important legal milestone for the open source/free software movement was adopted in 2008, when a US federal appeals court ruled that a free software license would prescribe legally binding conditions on the use of copyrighted works, and therefore may be enforced under the law existing copyright. As a result, if the end user violates the terms of the license, the license disappears, meaning they infringe copyright. Despite the risks of licensing, most commercial software vendors use open source software in commercial products when they meet licensing requirements, e.g. make use of Apache license.

Certification

Certification can help build user trust. Certification can be applied to the simplest component, to the entire software system. The United Nations International Institute of Technology for Software Technology, started a project known as the "Global Desktop Project". The project aims to build a desktop interface that every end-user can understand and interact with, thereby traversing language and cultural barriers. This project will increase the access of developing countries to information systems. UNU/IIST hopes to achieve this without compromise in software quality by introducing certification.

src: belfoss.eeecs.qub.ac.uk


Open-source software development

Development model

In its 1997 essay and Bazaar , open source evangelist Eric S. Raymond suggested a model for developing an OSS known as a bazaar model. Raymond likens software development with a traditional methodology for building a cathedral, "carefully crafted by individual wizards or a small group of magicians working in beautiful isolation." He suggested that all software should be developed using the bazaar style, which he described as "an astonishing great bazaar of various agendas and approaches."

In the traditional development model, which he calls cathedral model, development takes place centrally. Roles are clearly defined. Roles include people dedicated to designing (the architect), the person responsible for managing the project, and the person responsible for implementation. Traditional software engineering follows the cathedral model.

The bazaar model, however, is different. In this model, the role is not clearly defined. Gregorio Robles points out that software developed using the bazaar model should show the following pattern:

Users should be treated as a shared developer
Users are treated like fellow developers and they must have access to software source code. In addition, users are encouraged to submit additions to the software, code fixes for software, bug reports, documentation, etc. After more developers together, increase the rate of software development. Linus's law states, "Given enough eyes, all insects are shallow." This means that if many users see the source code, they will eventually find all the 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 test environment offers the ability to find and fix new bugs.
Initial release
The first version of the software should be released as early as possible so as to increase one's chances of finding an early co-developer.
Frequent integration
Code changes should be integrated (combined into a common code base) as often as possible so as to avoid overhead fixing a large number of bugs at the end of the project life cycle. Some open source projects have been built every night where integration is done automatically every day.
Multiple 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 development version) is for users who want to quickly use the latest features, and are willing to accept the risk of using code that has not been fully tested. Users can then act as developer partners, report bugs and provide 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 formal or informal decision-making structure, which makes strategic decisions dependent on changing user needs and other factors. Compare with extreme programming.

The data show, however, that OSS is not democratic enough as shown by the bazaar model. An analysis of five billion bytes of free/open source code by 31,999 developers shows that 74% of the code is written by the 10% most active authors. The average number of authors involved in the project is 5.1, with the median at 2.

Advantages and disadvantages

Open source software is usually easier to obtain than proprietary software, often resulting in increased usage. In addition, the availability of standard open source implementations can improve the adoption of those standards. It also helps build developer loyalty because developers feel empowered and have a sense of ownership of the final product.

In addition, lower marketing and logistics costs are required for OSS. OSS also helps companies keep pace with technological developments. This is a great tool for promoting the company's image, including its commercial products. The OSS development approach has helped to produce reliable, high-quality software quickly and inexpensively.

Open source development offers the potential for more flexible technology and faster innovation. It is said to be more reliable because it usually has thousands of independent programmers who test and fix bugs from software. Open source does not depend on the company or author who originally created it. Even if the company fails, the code continues to exist and developed by its users. Also, using open standards that are accessible to everyone; thus, there are no incompatible formatting issues present in the proprietary software.

This is flexible because the modular system allows programmers to build custom interfaces, or add new capabilities to it and it's innovative because open source programs are a collaborative product among a large number of different programmers. The combination of different perspectives, corporate goals, and personal goals accelerates innovation.

In addition, free software can be developed in accordance with pure technical requirements. No need to think about commercial pressures that often degrade software quality. Commercial pressures make traditional software developers pay more attention to customer needs than security requirements, because such features are somewhat invisible to customers.

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, can be ignored. This however only applies to small projects (mostly single programmers). Larger and more successful projects do define and enforce at least some rules because they need them to make teamwork possible. In the most complex projects, this rule may be as strict as reviewing even minor changes by two independent developers.

Not all OSS initiatives are successful, such as SourceXchange and Eazel. Software experts and researchers who are unsure of open source capabilities to produce quality systems identify unclear processes, late disability discoveries and lack of empirical evidence as the most important problem (collecting data on productivity and quality). It is also difficult to design a commercially viable business model around the open source paradigm. Consequently, only technical requirements can be met and not those of the market. In terms of security, open source can allow hackers to know about weaknesses or loopholes of software more easily than closed source software. It depends on the control mechanisms to create effective performance of autonomous agents participating in virtual organizations.

Development tools

In OSS development, tools are used to support product development and development process itself.

Revision control systems such as System Version Serially (CVS) and Subversion (SVN) and Git are examples of tools, often open source, helping to manage source code files and changes to those files for software projects. These projects are often hosted and published on sites like Launchpad, Bitbucket, and GitHub.

Open source projects are often loosely organized with "minimal modeling or formalized process support", but utilities like problem trackers are often used to manage open source software development. Commonly used bugtrackers include Bugzilla and Redmine.

Tools such as mailing lists and IRC provide a means of coordination among developers. Centralized code hosting sites also have social features that allow developers to communicate.

Organization

Some of the more prominent "organizations" involved in OSS development include the Apache Software Foundation, the creator of the Apache web server; The Linux Foundation, the nonprofit that in 2012 employs Linus Torvalds, the creator of the Linux operating system kernel; Eclipse Foundation, home of the Eclipse software development platform; The Debian project, an influential maker of Debian GNU/Linux distributions; Mozilla Foundation, home of Firefox web browser; and OW2, the European-born community that develops open source middleware. New organizations tend to have more sophisticated governance models and their membership is often shaped by members of legal entities.

The Open Source Software Institute is a non-profit, membership-based (501 (c) (6) organization founded in 2001 that promotes the development and implementation of open source software solutions within federal, state and local government agencies. OSSI's efforts have focused on promoting the adoption of open source software programs and policies within the Federal Government's community and Defense and Homeland Security.

Open Source for America is a group created to raise awareness in the Federal Government of the United States about the benefits of open source software. Their stated purpose is to encourage the use of open source software by governments, participation in open source software projects, and the incorporation of open source community dynamics to enhance government transparency.

Mil-OSS is a group dedicated to the advancement of the use and creation of OSS in the military.

Funding

Open-source software is widely used both as an independent application and as a component in non-open-source applications. Many independent software vendors (ISVs), value-added retailers (VARs), and hardware vendors (OEM or ODM) use open source frameworks, modules, and libraries in their profit-driven, proprietary products and services. From a customer perspective, the ability to use open technologies under the requirements and standard commercial support is invaluable. They are willing to pay for legal protection (eg, indemnification of copyright or patent infringement), "commercial level QA", and professional support/training/consulting typical of commercial software, while also benefiting from fine-grained controls and lack of locking which comes with open-source.

src: thumbnails-visually.netdna-ssl.com


Comparison with other software license/development model

Closed source/owned software

The debate about open source vs. closed source (or so-called proprietary software) sometimes heats up.

Four main reasons (such as those provided by the Open Source Business Conference survey) individuals or organizations choosing open source software are:

  1. lower cost
  2. security
  3. there is no vendor key in '
  4. better quality

Since innovative companies no longer rely heavily on software sales, proprietary software becomes increasingly unnecessary. Thus, things like open source content management systems - or CMS - are becoming more commonplace. In 2009, the US White House switched CMS system from an exclusive system to Drupal's open source CMS. Furthermore, companies like Novell (which traditionally sell software the old way) continue to debate the benefits of switching to open source availability, having shifted parts of product offerings to open source code. In this way, open source software provides solutions to unique or specific problems. Thus, it was reported that 98% of company-level firms use open source software offerings in multiple capacities.

With this market shift, more important systems are beginning to rely on open source offerings, enabling greater funding (such as the US Department of Homeland Security grants) to help "hunt for security bugs." According to a pilot study the organization adopted (or not adopted) the OSS, the following factors of statistical significance were observed in the manager's beliefs: (a) attitudes toward outcomes, (b) influence and behavior of others, and (c) their ability to act.

The major source distributors have begun to develop and contribute to the open source community because of the shift in market share, doing so with the need to reinvent their models to stay competitive.

Many proponents argue that open source software is inherently more secure because everyone can view, edit, and modify the code. A study of Linux source code has 0.17 bugs per 1000 lines of code while proprietary software generally generates 20-30 bugs per 1000 rows.

Free software

According to Free software movement leader Richard Stallman, the main difference is that by choosing one term on another (ie either "open source" or "free software"), people let others know what a person's goal is: "Open source is a development methodology; free software is a social movement. "Nevertheless, there is significant overlap between open source software and free software.

The FSF says that the term "open source" fosters the ambiguity of a different kind that confuses only the availability of resources with the freedom to use, modify, and redistribute it. On the other hand, the term "free software" is criticized for the ambiguity of the word "free" as "available at no cost", which is seen as understated for business adoption, and for the historical ambiguous use of the term.

Developers have used alternative terms Free and Open Source Software (FOSS), or Libre and Open Source Software (FLOSS), consequently, to describe open source software which is also free software. While the definition of open source software is very similar to the FSF free software definition it is based on the Debian Free Software Guidelines, written and adapted mainly by Bruce Perens with input from Eric S. Raymond and others.

The term "open source" was originally intended to be a trademark; However, the term is considered too descriptive, so there is no trademark. OSI would prefer 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 that is only granted to persons who distribute licensed software under the license listed in the Open Source Initiative list.

Open-source versus 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 be legally modified or redistributed. The software is more commonly referred to as source-available , or as common source , a term coined by Microsoft in 2001. While in 2007, two shared resource licenses have been certified by OSI, most shared resource licenses are available sources only .

In 2007, Michael Tiemann, president of the OSI, criticized companies such as SugarCRM for promoting their software as "open source" when in fact it did not have an OSI-approved license. In the case of SugarCRM, it's because of the software called "badgeware" because it sets the "badge" that should be displayed in the user interface (SugarCRM since switching to GPLv3). Another example is Scilab before version 5, which calls itself "open source platform for numerical computation" but has a license that prohibits modified commercial redistribution versions.

Open-sourcing

Open-sourcing is the act of spreading the open source movement, which most often refers to releasing proprietary software previously under open source/free software licenses, but may also refer to Open Source software or install Open Source software.

The leading, previously proprietary software packages, which have been sourced openly include:

  • Netscape Navigator, the code under which the Mozilla and Mozilla Firefox web browsers are
  • StarOffice, which is the basis of the OpenOffice.org office suite and LibreOffice
  • The Global File System, originally the GPL, was then made public in 2001 (?), but in 2004 was the re-GPL.
  • SAP DB, which has become MaxDB, and is now distributed (and owned) by MySQL AB
  • The Interbase database, which opened from Borland in 2000 and currently exists as a commercial product and open-source fork (Firebird)

Before changing software licenses, distributors usually audit the source code for a third party license code that they must delete or obtain permission for relicense. Backdoor and other malware should also be removed as they can be easily found after the release of the code.

src: i.ytimg.com


Current app and adoption

Most widely used open-source software

The open source software project is built and maintained by a network of volunteer programmers and is widely used for free as well as commercial products. The main examples of open-source products are the Apache HTTP Server, the osCommerce e-commerce platform, the Mozilla Firefox web browser, and Chromium (the project where most of the Google Chrome freeware development has finished) and the LibreOffice full office. One of the most successful open-source products is the GNU/Linux operating system, the open-source Unix operating system, and its Android derivatives, the operating system for mobile devices. In some industries, open source software is the norm.

src: www.livemint.com


Extensions for non-software use

While the term "open source" was initially applied only to software source code, it is now being applied to many other fields such as Open source ecology, a movement to decentralize technology so that every human can use it. However, it is often misused to other areas that have different and competing principles, which overlap only partly.

The same principle that underlies open source software can be found in many other businesses, such as open-source hardware, Wikipedia, and open access publishing. Collectively, these principles are known as open source, open content, and open collaboration: "any system of innovation or production that depends on a goal-oriented but loosely-coordinated participant who interacts to create products (or services) of economic value , which they provide to contributors and non-contributors alike. "

Source of the article : Wikipedia

Comments
0 Comments