Content deleted Content added
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5 |
The lead would benefit from an example of a widely known fork (for any person, or at least for the FOSS community) |
||
Line 3:
{{Use dmy dates|date=December 2022}}
[[File:Linux Distribution Timeline.svg|thumb|upright|A timeline chart showing the evolution of [[Linux distribution]]s, with each split in the diagram being called "a fork"]]
In [[software engineering]], a '''project fork''' happens when developers take a copy of [[source code]] from one [[Computer software|software package]] and start independent development on it, creating a distinct and separate piece of software.{{Example needed|date=June 2024}} The term often implies not merely a [[branching (revision control)|development branch]], but also a split in the developer community; as such, it is a form of [[schism]].<ref>"Schism", with its connotations, is a common usage, ''e.g.''
* [http://www.jwz.org/doc/lemacs.html "the Lemacs/FSFmacs schism"] {{Webarchive|url=https://web.archive.org/web/20091130093142/http://www.jwz.org/doc/lemacs.html|date=30 November 2009}} ([[Jamie Zawinski]], 2000)
* [https://lwn.net/Articles/419822/ "Behind the KOffice split"] {{webarchive|url=https://web.archive.org/web/20130706094238/http://lwn.net/Articles/419822/|date=6 July 2013}} (Joe Brockmeier, ''Linux Weekly News'', 2010-12-14)
| |||