Global Sysops

Global Sysops on miraheze>Special:MyLanguage/Miraheze|Miraheze are users who assist Stewards in supporting the community and working with communities to address issues facing them locally as well as cleaning up vandalism, preventing it when possible and enforcing Miraheze's global policies.

Note however that they specifically do not have global access to read private wikis, or access any CheckUser or oversight tools.

If you have an issue with a lock/block made by a global sysop, or you need to request one you can email cvt@undefinedmiraheze.org (which also gets redirected to all stewards>Special:MyLanguage/Stewards|Stewards)

==

Local interference ==

Global sysops should only act in their capacity if:

There is disruption on a wiki and there are no local sysops or bureaucrats acting in a reasonable amount of time

The global abuse-log>Special:AbuseLog shows attempted spam that hasn't been dealt with by local sysops or bureaucrats

A request to intervene is made by a member of the local community

A global policy violation needs rectification and local sysops or bureaucrats aren't acting in a reasonable amount of time

If there is consensus, a wiki can request to wiki-set>Special:WikiSets/1|opt out of the group, which prevents global sysops from taking action on that wiki. Meta is currently opted out from Global sysops.

==

Technical capability ==

Members of  global group can do, among other things:

==

Action log ==

A list of Global Sysops member's actions is located action-log>mh:cvt:CVT action log|on cvtwiki. The page is on the read whitelist and visible to all users.

==

Appointment ==

To be appointed Global Sysop a request needs to be made at rfgr>Requests for global rights. The community can discuss (support/oppose/abstain/comment) the request. The request will be considered successful if:

at least 10 users share their view

there is a support ratio of at least 80%

a period of one week has passed since it started

==

Revocation ==

The global community can initiate a vote of no confidence or a request of removal at any time. In order for it to pass it needs to:

at least 10 users share their view

there is a support ratio of at least 80%

a period of one week has passed since it started

A vote of no confidence or request for removal must include a reason for why users are requesting the removal of a Global Sysop member, and it is not determined solely by the number of votes.

In the case of a blatant misuse of rights or an abuse of power, a Steward may remove a user from Global Sysop at their discretion without a community vote. If this happens, the user must undergo a no-confidence vote while their rights are temporarily removed, and their rights may only be added back if the no-confidence vote does not pass. This should only be used in extreme cases and should not substitute a no-confidence vote in non-urgent situations.

Global Sysops members who do not participate in Global Sysop duties in some form (countervandalism, locking abusive users, etc.) for 6 months will be deemed inactive and have their Global Sysop rights revoked by a Steward.

Once a Global Sysop has their rights revoked for any reason, they must make a successful request that satisfies the criteria above in order to regain the rights.

List of Global Sysops
==

See also ==

See gs-global-perms>Special:GlobalGroupPermissions/globalsysop|this page for a list of Global Sysops' global permissions

See gs-list>Special:GlobalUsers/globalsysop|this page for a list of members of the global group