Archive:Project fork: Difference between revisions
wikademia>David Gerard why forking is possible |
wikademia>David Gerard hmm, let's separate that out |
||
| Line 3: | Line 3: | ||
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 that which it is possible to fork without permission of the original creator | [[free software|Free]] (libre) or [[open source]] software is, by definition, that which it is possible to fork without permission of the original creator. However, licensed forks of proprietary software (''e.g.'' [[Unix]]) can also be important. | ||
== Branching == | == Branching == | ||
| Line 9: | Line 9: | ||
==Free software== | ==Free software== | ||
Free or open source software is that which it is possible to fork with no prior permission, per the definitions of "[[free software]]" (''"Freedom 3: The freedom to improve the program, and release your improvements to the public, so that the whole community benefits"'') and "[[Open Source Definition|open source]]" (''"3. Derived Works: redistribution of modifications must be allowed. (To allow legal sharing and to permit new features or repairs.)"''). | |||
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 ([[X.Org Server]] and [[XFree86]], or [[cdrtools]] and [[cdrkit]]) or none to speak of (most branching [[Linux distribution]]s). | 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 ([[X.Org Server]] and [[XFree86]], or [[cdrtools]] and [[cdrkit]]) or none to speak of (most branching [[Linux distribution]]s). | ||