Jump to content

Wikiteknokrati

From Meta, a Wikimedia project coordination wiki
This page is a translated version of the page Wikitechnocracy and the translation is 43% complete.
Gemenskap
Anti-wiki
Konfliktdriven syn
Falsk gemenskap
Wikikultur
Wikitro
Wikiprocessen
Wikins väg
Darwikinism
Maktstruktur
Wikianarkism
Wikibyråkrati
Wikidemokrati
WikiDemokrati
Wikidespotism
Wikifederalism
Wikihierarki
Wikimeritokrati
Wikiindividualism
Wikioligarki
Wikiplutokrati
Wikirepublikanism
Wikiskepticism
Wikiteknokrati
Samarbete
Antifraktionering
Fraktionering
Socialt
Exopedianism
Mesopedianism
Metapedianism
Övergripande innehållsstruktur
Transclusionism
Antitransclusionism
Kategorism
Strukturism
Encyklopediska standarder
Deletionism
Delusionism
Exclusionism
Inclusionism
Precisionism
Precision-Skeptics
Notability
Essentialism
Incrementalism
Artikellängd
Mergism
Separatism
Measuring accuracy
Eventualism
Immediatism
Miscellaneous
Antiovertranswikism
Mediawikianism
Post-Deletionism
Transwikism
Wikidynamism
Wikisecessionism
Redirectionism

Wikiteknokrati förespråkar att Wikipedia och andra instanser i wikisfären ska vara aktiva teknokratier som investerar makt och auktoritet i tekniska experter i deras respektive fält.

Det favoriserar centraliserat, ibland wikihierarkiskt ledarskap snarare än utveckling genom decentraliserad, wikidynamisk process av spontana order.

An example of a wikitechnocratic body is the bot approval group; its reason for being is that most members of the community do not understand bots, and therefore are not well-equipped to make bot approval decisions.

One of the arguments for wikitechnocracy is that it takes time for the community to reach consensus, and in the meantime progress is held up.

Sometimes, the community may never reach consensus, and the system permanently stagnates on that issue.

The Wikimedia Foundation and its developers have played a major leadership role in helping technical and other standards emerge in the wikisphere. For example, the mw:coding conventions page lists practices that are expected to be followed in all code checked into git, and the system of +2 approvers ensures that there is an orderly system of deciding what should go in the core. This has been influential on the technical aspects of the wikisphere.