Fork (software development): Difference between revisions

Revision as of 12:56, 20 August 2007

Revision as of 15:57, 27 August 2007

Line 10:

==Free software==

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. The relationship between the different teams can be cordial (''e.g.'' [[Ubuntu Linux|Ubuntu]] and [[Debian]]), very bitter ([[XOrgX.Org Server]] and [[XFree86]]) or none to speak of (most branching [[Linux distribution]]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}}