Archive:Project fork: Difference between revisions
wikademia>Chealer encyclopedia-s are not software. PostgreSQL forks are already mentioned. tag {{refimprove}} |
wikademia>SmackBot Date/fix the maintenance tags or gen fixes |
||
| Line 1: | Line 1: | ||
{{ | {{Refimprove|date=August 2007}} | ||
{{otheruses|fork (disambiguation)}} | {{otheruses|fork (disambiguation)}} | ||
| Line 10: | Line 10: | ||
In free software, forks often result from a schism over different goals or personality clashes. In a fork, both parties assume nearly identical code bases but typically only the larger group, or that containing the original [[software architecture|architect]], will retain the full original name and its associated user community. Thus there is a reputation penalty associated with forking. | In free software, forks often result from a schism over different goals or personality clashes. In a fork, both parties assume nearly identical code bases but typically only the larger group, or that containing the original [[software architecture|architect]], will retain the full original name and its associated user community. Thus there is a reputation penalty associated with forking. | ||
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.{{Fact|date=August 2007}} | ||
''[[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. | ||
| Line 25: | Line 25: | ||
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.{{Fact|date=August 2007}} ''See'' [[UNIX wars]]. | ||
The BSD license permits forks of Free / Open Source software to become proprietary software, and some say that commercial incentives thus make proprietarisation almost inevitable. Examples include | The BSD license permits forks of Free / Open Source software to become proprietary software, and some say that commercial incentives thus make proprietarisation almost inevitable. Examples include | ||
| Line 46: | Line 46: | ||
* [http://www.dwheeler.com/oss_fs_why.html#forking Forking] ([[David A. Wheeler]]) | * [http://www.dwheeler.com/oss_fs_why.html#forking Forking] ([[David A. Wheeler]]) | ||
* [http://www.usemod.com/cgi-bin/mb.pl?RightToFork Right to Fork] at [[Meatball Wiki]]. | * [http://www.usemod.com/cgi-bin/mb.pl?RightToFork Right to Fork] at [[Meatball Wiki]]. | ||
[[Category:Software engineering]] | [[Category:Software engineering]] | ||
[[Category:Software forks| ]] | [[Category:Software forks| ]] | ||