Archive:Project fork: Difference between revisions
wikademia>David Gerard egcs/gcc |
wikademia>David Gerard EGCS/GCC; internal forking (Mozilla vs Mozilla Firebird) |
||
| Line 6: | Line 6: | ||
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 is a developer forking their own code to develop two versions, such as a windowed version and a command line version. | 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 is a developer forking their own code to develop two versions, such as a windowed version and a command line version. | ||
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 "blessed" as the official GCC project. | |||
Some projects attempt internal forks to further development. When the [[Mozilla]] suite (Seamonkey) appeared bogged down and overly beholden to [[Netscape Communications Corporation|Netscape]]'s commercial needs, some Mozilla developers started a separate stripped-down browser project. This developed into [[Mozilla Firebird]], which has been sufficiently successful to be declared the official Mozilla browser when it is ready. | |||
==Examples== | ==Examples== | ||
*[[Enciclopedia Libre]] is a fork from the [http://es.wikipedia.org Spanish-language Wikipedia] to evade possible advertising. | *[[Enciclopedia Libre]] is a fork from the [http://es.wikipedia.org Spanish-language Wikipedia] to evade possible advertising. | ||
*[[Pretty Good Privacy]] was forked outside of the United States to free it from the restrictive laws on the exportation of cryptographic software. | *[[Pretty Good Privacy]] was forked outside of the United States to free it from the restrictive laws on the exportation of cryptographic software. | ||
*[[XEmacs]] was a fork from [[Emacs]] to support the proprietary Energize environment. | *[[XEmacs]] was a fork from [[Emacs]] to support the proprietary Energize environment. | ||
*The split of [[Berkeley Software Distribution|BSD]] from AT&T [[UNIX]]. | *The split of [[Berkeley Software Distribution|BSD]] from AT&T [[UNIX]]. | ||
*A closed-source example is the development of the [[NTFS]] filesystem by Microsoft based in previous work in [[HPFS]] that was left to [[IBM]] | *A closed-source example is the development of the [[NTFS]] filesystem by Microsoft based in previous work in [[HPFS]] that was left to [[IBM]] | ||