Archive:Project fork: Difference between revisions
Linked Theo de Raadt's name to the page about him |
wikademia>David Gerard →Free software: it wasn't called Firefox then, of course |
||
| Line 16: | Line 16: | ||
''[[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. | ||
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]] | 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. | ||
On the matter of forking, the [[Jargon File]] says: | On the matter of forking, the [[Jargon File]] says: | ||