Guest User

Stop calling them forks

a guest
Jul 19th, 2026
30
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.44 KB | None | 0 0
  1. @@ -1,29 +1,30 @@
  2. If you know wikis that are hosted outside Fandom, you may have heard the
  3. -term *fork*. In short words, *forking* refers to the process of leaving
  4. -Fandom, moving a wiki to a different wiki farm or being indepentendly
  5. -hosted by the community.
  6. +term *fork*. In short, *forking* refers to the process of leaving
  7. +Fandom, moving a wiki to another wiki farm or being independently hosted
  8. +by the community.
  9.  
  10. -The term is used as an analogy to [road
  11. -forks](https://en.wikipedia.org/wiki/Intersection_(road)), where the
  12. -idea is that a wiki will be now available at two different places, and
  13. -you will choose one or the other at the intersection before arriving.
  14. -Alternatively, you can also associate it with the meaning of [fork in
  15. -programming
  16. +The term is an analogy to [road
  17. +forks](https://en.wikipedia.org/wiki/Intersection_(road)), where a wiki
  18. +becomes available in two different places, and you will choose one or
  19. +the other at the intersection before arriving. Alternatively, you can
  20. +associate it with the meaning of [fork in programming
  21. spaces](https://en.wikipedia.org/wiki/Fork_(software_development)),
  22. -which refers to duplicating an existing project to a different, separate
  23. -space to modify it independently.
  24. +which refers to creating a copy of an existing project that can evolve
  25. +independently.
  26.  
  27. -This blog post is not telling you that you should not "fork", nor
  28. -telling you that you should stop calling wikis to "fork". This is only a
  29. -semantics opinion.
  30. +This blog post is not arguing that communities should avoid "forking",
  31. +nor that people should stop calling wikis to "fork". This is only an
  32. +opinion about terminology. It makes sense why "fork" started to be used,
  33. +but its perspective gives too much importance to the host and not enough
  34. +to the community behind the project.
  35.  
  36. -For the most part, wikis are considered to belong to the community that
  37. -builds it. [IANAL](https://en.wikipedia.org/wiki/IANAL), but legally it
  38. -belongs to the platform hosting it since they are granted a license for
  39. -each edit and stuff like that, but the project still belongs to the
  40. -community since they are the ones doing all the hard work. At least
  41. -that's how most editors would see it. Even Fandom has historically
  42. -shared this sentiment:
  43. +For the most part, wikis are considered to belong to the communities
  44. +that build them. [IANAL](https://en.wikipedia.org/wiki/IANAL), but
  45. +legally the hosting platform is generally granted a license to the
  46. +content contributed by editors. Even so, the project still belongs to
  47. +the community since they are the ones doing the work of building and
  48. +maintaining it. At least that's how most editors would see it. Even
  49. +Fandom has historically shared this sentiment:
  50.  
  51. - From [Community Central:Moving your wiki to FANDOM ยง Who will control
  52. the
  53. @@ -45,17 +46,16 @@ project itself to belong to the community, then the process of moving to
  54. a different host is not a *fork* just because the previous hosting
  55. platform keeps its own copy.
  56.  
  57. -If a community is choosing to move away, that's how we should call it: a
  58. -move. The project can hardly be called a fork when the previous hosted
  59. -wiki is not actively maintained by anyone; notice that I am not calling
  60. -it "the original wiki" or "the original version", because the project is
  61. -the same and is just changing its URL. The wiki community is not a copy
  62. -of itself, but it is the original members taking a decision for their
  63. -wiki. If all of the community is in with moving away, there's no
  64. -"original wiki" left behind but a [zombified
  65. +If a community chooses to move away, that's how we should call it: a
  66. +move. It is difficult to describe the project as a fork when the
  67. +previous host's copy is no longer actively maintained by anyone, because
  68. +the project itself has not changed, only the URL. The wiki community is
  69. +not a copy of itself, but it is the community's members making a
  70. +decision about their wiki. If the whole community moves together,
  71. +there's no "original wiki" left behind but a [zombified
  72. corpse](https://www.pcgamer.com/minecraft-wiki-completes-exit-from-fandom-gets-ready-to-fight-its-own-zombified-corpse/)
  73. -(and you should really try to move away with all the community in,
  74. -[avoid splitting the community as much as you
  75. +(and you should really try to move together as a community, [avoid
  76. +splitting it as much as you
  77. can](https://meta.weirdgloop.org/w/Leaving_Fandom/what_to_do_if_you're_not_an_editor#What_to_avoid)).
Add Comment
Please, Sign In to add comment