Fork: Difference between revisions

From WikiIndex
Jump to navigation Jump to search
(Created page with "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 distin...")
 
mNo edit summary
 
(34 intermediate revisions by 7 users not shown)
Line 1: Line 1:
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.
<div style=float:right>{{Not a wiki}}</div>
In {{tag|software}} engineering, a project <b>fork</b> happens when [[developer]]s take a copy of source-code from a specific software package, and then start independent {{tag|Software development|development}} upon it, thus creating a distinct piece of 'new' software.


For instance, the above text was forked from the [[English Wikipedia]]! Free content licenses allow users to copy material in part or whole to create their own versions of that content: be it a cultural work, a piece of media, software, or some intellectual pursuit.
The term <b>{{tag|fork}}</b> is also used in the '[[wikisphere]]'.  For example, the above text was forked from the [[English Wikipedia]]! Most [[:Category:Open content|free content]] [[:Category:Wiki license|licenses]] allow [[:Category:Wiki people|people]] to copy material in part or whole; to create their own separate versions of that content: be it a [[:Category:Culture|cultural]] work, a piece of [[:Category:Media|media]], software, or some intellectual pursuit.
{{TOC right}}
Sometimes, forking results in [[fragmentation]], whereby two separate [[wiki community|wiki-communities]] have overlapping but divergent goals. There are strengths and weaknesses to this. On one hand, different communities can meet different needs, and problem-solve in new ways. This also keeps one cultural work from being dominated or controlled by a [[god-king|single individual]] or small subset of [[User|people]]. On the other hand, fragmentation can create redundancy, and confusion between people.


Sometimes, forking results in [[fragmentation]], whereby two separate communities have overlapping goals. There are strengths and weaknesses to this. On the one hand, different communities can meet different needs and problem-solve in new ways. This also keeps one cultural work from being dominated or controlled by a single individual or small subset of users. On the other hand, fragmentation can create redundancy and confusion amongst users.
[[Wiki]]-forking typically starts as [[mirror]]ing, which is a similar concept; where one wiki-website hosts <u>identical</u> content to another wiki-website.
 
{{See also|federated wiki (wiki)}}
 
==Wiki-forking vs. wiki-mirroring==
A [[mirror]] wiki-website <i>coud</i>, or may also be described as an [[:Category:Archives|archive]]. It duplicates or re-uses content which originated elsewhere (hopefully, with proper [[attribution]], and respecting its original [[:Category:Wiki license|license(s)]]), but a wiki-mirror normally is <u>not</u> an originator of <u>new content</u>.
 
A wiki-fork creates an entirely new second project (sometimes, though not always, with an identical wiki-website name); the wiki-fork uses a common set of [[:Category:Wiki Topic|content]] as a starting point. As the new wiki-fork project matures, it builds a (new) [[community]], and creates its own new, unique content, and ultimately its own new identity.
 
In the global '[[wikisphere]]', the most significant fork was the creation of [[:Category:Wikivoyage|Wikivoyage]]. Wikivoyage started as a wholly independent fork of the earlier [[:Category:Wikitravel|Wikitravel]]. The Wikivoyage fork was seeded, and gained significant traction, after the original (private) [[owner]]s of Wikitravel latterly sold it to [[:Category:Internet Brands|Internet Brands, Inc.]] (a highly commercial, 'for profit' company), which then had the result of alienating the original Wikitravel community (who, like most open-content wiki-[[editor]]s, were all unpaid volunteers).
 
Conversely, the many various sites which merely provide an 'archived' copy of [[English Wikipedia]] content online (such as the [[NationMaster Encyclopedia]]) without originating new content are mirrors.
[[File:Spoon.jpg|thumb|300px|A '[[:Category:Spoon|spoon]]' is the term used to describe an original wiki-website that was left, often [[:Category:Goal abandoned|abandoned]], following a {{tag|fork}}.|alt=]]
 
==On [[wiki farm]]s==
Forking is common on [[:Category:Wikia|Wikia]] (now known as Fandom), usually because of its forced [[:Category:Wikia skin|skin]] changes, poor community support, [[global blocking]], enforced social features, and a bombarding plethora of objectional on-screen [[:Category:Advertising|advertising]] (including video adverts); and also because independent hosting is more versatile, and more controllable.  Where [[:Category:Ex-Wikia|forking occurs]], the [[:Category:Goal abandoned|abandoned]] Wikia version of the site; invariably left [[:Category:OpenEdit|open]] and frequently [[:Category:Dormant|dormant]], is commonly referred to as the '[[:Category:Spoon|spoon]]'.
 
==Forked wiki articles on WikiIndex==
From the founding outset of [[WikiIndex]], the long-term goal has been to have an article entry page; and therefore an [[Template:Wiki|infobox]]; for <u>ALL</u> wiki-websites, even [[:Category:Dead|dead]] and / or [[:Category:Dormant|dormant]] wiki-websites. Forked wiki-websites are to be treated with exactly the same ethos; therefore, WikiIndex has a specific method of dealing with forked wiki.  Fundamentally, a forked wiki-website [[article]] (and also any [[:Category:Wiki engine|wiki engine]] forks) <i>shoud</i> each have their own <u>separate</u> article page, with their own infobox and [[Template:Size|size template]].<!--Separate articles are preferred due to different page counts, wikiFactor values, edit modes, even differing wiki engines, etc-->  The two separate wiki-website articles shoud be annotated at the top of their respective pages with a standard 'hatnote', specificly using [[template:For]]; this will give the reader of the article here on WikiIndex salient information, along with the required [[wikilink]], to either the original (spoon) wiki-website, or its subsequent forked wiki-website.
 
[[Mirror]]ed wiki-websites <i>may</i> be treated different to forked wiki-websites, in that both wiki-websites (if both remain [[:Category:Active|active]]) will eventually contain differing content, and may ultimately form differing identities. In these instances, we would have two (or more, for multiple mirrors) separate page articles here on WikiIndex. Again, just like the forked examples, a 'hatnote' template shoud be used on all article pages relevant to any mirrors, and the originating wiki-website article.
 
 
[[Category:Fork| ]]
[[Category:Wiki idea]]
[[Category:Glossary]]

Latest revision as of 06:38, 30 October 2025

This Fork article is
referring to a site which seems
not to be, or include, a wiki.
However, it still refers to, or is
pertinent to the subject of wikis.

In software engineering, a project fork happens when developers take a copy of source-code from a specific software package, and then start independent development upon it, thus creating a distinct piece of 'new' software.

The term fork is also used in the 'wikisphere'. For example, the above text was forked from the English Wikipedia! Most free content licenses allow people to copy material in part or whole; to create their own separate versions of that content: be it a cultural work, a piece of media, software, or some intellectual pursuit.

Sometimes, forking results in fragmentation, whereby two separate wiki-communities have overlapping but divergent goals. There are strengths and weaknesses to this. On one hand, different communities can meet different needs, and problem-solve in new ways. This also keeps one cultural work from being dominated or controlled by a single individual or small subset of people. On the other hand, fragmentation can create redundancy, and confusion between people.

Wiki-forking typically starts as mirroring, which is a similar concept; where one wiki-website hosts identical content to another wiki-website.

See also: federated wiki (wiki).

Wiki-forking vs. wiki-mirroring[edit]

A mirror wiki-website coud, or may also be described as an archive. It duplicates or re-uses content which originated elsewhere (hopefully, with proper attribution, and respecting its original license(s)), but a wiki-mirror normally is not an originator of new content.

A wiki-fork creates an entirely new second project (sometimes, though not always, with an identical wiki-website name); the wiki-fork uses a common set of content as a starting point. As the new wiki-fork project matures, it builds a (new) community, and creates its own new, unique content, and ultimately its own new identity.

In the global 'wikisphere', the most significant fork was the creation of Wikivoyage. Wikivoyage started as a wholly independent fork of the earlier Wikitravel. The Wikivoyage fork was seeded, and gained significant traction, after the original (private) owners of Wikitravel latterly sold it to Internet Brands, Inc. (a highly commercial, 'for profit' company), which then had the result of alienating the original Wikitravel community (who, like most open-content wiki-editors, were all unpaid volunteers).

Conversely, the many various sites which merely provide an 'archived' copy of English Wikipedia content online (such as the NationMaster Encyclopedia) without originating new content are mirrors.

A 'spoon' is the term used to describe an original wiki-website that was left, often abandoned, following a fork.

On wiki farms[edit]

Forking is common on Wikia (now known as Fandom), usually because of its forced skin changes, poor community support, global blocking, enforced social features, and a bombarding plethora of objectional on-screen advertising (including video adverts); and also because independent hosting is more versatile, and more controllable. Where forking occurs, the abandoned Wikia version of the site; invariably left open and frequently dormant, is commonly referred to as the 'spoon'.

Forked wiki articles on WikiIndex[edit]

From the founding outset of WikiIndex, the long-term goal has been to have an article entry page; and therefore an infobox; for ALL wiki-websites, even dead and / or dormant wiki-websites. Forked wiki-websites are to be treated with exactly the same ethos; therefore, WikiIndex has a specific method of dealing with forked wiki. Fundamentally, a forked wiki-website article (and also any wiki engine forks) shoud each have their own separate article page, with their own infobox and size template. The two separate wiki-website articles shoud be annotated at the top of their respective pages with a standard 'hatnote', specificly using template:For; this will give the reader of the article here on WikiIndex salient information, along with the required wikilink, to either the original (spoon) wiki-website, or its subsequent forked wiki-website.

Mirrored wiki-websites may be treated different to forked wiki-websites, in that both wiki-websites (if both remain active) will eventually contain differing content, and may ultimately form differing identities. In these instances, we would have two (or more, for multiple mirrors) separate page articles here on WikiIndex. Again, just like the forked examples, a 'hatnote' template shoud be used on all article pages relevant to any mirrors, and the originating wiki-website article.