Archive:Project fork: Difference between revisions
wikademia>SmackBot Date/fix the maintenance tags or gen fixes |
wikademia>David Gerard "prone to"? Possible to! + section edits; no really, even SuSE came from Slackware |
||
| Line 2: | Line 2: | ||
{{otheruses|fork (disambiguation)}} | {{otheruses|fork (disambiguation)}} | ||
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 piece of software | 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 piece of software. | ||
[[free software|Free]] (libre) or [[open source]] software is, by definition, that which it is possible to fork without permission of the original creator. | |||
== Branching == | |||
A kind of fork that is standard practice in many projects is a ''stable'' or ''release'' version, modified only for bug fixes, while a ''development'' tree develops new features. Such forks are often referred to instead as "branches" both to avoid the negative connotations of a fork and because it is closer in intent and function to the common software engineering meaning of [[branching (software)|branching]]. | A kind of fork that is standard practice in many projects is a ''stable'' or ''release'' version, modified only for bug fixes, while a ''development'' tree develops new features. Such forks are often referred to instead as "branches" both to avoid the negative connotations of a fork and because it is closer in intent and function to the common software engineering meaning of [[branching (software)|branching]]. | ||
| Line 14: | Line 17: | ||
''[[The Cathedral and the Bazaar]]'' stated in 1997 [http://www.catb.org/~esr/writings/cathedral-bazaar/homesteading/ar01s03.html] that ''"The most important characteristic of a fork is that it spawns competing projects that cannot later exchange code, splitting the potential developer community."'' However, this is not common present usage. | ''[[The Cathedral and the Bazaar]]'' stated in 1997 [http://www.catb.org/~esr/writings/cathedral-bazaar/homesteading/ar01s03.html] that ''"The most important characteristic of a fork is that it spawns competing projects that cannot later exchange code, splitting the potential developer community."'' However, this is not common present usage. | ||
In some cases, a fork can merge back into the original project or replace it. | In some cases, a fork can merge back into the original project or replace it. [[EGCS]] (the 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 have attempted to invoke this effect deliberately, ''e.g.'' [[Mozilla Firefox]] was an unofficial project within [[Mozilla]] that soon replaced the [[Mozilla Suite]] as the focus of development. | ||
On the matter of forking, the [[Jargon File]] says: | On the matter of forking, the [[Jargon File]] says: | ||
:"Forking is considered a [[Bad Thing]] — not merely because it implies a lot of wasted effort in the future, but because forks tend to be accompanied by a great deal of strife and acrimony between the successor groups over issues of legitimacy, succession, and design direction. There is serious social pressure against forking. As a result, major forks (such as the [[GNU Emacs|Gnu-Emacs]]/[[XEmacs]] split, the fissioning of the [[386BSD]] group into three daughter projects, and the short-lived GCC/EGCS split) are rare enough that they are remembered individually in hacker folklore." | :"Forking is considered a [[Bad Thing]] — not merely because it implies a lot of wasted effort in the future, but because forks tend to be accompanied by a great deal of strife and acrimony between the successor groups over issues of legitimacy, succession, and design direction. There is serious social pressure against forking. As a result, major forks (such as the [[GNU Emacs|Gnu-Emacs]]/[[XEmacs]] split, the fissioning of the [[386BSD]] group into three daughter projects, and the short-lived GCC/EGCS split) are rare enough that they are remembered individually in hacker folklore." | ||
It is easy to declare a fork, but can require considerable effort to continue independent development and support. As such, forks without adequate resources can soon become inactive, ''e.g.'' [[GoneME]], a fork of [[GNOME]] by a former developer, which was soon discontinued despite attracting some publicity. Some well-known forks have enjoyed great success, however, such as the [[X.Org Server|X.Org]] [[X Window System|X11]] server, a fork from [[XFree86]] which gained widespread support and notably sped up X development. | It is easy to declare a fork, but can require considerable effort to continue independent development and support. As such, forks without adequate resources can soon become inactive, ''e.g.'' [[GoneME]], a fork of [[GNOME]] by a former developer, which was soon discontinued despite attracting some publicity. Some well-known forks have enjoyed great success, however, such as the [[X.Org Server|X.Org]] [[X Window System|X11]] server, a fork from [[XFree86]] which gained widespread support from developers and users and notably sped up X development. | ||
==Proprietary software== | ==Proprietary software== | ||
| Line 25: | Line 28: | ||
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 [[Window (computing)|windowed]] version and a [[command line interface|command line]] version, or versions for differing operating systems, such as a [[wordprocessor]] for [[IBM PC]] compatible machines and [[Apple Macintosh|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. | 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 [[Window (computing)|windowed]] version and a [[command line interface|command line]] version, or versions for differing operating systems, such as a [[wordprocessor]] for [[IBM PC]] compatible machines and [[Apple Macintosh|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]] — all derived from AT&T Unix and all called "Unix", but increasingly mutually incompatible. | A notable proprietary fork not of this kind is the many varieties of proprietary [[Unix]] — all derived from AT&T Unix and all called "Unix", but increasingly mutually incompatible.<!-- see the see-also for the reference for this --> ''See'' [[UNIX wars]]. | ||
The BSD | The [[BSD licenses]] permit forks to become proprietary software, and some say that commercial incentives thus make proprietisation almost inevitable. Examples include | ||
[http://www.enterprisedb.com EnterpriseDB] (a version of PostgreSQL with Oracle compatibility features), [http://www.fastware.com.au/docs/FujitsuSupportedPostreSQLWhitePaperV1_02.pdf Fujitsu Supported PostgresSQL] | [http://www.enterprisedb.com EnterpriseDB] (a version of PostgreSQL with Oracle compatibility features), [http://www.fastware.com.au/docs/FujitsuSupportedPostreSQLWhitePaperV1_02.pdf Fujitsu Supported PostgresSQL] | ||
with their proprietary ESM storage system, and [http://www.netezza.com/media/2004/Weblog.htm Netezza]'s proprietary highly scalable derivative of PostgreSQL. Some of these vendors contribute back changes to the community project | with their proprietary ESM storage system, and [http://www.netezza.com/media/2004/Weblog.htm Netezza]'s 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. | ||
==Other notable forks== | ==Other notable forks== | ||
*Most [[Linux distribution]]s are descended from other distributions, most being traceable back to [[Debian]] or | *Most [[Linux distribution]]s are descended from other distributions, most being traceable back to [[Debian]], [[Red Hat Linux|Red Hat]] or [[Slackware]]. Since most of the content of a distribution is free software, ideas and software interchange freely as is useful to the individual distribution. Merges (''e.g.'', [[United Linux]] or [[Mandriva]]) are rare. | ||
*[[Pretty Good Privacy]] was forked outside of the United States | *[[Pretty Good Privacy]] was forked outside of the United States<!-- see that article for ref--> to free it from restrictive US laws on the [[export of cryptography|exportation of cryptographic software]]. | ||
*The game [[NetHack]] has spawned a number of variants using the original code, notably [[Slash'EM]], and was itself a fork of [[Rogue (computer game)|Rogue]]. | *The game [[NetHack]] has spawned a number of variants using the original code, notably [[Slash'EM]], and was itself a fork of [[Rogue (computer game)|Rogue]]. | ||
*[[OpenBSD]] was a fork of [[NetBSD]] 1.0 by Theo de Raadt | *[[OpenBSD]] was a fork of [[NetBSD]] 1.0 by Theo de Raadt | ||
| Line 40: | Line 43: | ||
*[[DragonFly BSD]] was forked from [[FreeBSD]] 4.8 by long-time FreeBSD developer [[Matt Dillon (computer scientist)|Matt Dillon]], due to disagreement over FreeBSD 5's technical direction. | *[[DragonFly BSD]] was forked from [[FreeBSD]] 4.8 by long-time FreeBSD developer [[Matt Dillon (computer scientist)|Matt Dillon]], due to disagreement over FreeBSD 5's technical direction. | ||
*[[Adempiere]] is a community maintained fork of [[Compiere]] 2.5.3b, due to disagreement with commercial and technical direction of Compiere Inc. | *[[Adempiere]] is a community maintained fork of [[Compiere]] 2.5.3b, due to disagreement with commercial and technical direction of Compiere Inc. | ||
*[[NeoOffice]] is a fork of [[OpenOffice.org]], with an incompatible license, due to disagreements about licensing and about the best method to [[porting|port]] OpenOffice.org to [[Mac OS X]]. | *[[NeoOffice]] is a fork of [[OpenOffice.org]], with an incompatible license (GPL rather than LGPL), due to disagreements about licensing and about the best method to [[porting|port]] OpenOffice.org to [[Mac OS X]]. | ||
==References== | ==References== | ||