Archive:Project fork: Difference between revisions
wikademia>David Gerard separate into sections; shuffle, tweak |
wikademia>David Gerard more shuffling, CatB quote |
||
| Line 3: | Line 3: | ||
In [[software engineering]], a '''project fork''' happens when a developer (or a group of them) takes a copy of [[source code]] from one [[software package]] and starts to independently develop a new package. 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]]), particularly with [[free software|free]] or [[open source]] software. | In [[software engineering]], a '''project fork''' happens when a developer (or a group of them) takes a copy of [[source code]] from one [[software package]] and starts to independently develop a new package. 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]]), particularly with [[free software|free]] or [[open source]] software. | ||
A fork that is standard practice in many projects are ''stable'' or ''release'' versions which are modified only for bug fixes, while a ''development'' tree develops new features. 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] 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)]]. | A fork that is standard practice in many projects are ''stable'' or ''release'' versions which are modified only for bug fixes, while a ''development'' tree develops new features. 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] 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]]. | ||
==Free software== | ==Free software== | ||
| Line 10: | Line 10: | ||
Forks are considered an expression of the freedom made available by free software, but a weakness since they duplicate development efforts and can confuse users over which forked package to use. Developers have the option to collaborate and pool resources with free software, but it is not ensured by [[free software licenses]], only by a commitment to cooperation. That said, many developers will make the effort to put changes into all relevant forks, ''e.g.'' amongst the [[BSD]]s. | Forks are considered an expression of the freedom made available by free software, but a weakness since they duplicate development efforts and can confuse users over which forked package to use. Developers have the option to collaborate and pool resources with free software, but it is not ensured by [[free software licenses]], only by a commitment to cooperation. That said, many developers will make the effort to put changes into all relevant forks, ''e.g.'' amongst the [[BSD]]s. | ||
''[[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 relationship between the different teams can be cordial or very bitter. For instance, when the author of the [[LMule]] file-sharing program for Linux was uninterested in porting it to other systems, the [[xMule]] team started a fork to do so. Disagreements among the developers led to xMule itself being forked into [[aMule]], and the tension between the developers persisted. | The relationship between the different teams can be cordial or very bitter. For instance, when the author of the [[LMule]] file-sharing program for Linux was uninterested in porting it to other systems, the [[xMule]] team started a fork to do so. Disagreements among the developers led to xMule itself being forked into [[aMule]], and the tension between the developers persisted. | ||
| Line 28: | Line 30: | ||
==Other notable forks== | ==Other notable forks== | ||
*Most [[Linux distribution]]s are descended from other distributions, most being traceable back to [[Red Hat Linux]] or [[Debian]]. 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 to free it from the restrictive laws on the [[export of cryptography|exportation of cryptographic software]]. | *[[Pretty Good Privacy]] was forked outside of the United States to free it from the restrictive 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]]. | ||