Archive:Project fork: Difference between revisions
wikademia>Otterathome |
|||
| Line 9: | Line 9: | ||
==Free software== | ==Free software== | ||
Free or open source software 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.)"''). | Free or open source software 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). | ||
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}} | 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 | ''[[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. [[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]] started as an unofficial project within [[Mozilla]] that soon replaced the [[Mozilla Suite]] as the focus of development. | 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]] started as an unofficial project within [[Mozilla]] that soon replaced the [[Mozilla Suite]] as the focus of development. | ||