Szerkesztői csoportok

This page is a translated version of the page User groups and the translation is 56% complete.
Outdated translations are marked like this.

The following is a list of user groups in the Wikimedia Foundation projects. It is organized in approximate descending order of permissions. Note that the order is not directly correlated to power in the proper sense of the word, but rather refers to technical access in the MediaWiki software. Be aware that, though the technical abilities are the same on all Foundation projects, certain groups' definitions and roles differ from wiki to wiki.

Helyi csoportok

Alább látható a csoportok listája jogosultság szerint csökkenő sorrendben:

Globális szerkesztőcsoportok

Lásd még a Globális engedélyek , Globális csoportok és a Globális jogok lapot.

Globális bot

Global bots have bot access on all wikis where global bots are enabled (this must be explicitly permitted by local policy; see a list of allowing wikis). Global bots are subject to the standard bot policy, which limits these bots to specific tasks.

Globális visszaállítók

A globális visszaállítók bármely wikin tömegével állíthatnak vissza vandalizmust és tesztszerkesztést egy kattintással. A jog megadásához bizonyítani kell a wikiközi vandalizmus-elhárításban szerzett tapasztalatokat.

Lásd:

Globális adminisztrátor

A globális adminisztrátorok azon kisebb wikiken működnek közre, ahol nincsenek helyi adminisztrátorok. A jogosultság megadása az SRGP lapon folytatott hosszas megbeszélés után lehetséges.

Lásd:

OTRS-kezelők

VRT permissions agents are users who have access to the permissions queues of the Wikimedia VRTS. The global group is used primarily for identification purposes, and the only user right it contains is the ability to activate two factor authentication.

Alkalmazottak

A csoportot a Wikimédia Alapítvány egyes fizetett munkatársaihoz rendeljük hozzá, amely műszaki és jogi célból különleges engedélyeket ad.

Háttér

The Wikimedia Foundation is constantly evaluating who is a member of the staff user group in order to minimize the proliferation of this very specialized tool. Membership of the staff group is constantly re-evaluated, particularly in light of a more limited tool being available that will fit a staff member's needs, if someone is expected to not need staff rights for a period of time, or if there is something that triggers during a risk assessment. These re-evaluations are part of good security practices.

Previously, who did and did not have staff rights was relatively arbitrary, based upon asking the staff member who was in charge of these rights. The process has been subsequently formalized to protect against abuse or misuse of staff rights. In order to receive staff rights, it requires second level sign-off (meaning that for a new employee in a department, director level signoff is required and for a new manager, C-level signoff is required), a formal written use-case that is kept on file and routinely reviewed to determine whether the use-case is still met by assignment of staff rights, a brief training session explaining their appropriate and inappropriate use, and an acknowledgement (in writing) of the rights and responsibilities that come with staff rights.

Previously, there were few protections against abuse. Today, there are a number of checks and balances built into the system. On the English Wikipedia, for instance, the Arbitration Committee reviews all logged actions and discusses questionable actions with Jan (as the WMF employee responsible for approving rights assignments) to ensure they are within policy. On other wikis where there is no comparable subcommittee, the Trust and Safety (T&S) team audits and reviews employee actions. This has resulted in employee disciplinary action on occasion. These are not toothless protections.

Assignment

Staff rights are managed by the Lead Manager of Trust and Safety and the second-level Wikimedia Foundation manager of the person requesting staff rights.

Wikimedia stewards and staff will add or remove permissions (former link) from the staff global user group and they also add or remove user accounts from the staff global user group based on the requests of the Lead Manager of Trust and Safety or their designee. There is no requirement that community consensus be demonstrated or that the above requirements (including sign-offs) are proved.

Rationale and responsibility of advanced permissions assignment for Wikimedia Foundation staff are currently recorded in a locked Google spreadsheet. A mirror of that page can be found at WMF Advanced Permissions.

Jogosultságok

A következő lista összefoglalja az alkalmazottak jogosultságait és elmagyarázza ezek szükségességét.

Szerkesztői jogosultság Cél
autoconfirmed ...
autopatrol ...
bigdelete At times, the T&S or technical team need the ability to delete pages with a high number of revisions for technical reasons, or for legal compliance reasons.
browsearchive ...
centralauth-merge ...
centralauth-unmerge ...
centralnotice-admin ...
checkuser The T&S team uses this right for legal compliance (subpoena, etc.) and safety reasons (investigations of threats)
checkuser-log The T&S team uses this right for legal compliance (subpoena, etc.) and safety reasons (investigations of threats)
delete The T&S team uses this right for legal compliance and copyright purposes.
deletedhistory The T&S team uses this right for legal compliance and copyright purposes.
deletedtext The T&S team uses this right for legal compliance and copyright purposes.
deletelogentry The T&S team uses this right for legal compliance purposes.
deleterevision The T&S team uses this right for legal compliance and copyright purposes.
edit ...
editinterface The T&S team uses this right for legal compliance and copyright purposes (i.e., to change the copyright notices, etc.). Other staff members use it to support the development of other projects and technical initiatives.
editusercss This was done for a couple of reasons.

First, we have had times when we saw a user insert some code in their own user.js and user.css files that really shouldn't be there, and then propagate that code out to the wikis by adding a transclusion from their own user files to, for instance, Mediawiki:Common.js of a smaller wiki, and thereby add google tracking code, for instance. This allows staff to easily (and in a logged fashion) remove such code.

Second, in order to include a script for those users who hold staff rights which colors red the interface buttons for things that they really shouldn't touch without a REALLY good reason (i.e., the execute checkuser button). You can see that script in my own user.js file. This is a reminder for new staff who didn't come from the community that these are specialized rights, and not everyone has access to them, and serves as a mental "speedbump" against using them.

editusercssjs
edituserjs
globalblock ...
globalblock-exempt ...
globalblock-whitelist ...
globalunblock ...
hiderevision ...
hideuser ...
import ...
importupload ...
ipblock-exempt ...
moodbar-admin ...
move ...
move-rootuserpages ...
move-subpages ...
movefile ...
noratelimit ...
nuke ...
override-antispoof ...
oversight ...
prefstats ...
protect ...
purge ...
reupload ...
reupload-shared ...
superprotect ...
suppressionlog ...
suppressredirect ...
suppressrevision ...
tboverride ...
tboverride-account ...
transcode-reset ...
transcode-status ...
uboverride ...
unblockself ...
undelete ...
unwatchedpages ...
upload ...
upload_by_url ...

Lásd:

Intéző

Az intézők a wikifelület egészéhez hozzáférhetnek, és a közösségi konszenzust követően végrehajthatnak műszaki módosításokat, eljárhatnak vészhelyzetekben és küzdhetnek a wikiközi vandalizmus ellen. Az intézőválasztás évente zajlik, ahol minden wikiről érkeznek szavazók.

Lásd:

<span id="Special-purpose ">

Különleges globális jogosultságok

Jegyzetek

  • ToolLabs – szerkesztői csoportok, amelyek nem minden wikin léteznek (az érintett projektek jelezve vannak)

Lásd még