Fork (software development)

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.^{[example needed]} The term often implies not merely a development branch, but also a split in the developer community; as such, it is a form of schism.^[1] Grounds for forking are varying user preferences and stagnated or discontinued development of the original software.

Free and open-source software is that which, by definition, may be forked from the original development team without prior permission, and without violating copyright law. However, licensed forks of proprietary software (e.g. Unix) also happen.

^
"Schism", with its connotations, is a common usage, e.g.
- "the Lemacs/FSFmacs schism" Archived 30 November 2009 at the Wayback Machine (Jamie Zawinski, 2000)
- "Behind the KOffice split" Archived 6 July 2013 at the Wayback Machine (Joe Brockmeier, Linux Weekly News, 2010-12-14)
- "Copyright assignment – once bitten, twice shy" Archived 30 March 2012 at the Wayback Machine (Richard Hillesley, H-Online, 2010-08-06)
- "Forking is a feature" Archived 29 February 2012 at the Wayback Machine (Anil Dash, 2010-09-10)
- "The Great Software Schism" Archived 6 January 2012 at the Wayback Machine (Glyn Moody, Linux Journal, 2006-09-28)
- "To Fork Or Not To Fork: Lessons From Ubuntu and Debian" Archived 26 February 2012 at the Wayback Machine (Benjamin Mako Hill, 2005).

[1] "Schism", with its connotations, is a common usage, e.g.
"the Lemacs/FSFmacs schism" Archived 30 November 2009 at the Wayback Machine (Jamie Zawinski, 2000)

"Behind the KOffice split" Archived 6 July 2013 at the Wayback Machine (Joe Brockmeier, Linux Weekly News, 2010-12-14)

"Copyright assignment – once bitten, twice shy" Archived 30 March 2012 at the Wayback Machine (Richard Hillesley, H-Online, 2010-08-06)

"Forking is a feature" Archived 29 February 2012 at the Wayback Machine (Anil Dash, 2010-09-10)

"The Great Software Schism" Archived 6 January 2012 at the Wayback Machine (Glyn Moody, Linux Journal, 2006-09-28)

"To Fork Or Not To Fork: Lessons From Ubuntu and Debian" Archived 26 February 2012 at the Wayback Machine (Benjamin Mako Hill, 2005).

[2] "the Lemacs/FSFmacs schism" Archived 30 November 2009 at the Wayback Machine (Jamie Zawinski, 2000)

[3] "Behind the KOffice split" Archived 6 July 2013 at the Wayback Machine (Joe Brockmeier, Linux Weekly News, 2010-12-14)

[4] "Copyright assignment – once bitten, twice shy" Archived 30 March 2012 at the Wayback Machine (Richard Hillesley, H-Online, 2010-08-06)

[5] "Forking is a feature" Archived 29 February 2012 at the Wayback Machine (Anil Dash, 2010-09-10)

[6] "The Great Software Schism" Archived 6 January 2012 at the Wayback Machine (Glyn Moody, Linux Journal, 2006-09-28)

[7] "To Fork Or Not To Fork: Lessons From Ubuntu and Debian" Archived 26 February 2012 at the Wayback Machine (Benjamin Mako Hill, 2005).

[1]