Global Sysops

Other languages:

Global Sysops on 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 an action made by a Global Sysop such as a lock or block, or you need to request CVT intervention including local blocks and global locks, you can email cvtmiraheze.org (which also gets redirected to all Stewards) or you may make a new thread on the Stewards' noticeboard.

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 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

Technical capability

Members of Global Sysop global group can do, among other things:

View the abuse log
View detailed abuse log entries
Not be affected by IP-based rate limits
Have one's own edits automatically marked as patrolled
Edit pages protected as "Allow only autoconfirmed users"
Mark rolled-back edits as bot edits
Mark edits as minor
Move pages
Not have minor edits to discussion pages trigger the new messages prompt
Not be affected by rate limits
View recent changes patrol marks
Quickly rollback the edits of the last user who edited a particular page
Perform CAPTCHA-triggering actions without having to go through the CAPTCHA
Not create redirects from source pages when moving pages

Action log

A list of Global Sysops member's actions is located on cvtwiki. The page is on the read whitelist and visible to all users.

Eligibility criteria and requesting

Global Sysops are voted by users. However, the following conditions must be met in order for the user to be eligible to be voted. If these conditions are not met, the user may not be a candidate for globalsysop and any support votes will not matter. A candidate must:

Have at least 1000 total global edits on Miraheze (on more than one wiki, unless that wiki is Meta Wiki) (Note: These edits may not consist of directly copy/pasting content from other wikis, they must be edits done by the user);
Have had their Miraheze account for at least 2 months; and,
Be involved in some way in community matters (in discussions on Community noticeboard, etc.)

Appointment

To be elected Global Sysop, a request needs to be made at 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

In addition, Global Sysops are required to have two-factor authentication enabled on their user accounts in order to perform certain Global Sysop-restricted functions and may be demoted if they do not.

Revocation

Inactivity

Global Sysops 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.

Votes of no confidence

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 who predate the permissions request in question share their view
there is a support ratio of at least 50%
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 the Global Sysop, and it is not determined solely by the number of votes.

Emergency revocation

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.

Readdition of rights

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

Page last updated: 29 December 2022
Total number of Global Sysops: 2

+/-	User name	Languages spoken	Other rights	Libera Chat nickname on IRC
	MrJaroslavik	cs, sk-3, en-3	administrator
	Universal Omega	en-N	administrator, interface administrator, wiki creator, interwiki administrator, global rollbacker, system administrator	CosmicAlpha

Timeline of past and current Global Sysops

<translate>The following is a chart of <tvar name=1>global sysops/en</tvar></translate>.

Background

The following Requests for Comment have shaped this policy:

Requests for Comment/Miscellaneous RfGR and WC rules (amended) (June 2022)
Requests for Comment/CVT reform (amended, partly superseded) (May 2020)
Requests for Comment/CVT policy (amended, party superseded) (August 2019)
Requests for Comment/Changes to CVT group (amended, superseded) (May 2017)