Fork
In software engineering, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct and separate piece of software. The term often implies not merely a development branch, but a split in the developer community, a form of schism.<ref>"Schism", with its connotations, is a common usage, e.g. "the Lemacs/FSFmacs schism" (Jamie Zawinski, 2000), "Behind the KOffice split" (Joe Brockmeier, Linux Weekly News, 2010-12-14), "Copyright assignment - once bitten, twice shy" (Richard Hillesley, H-Online, 2010-08-06), "Forking is a feature" (Anil Dash, 2010-09-10), "The Great Software Schism" (Glyn Moody, Linux Journal, 2006-09-28), "To Fork Or Not To Fork: Lessons From Ubuntu and Debian" (Benjamin Mako Hill, 2005).</ref>
Free and open-source software is that which, by definition, may be forked from the original development team without prior permission without violating copyright law. However, licensed forks of proprietary software (e.g. Unix) also happen.
Etymology
The word fork stems from the Latin word furca, meaning a "fork or similarly shaped instrument."<ref> See, e.g., "furca" from Etymological Dictionary of Latin by Michiel de Vaan (Ph.D. 2002)</ref> "Fork" in the meaning of "to divide in branches, go separate ways" has been used as early as the 14th century.<ref>Entry 'fork' in Online Etymology Dictionary</ref> In the software environment, the word evokes the fork system call, which causes a running process to split itself into two (almost) identical copies that (typically) diverge to perform different tasks.<ref>"The term fork is derived from the POSIX standard for operating systems: the system call used so that a process generates a copy of itself is called fork()." Template:Cite conference</ref>
In the context of software development, "fork" was used in the sense of creating a revision control "branch" by Eric Allman as early as 1980, in the context of SCCS:<ref>Allman, Eric. "An Introduction to the Source Code Control System." Project Ingres, University of California at Berkeley, 1980.</ref>
The term was in use on Usenet by 1983 for the process of creating a subgroup to move topics of discussion to.<ref>Can somebody fork off a "net.philosophy"? (John Gilmore, net.misc, 18 January 1983)</ref>
"Fork" is not known to have been used in the sense of a community schism during the origins of Lucid Emacs (now XEmacs) (1991) or the BSDs (1993–1994); Russ Nelson used the term "shattering" for this sort of fork in 1993, attributing it to John Gilmore.<ref>Shattering — good or bad? (Russell Nelson, gnu.misc.discuss, 1 October 1993)</ref> However, "fork" was in use in the present sense by 1995 to describe the XEmacs split,<ref>Re: Hey Franz: 32K Windows SUCK!!!!! (Bill Dubuque, cu.cs.macl.info, 21 September 1995)</ref> and was an understood usage in the GNU Project by 1996.<ref>Lignux? (Marcus G. Daniels, gnu.misc.discuss, 7 June 1996)</ref>
Forking of free and open source software
Free and open source software may be legally forked without prior approval of those currently developing, managing, or distributing the software per both The Free Software Definition and The Open Source Definition:<ref name=wheeler/> Template:Quotation Template:Quotation
In free software, forks often result from a schism over different goals or personality clashes. In a fork, both parties assume nearly identical code bases, but typically only the larger group, or whoever controls the Web site, will retain the full original name and the associated user community. Thus, there is a reputation penalty associated with forking.<ref name=wheeler/> The relationship between the different teams can be cordial or very bitter.
Eric S. Raymond, in his essay Homesteading the Noosphere,<ref>Template:Cite web</ref> stated that "The most important characteristic of a fork is that it spawns competing projects that cannot later exchange code, splitting the potential developer community". He notes in the Jargon File:
David A. Wheeler notes<ref name=wheeler>Why Open Source Software / Free Software (OSS/FS, FLOSS, or FOSS)? Look at the Numbers!: Forking (David A. Wheeler)</ref> four possible outcomes of a fork, with examples:
- The death of the fork. This is by far the most common case. It is easy to declare a fork, but considerable effort to continue independent development and support.
- A re-merging of the fork (e.g., egcs becoming "blessed" as the new version of gcc.)
- The death of the original (e.g. the X.Org Server succeeding and XFree86 dying.)
- Successful branching, typically with differentiation (e.g., OpenBSD and NetBSD.)
Distributed revision control (DVCS) tools have popularised a less emotive use of the term "fork", blurring the distinction with "branch".<ref>e.g. Template:Cite web See also Template:Cite thesis</ref> With a DVCS such as Mercurial or Git, the normal way to contribute to a project is to first branch the repository, and later seek to have your changes integrated with the main repository. Sites such as GitHub, Bitbucket and Launchpad provide free DVCS hosting expressly supporting independent branches, such that the technical, social and financial barriers to forking a source code repository are massively reduced, and GitHub uses "fork" as its term for this method of contribution to a project.
Forks often restart version numbering from 0.1 or 1.0 even if the original software was at version 3.0, 4.0, or 5.0. An exception is when the forked software is designed to be a drop-in replacement for the original project, e.g. MariaDB for MySQL<ref>Forked a project, where do my version numbers start?</ref> or LibreOffice for OpenOffice.org.
Forking proprietary software
In proprietary software, the copyright is usually held by the employing entity, not by the individual software developers. Proprietary code is thus more commonly forked when the owner needs to develop two or more versions, such as a windowed version and a command line version, or versions for differing operating systems, such as a word processor for IBM PC compatible machines and Macintosh computers. Generally, such internal forks will concentrate on having the same look, feel, data format, and behavior between platforms so that a user familiar with one can also be productive or share documents generated on the other. This is almost always an economic decision to generate a greater market share and thus pay back the associated extra development costs created by the fork.
A notable proprietary fork not of this kind is the many varieties of proprietary Unix—almost all derived from AT&T Unix and all called "Unix", but increasingly mutually incompatible.<ref name=moen>Fear of forking - An essay about forking in free software projects, by Rick Moen</ref> See UNIX wars.
The BSD licenses permit forks to become proprietary software, and some sayTemplate:Who that commercial incentives thus make proprietisation almost inevitable. Examples include Mac OS X (based on the proprietary NeXTSTEP and the open source FreeBSD), Cedega and CrossOver (proprietary forks of Wine, though CrossOver tracks Wine and contributes considerably), EnterpriseDB (a fork of PostgreSQL, adding Oracle compatibility features<ref>EnterpriseDB</ref>), Supported PostgreSQL with their proprietary ESM storage system,<ref>Fujitsu Supported PostgreSQL</ref> and Netezza's<ref>Netezza</ref> proprietary highly scalable derivative of PostgreSQL. Some of these vendors contribute back changes to the community project, while some keep their changes as their own competitive advantages.
See also
References
| references-column-width
| references-column-count references-column-count-{{#if:1|30em}} }}
| {{#if:
| references-column-width }} }}" style="{{#if: 30em
| {{#iferror: {{#ifexpr: 30em > 1 }}
| Template:Column-width
| Template:Column-count }}
| {{#if:
| Template:Column-width }} }} list-style-type: {{#switch:
| upper-alpha
| upper-roman
| lower-alpha
| lower-greek
| lower-roman = {{{group}}}
| #default = decimal}};">
<references group=""></references>
