Global sysops/ar

From Meta, a Wikimedia project coordination wiki

This is a current proposal to enable global sysops on an opt-out basis on small wikis. For previous proposals, see the bottom of the page. To discuss the page, please see the talk page.

Global sysops have access to the sysop interface on wikis where this is permitted by policy (usually small wikis that do not have active local sysops available). These users have access strictly for maintenance and countering abuse; they have no editorial control over content or the local community.

Need help? See the Translation FAQ or Meta:Babylon. All translators should also subscribe to translators-l to be kept up-to-date (and to ask questions).

---

Contents 1 Scope 2 Election 3 Removal 4 Permissions 5 Communication 6 See also

[edit] Scope

By default, global sysop would be enabled for every project that meets one of the following criteria:

• fewer than ten administrators exist; or
• fewer than three administrators have made a logged action within the past two months.

Projects may opt-in or opt-out at their own discretion if they obtain local consensus. A wiki set will be used to give rights on the included wikis only.

[edit] Election

Requests should be placed on Steward requests/Global. The request will be approved by a steward if there is a consensus for the user to become a global sysop after a period of discussion, normally about two weeks' time. The discussion is not a vote; comments must present specific points in favor of or against the user's approval. Contributors to the discussion must have unified accounts with their Meta account.

[edit] Removal

Continued global sysop access depends on both activity and the continued support of the Wikimedia community.

Inactivity

Global sysops will automatically lose their access if it is unused for more than six months.

Vote of confidence

Any steward may remove a global sysop's rights at any time if they feel the tools have been misused, or if a request for comment has shown that a significant minority does not trust the global sysop. If this occurs and the global sysop wants the tools back, a vote of confidence shall occur, where the global sysop must retain the consensus of the community in order to return their access.

[edit] Permissions

This is the list of permissions with explanations which global sysops have. The permissions are nearly identical to those of regular administrators, however, these permissions apply to any Wikimedia Foundation project that has not opted-out of global sysops' access list. Global sysops also have access to Special:GlobalBlock, which local administrators do not have access to.

Block

• Block a user from sending e-mail (blockemail)
• Block other users from editing (block)
• Bypass IP blocks, auto-blocks and range blocks (ipblock-exempt)
• Bypass automatic blocks of proxies (proxyunbannable)

Global blocks

• Bypass global blocks (globalblock-exempt)
• Disable global blocks locally (globalblock-whitelist)
• Make global blocks (globalblock)
• Remove global blocks (globalunblock)

Delete

• Delete pages (delete)
• Mass delete pages (nuke)
• Not create redirects from source pages when moving pages (suppressredirect)
• Search deleted pages (browsearchive)
• Undelete a page (undelete)
• View deleted history entries, without their associated text (deletedhistory)

Protect/Edit

• Change protection levels and edit protected pages (protect)
• Edit other users' CSS and JS files (editusercssjs)
• Edit semi-protected pages (autoconfirmed)
• Edit the user interface (editinterface)

Abuse (Edit) Filter

• Modify abuse filters (abusefilter-modify)
• View detailed abuse log entries (abusefilter-log-detail)

Miscellaneous

• Have one's own edits automatically marked as patrolled (autopatrol)
• Not be affected by rate limits (noratelimit)
• Import pages from other wikis (import)
• Mark others' edits as patrolled (patrol)
• Mark rolled-back edits as bot edits (markbotedits)
• Move files (movefile)
• Move pages (move)
• Move pages with their subpages (move-subpages)
• Move root user pages (move-rootuserpages)
• Override files on the shared media repository locally (reupload-shared)
• Override the spoofing checks (override-antispoof)
• Override the title blacklist (tboverride)
• Overwrite existing files (reupload)
• Perform captcha triggering actions without having to go through the captcha (skipcaptcha)
• Quickly rollback the edits of the last user who edited a particular page (rollback)
• Upload files (upload)
• Use higher limits in API queries (apihighlimits)
• View a list of unwatched pages (unwatchedpages)

[edit] Communication

Global sysops must have user pages on every wiki they use their global sysop access on, which provides contact information or links to their primary user page (creation bot available).

If a user cannot resolve a dispute by talking to the global sysop, they can place a complaint on Talk:Global sysops.

[edit] See also

• All previous proposals

User groups
Local:	blocked user – anonymous user – registered user – bot – administrator – bureaucrat – oversight – checkuser
Global:	Abuse filter editors – locked account – unified account – bots – rollback – ombudsmen – sysop – system administrators – staff – steward – founder