管理员

From Meta
Jump to navigation Jump to search
This page is a translated version of the page Stewards and the translation is 11% complete.

Other languages:
English • ‎español • ‎italiano • ‎português do Brasil • ‎русский • ‎中文（中国大陆）‎ • ‎日本語


This page documents a Miraheze global policy, this policy follows consensus and/or Staff guidelines. All Miraheze users should follow it, and changes made to it should be discussed on the talk page.


Shortcut:

联系管理员，请参阅管理员告示板、向stewards at miraheze.org发邮件或者直接与下方列举的管理员联系。

Scope of responsibilities

Stewards are users with the permission and authority to use any part of the MediaWiki interface on any wiki. Stewards will work with communities to address issues facing them locally such as disputes, abusive or disruptive behaviour as well as global issues such as disruptive behaviour across multiple wikis. This includes global and local right assignment, use of routine administrator permissions (delete, blocking, etc.) on local wikis and in a global sense (locking accounts, renames), CheckUser and oversight permissions. In the event of an increase in requests for Steward assistance, Stewards may delegate some of these responsibilities to other users. As an example, routine administrator actions may be delegated to 'global sysops' or similar, if a need arises.

Appointment

Users may nominate themselves or other users to fulfill the Steward role, or the current Stewards may call for an election if they, as a group, decide more Stewards are needed. After an accepted nomination, self-nomination, or Steward-requested election, all Miraheze users will be allowed to comment on the nominee(s).

  • Users will be given an adequate time to comment on nominations
  • Any issues raised should be acknowledged or fixed by the nominee
  • If possible, any issues raised should be addressed before the closing of the nomination/election
  • Users may Support/Symbol neutral vote.svg Abstain/ Oppose nominees, but this alone will not decide the outcome
  • An existing Steward will close the nomination/election after taking into consideration the arguments made, not just the support/oppose count
  • For the nomination/election to be successful, there must be at least 20 user's comments and a support ratio of at least 80%

Removal & Readdition of rights

Inactivity

Stewards who do not participate in the community in some form (responding to questions, dealing with issues, administrative tasks on meta as a minimum) for 6 months will be deemed inactive and have their steward rights revoked. For the purpose of community, this includes all wikis and Phabricator.

This is and should be seen as a pretty relaxed requirement. Like everyone else here, Stewards are volunteers. Stewards should feel comfortable performing any of their responsibilities when it is possible for them to do so. Six months time should be enough time for any Steward logging in to acknowledge their responsibilities. This inactivity requirement is mainly to prevent having users with elevated access after they have moved on.

Readdition of rights

A Steward who lost their rights for any reason must successfully reapply for rights again per the appointment section above.

Revocation of rights

Stewards can have their permission revoked through a vote of no confidence or a request for removal.

  • The person starting the vote or opening the request must provide a valid reason for removal of Steward rights (mistrust, abuse, inactivity, etc.)
  • At least 20 users must comment on the vote of no confidence or request for removal (the same number of users required to appoint a Steward)

If at least 50% of user comments are for the removal of rights, then the Steward shall remove their own rights upon closure of the vote or have their rights removed by another Steward.

If Stewards as a group feel that a user is intentionally calling for votes of no confidence or requests for removal without valid reasons, Stewards may decide to ignore requests or votes started by said user. If there is actually an issue, another user may bring it up with the Stewards.

Term length

Stewards terms are not limited to a set time length. Users may call for a vote of non-confidence or request for removal at any time, as above.

List of Stewards

  • Page last updated: 21 8月 2018
User name Languages spoken Other rights
John en, cy-3 administrator, bureaucrat, system administrator
NDKilla en administrator, system administrator
Southparkfan nl, en-3 administrator, bureaucrat, system administrator
Void en, es-2
In the event of any differences in meaning between the original English version and a translation, the original English version takes precedence.
https://meta.miraheze.org/wiki/Stewards/zh-cn
meta.miraheze.org
crawl=CC-MAIN-2019-18
35358
application/http; msgtype=response
sha1:TJKTLVBPCUIB5KXOEICY7KS6DBFZJOQF
<urn:uuid:3088395a-583e-4d95-951d-8bc669ffddd6>
2019-04-19T16:59:51Z
107.191.126.23
text/html
sha1:IDBOKORRFY3VFXW2NMZ7IB3WNBYPTM6V
<urn:uuid:9fbfb330-5bc6-418f-aecf-fe6314260b9b>
https://meta.miraheze.org/wiki/Stewards/zh-cn
response
<urn:uuid:6d7240e1-3d31-4e0d-934d-b8d8cd044182>
isPartOf: CC-MAIN-2019-18
publisher: Common Crawl
description: Wide crawl of the web for April 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-165-178-231.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/