<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://ideawaza.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=199.120.189.49</id>
	<title>IdeaWazaWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://ideawaza.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=199.120.189.49"/>
	<link rel="alternate" type="text/html" href="https://ideawaza.com/wiki/Special:Contributions/199.120.189.49"/>
	<updated>2026-09-29T23:47:15Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.0</generator>
	<entry>
		<id>https://ideawaza.com/index.php?title=Archive:Project_fork&amp;diff=25598</id>
		<title>Archive:Project fork</title>
		<link rel="alternate" type="text/html" href="https://ideawaza.com/index.php?title=Archive:Project_fork&amp;diff=25598"/>
		<updated>2005-03-03T18:48:47Z</updated>

		<summary type="html">&lt;p&gt;199.120.189.49: capitalization, punctuation&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In [[software]], a &#039;&#039;&#039;project fork&#039;&#039;&#039; or &#039;&#039;&#039;branch&#039;&#039;&#039; happens when a developer (or a group of them) takes code from a project and starts to develop independently of the rest. The term is also used more loosely to represent a similar branching of any work (for example, there are several forks of the English language [[Wikipedia]]).&lt;br /&gt;
&lt;br /&gt;
The term is particularly used in [[free software|free]] or [[open source]] software, when a [[schism]] occurs because of different goals or personality clashes. Some see forks as a weakness in open source, but they can demonstrate the adaptability of the model. The relationship between the different teams can be cordial or very bitter.&lt;br /&gt;
&lt;br /&gt;
In a fork of this type, both parties inherit identical [[intellectual rights]] but typically only the larger group, or that containing the original [[software architecture|architect]], will retain the full original name and its associated [[social capital]].  Thus there is a reputation penalty associated with forking.&lt;br /&gt;
&lt;br /&gt;
This can happen in closed-source software as well, if the rights to the common code are shared; but this is rarer, as usually there are strict rules about ownership of the code. More commonly in closed source software, a developer forks its own code to develop two versions, such as a windowed version and a command line version.&lt;br /&gt;
&lt;br /&gt;
Another sort of fork is a standard practice in many projects: to fork a &#039;&#039;stable&#039;&#039; or &#039;&#039;release&#039;&#039; version which will be modified only for bug fixes, while a &#039;&#039;development&#039;&#039; tree continues to get new features added. This is common practice in the [[Linux kernel]], for instance, but has been misrepresented occasionally in the trade press as the more problematic sort of fork described above. [http://www.groklaw.net/article.php?story=20041121124609671]&lt;br /&gt;
&lt;br /&gt;
In some cases, a fork can merge back into the original project or replace it. [[EGCS]] (Experimental/Enhanced GNU Compiler System) was a fork from [[GNU Compiler Collection|GCC]] which proved more vital than the original project and was eventually &amp;quot;blessed&amp;quot; as the official GCC project.&lt;br /&gt;
&lt;br /&gt;
Likewise, when development of the [[Mozilla]] suite (Seamonkey) appeared bogged down and overly beholden to [[Netscape Communications Corporation|Netscape]]&#039;s commercial needs, some Mozilla developers started a separate stripped-down browser project. This developed into [[Mozilla Firefox]], which has been sufficiently successful to become the primary focus of [[Mozilla Foundation]] browser activity.&lt;br /&gt;
&lt;br /&gt;
==Other examples==&lt;br /&gt;
&lt;br /&gt;
*[[Enciclopedia Libre]] is a fork from the [http://es.wikipedia.org Spanish-language Wikipedia] to evade possible advertising.&lt;br /&gt;
*[[Pretty Good Privacy]] was forked outside of the United States to free it from the restrictive laws on the exportation of cryptographic software.&lt;br /&gt;
*[[XEmacs]] was a fork from [[Emacs]] to support the proprietary Energize environment.&lt;br /&gt;
*The split of [[Berkeley Software Distribution|BSD]] from AT&amp;amp;T [[Unix|UNIX]].&lt;br /&gt;
*The many varieties of [[proprietary]] [[Unix|UNIX]] &amp;amp;mdash; all derived from AT&amp;amp;T UNIX and all called &amp;quot;UNIX&amp;quot;, but increasingly mutually incompatible. &#039;&#039;See&#039;&#039; [[UNIX wars]].&lt;br /&gt;
*The development of the [[NTFS]] filesystem by Microsoft based upon previous work on [[HPFS]] that was left to [[IBM]]&lt;br /&gt;
*The game [[Nethack]] has spawned a number of variants using the original code (it is sometimes thought of as a fork of [[Rogue (computer game)|Rogue]], but its code was written independently).&lt;br /&gt;
*[[OpenBSD]] was originally a fork from [[NetBSD]], arising from conflicts of personality between NetBSD developers.&lt;br /&gt;
*[[OpenSSH]] was a fork from [[SSH]], which happened because the license for SSH 2.x was &amp;quot;[[non-free]]&amp;quot; (even though the source was available), so an older version of SSH 1.x, which was the last to have been licensed as [[free software]], was forked. Within months, virtually all Linux distributions, BSD versions and even some proprietary Unixes had replaced SSH with OpenSSH.&lt;br /&gt;
*The [[Xorg]] [[X Window System|X]] server was a fork from [[XFree86]] for a very similar reason as that of SSH and OpenSSH. Development on [[X11]] has since speeded up and most distributions have switched.&lt;br /&gt;
*[[DragonflyBSD]] forked from [[FreeBSD]] in order to pursue different technical approaches to those used in FreeBSD 5.&lt;br /&gt;
* [[Inkscape]] forked from [[Sodipodi]].&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[revision control]]&lt;br /&gt;
&lt;br /&gt;
[[de:Fork]]&lt;br /&gt;
[[fr:Fork]]&lt;br /&gt;
[[pl:Fork]]&lt;/div&gt;</summary>
		<author><name>199.120.189.49</name></author>
	</entry>
</feed>