Guild Wars Wiki:Adminship and Guild Wars Wiki:Adminship/draft B: Difference between pages

From Guild Wars Wiki 中文站
(Difference between pages)
Jump to navigationJump to search
Page 1
Page 2
gww>Poke
(Applying accepted policy modification Guild Wars Wiki:Adminship/draft for standby admins)
 
gww>Poke
m (change for policy status template)
 
Line 1: Line 1:
{{Policy||[[GWW:ADMIN]]<br>[[GWW:RFB]]}}
{{Policy modification||Adminship}}
 
{{notice|This proposal has interactions with both "administrative action" and "explicit restriction" in other policies. The result as a whole should be considered with this proposed change.}}
Guild Wars Wiki is administered by the community. There are two types of formal administrator status: [[#Sysops|sysop]] and [[#Bureaucrats|bureaucrat]]. This status is not intended to represent extra weight within community decisions or generally directing the wiki, nor is it a requirement for moderating or enforcing policy. Like all users, administrators are expected to respect policy and consensus.
The English language Guild Wars Wiki is administered by the community. There are two types of formal administrator status: [[#Sysops|sysop]] and [[#Bureaucrats|bureaucrat]]. This status is not intended to represent extra weight within community decisions or generally directing the wiki, nor is it a requirement for moderating or enforcing policy. Like all users, administrators are expected to respect policy and consensus.


== Sysops ==
== Sysops ==
{{shortcut box|[[GWW:SYSOP]]}}
{{shortcut box|[[GWW:SYSOP]]}}
 
Sysops are users that are also granted technical access to [http://meta.wikimedia.org/wiki/Help:Administrators a few restricted features] (including blocking users and deleting pages), and the additional responsibility of not misusing them. When effecting a change that requires this access, a clear reason must be provided and the action must only be performed in these cases (or else be reversed):
Sysops are users that are also granted technical access to [http://www.mediawiki.org/wiki/Manual:Administrators a few restricted features] (including blocking users and deleting pages), and the additional responsibility of not misusing them. When effecting a change that requires this access, a clear reason must be provided and the action must only be performed in these cases (or else be reversed):
* As specifically noted in any written policy, e.g. deletion according to [[Guild Wars Wiki:Deletion policy|deletion policy]]. For this purpose, mentions of ''"administrative action"'' should be interpreted as an allowance of blocking/banning offenders.
* As specifically noted in any written policy, e.g. deletion according to [[Guild Wars Wiki:Deletion policy|deletion policy]]. For this purpose, mentions of ''"administrative action"'' should be interpreted as an allowance of blocking/banning offenders.
* In accordance with an arbitration [[Guild Wars Wiki:Arbitration policy#Rulings and enforcement|ruling]] or [[Guild Wars Wiki:Arbitration policy#Injunctions|injunction]].
* At their own discretion, whenever he or she believes it would be supported directly by community consensus (regarding the specific change/action). If going against what would normally be accepted as policy or going beyond usual sysop actions, the sysop is to note this action on the [[Guild Wars Wiki:Sysop discretion log|sysop discretion log]]. If this discretion is exercised and the expected consensus is seriously challenged by any user, an actual consensus needs to be established and implemented or the action(s) should be reverted. In challenged cases that break an explicit restriction, the action(s) are to be reverted while that consensus is not yet established.
* At their own discretion, whenever he or she believes it would be supported directly by community consensus (regarding the specific change/action). If going against what would normally be accepted as policy or going beyond usual sysop actions, the sysop is to note this action on the [[Guild Wars Wiki:Sysop discretion log|sysop discretion log]]. If this discretion is exercised and the expected consensus is seriously challenged by any user, an actual consensus needs to be established and implemented or the action(s) should be reverted. In challenged cases that break an explicit restriction, the action(s) are to be reverted while that consensus is not yet established.


== Bureaucrats ==
== Bureaucrats ==
{{shortcut box|[[GWW:BCRAT]]}}
{{shortcut box|[[GWW:BCRAT]]}}
Bureaucrats have sysop status as well as these additional powers and responsibilities:
* Altering the [http://www.mediawiki.org/wiki/Manual:User_rights#List_of_Groups assigned groups] and administrator status of user accounts based on community decisions, policy, or arbitration. This includes appointing or revoking sysops based on [[Guild Wars Wiki:Requests for adminship|requests for adminship]] and managing bot status. A clear reason has to be provided in the log when altering the user rights.
* The group of bureaucrats, as long as there are at least 2, forms an ''arbitration committee'', which is conducted according to [[Guild Wars Wiki:Arbitration policy|arbitration policy]]. The committee membership for each arbitration case is determined by the list of bureaucrats at the time of the request for arbitration (so gaining/losing bureaucrat status in the middle of a case does not result in joining/leaving the active committee for that case).
* They are expected to respond to any questions about their actions from anyone, including via e-mail. Each bureaucrat is required to give a publicly reachable e-mail address (shown on the [[Guild Wars Wiki:List of bureaucrats|list of bureaucrats]]).
*Bureaucrats may only use sysop powers to deal with an ongoing situation and if no normal sysop is available. Additionally, they may delete pages at any time in accordance with the deletion policy. Bureaucrats are only allowed to block in emergencies, specifically for edits that impair the ability of users to access wiki content, such as vandalism.


Bureaucrats are sysops that have the following additional powers and responsibilities:
Note that these bureaucrat-only functions are not subject to the same conditions as sysop actions.
# Update the group-level permission of users based on community decisions and policies. (See [http://www.mediawiki.org/wiki/Manual:User_rights#List_of_Groups the MediaWiki manual on user rights].)
#* This includes appointing or removing sysops according to formal [[GWW:RFA|requests for adminship or reconfirmation]].
#* Managing the status of wikibots.
# Provide a publicly-reachable e-mail address on the [[Guild Wars Wiki:List of bureaucrats|list of bureaucrats]].
# Resolve existing disputes and (where sensible) prevent them from taking place.
# Document their actions appropriately and respond to any questions from the community.


== Selection process ==
== Selection process ==
The sysop selection (and reconfirmation) process is governed by the [[Guild Wars Wiki:Requests for adminship|policy for requests for adminship]]. Other ways to lose sysophood include arbitration and voluntary resignation. One also gets sysop status temporarily during a term as bureaucrat.


Sysop selection and reconfirmation is governed by the [[Guild Wars Wiki:Requests for adminship|policy for requests for adminship]]. Sysops can resign their position at any time and can be removed by bureaucrat discretion if it serves the best interests of the community.
The bureaucrat selection process is governed by the [[Guild Wars Wiki:Elections|policy for elections]]. Bureaucrats are generally appointed for fixed terms of 6 months from their date of appointment, with the term periods being staggered to have a functional and unchanging subgroup during the transitions. Bureaucrats can only be removed before their term end by voluntary resignation (which may be done at any time) or by unanimous votes of the other bureaucrats (as long as there are at least 2 others).
 
Bureaucrats were chosen by election according to the [[Guild Wars Wiki:Elections|policy for elections]] until August 2012, at which point then-current bureacrats became permanent, subject to the same reconfirmation process as sysops. Vacated bureaucrat seats are filled as follows:
* A bureaucrat resigning their position in good terms may choose their own replacement from the community.
* If a bureaucrat is removed due to failed reconfirmation or otherwise leaves without naming a replacement, the remaining bureaucrats may choose one.
* In both cases, it is expected that the bureaucrat(s) open a discussion on the wiki for the community to offer input before the new bureaucrat is chosen.
* Anyone selected as bureaucrat who is not already a sysop must be confirmed according to the same RfA process as any other sysop.


ArenaNet is not formally involved in the administrator selection process except where explicitly specified, and community decisions may not be otherwise appealed to them. ArenaNet staff may participate in the administrator selection process just as any other contributor in good standing, but their opinions are given equal weight as other members of the community.
ArenaNet is not formally involved in the administrator selection process except where explicitly specified, and community decisions may not be otherwise appealed to them. ArenaNet staff may participate in the administrator selection process just as any other contributor in good standing, but their opinions are given equal weight as other members of the community.
== Standby Admins ==
With the maturity of the wiki, the low frequency and limited scope of game updates leading to reduced overall activity in recent years, and use of automated administrative tools, the need for everyday admin engagement on the wiki is less than in times past. In order to keep the admin team robust for times when they are needed, any admin may mark themselves with the 'Standby' status on the [[Guild Wars Wiki:List of administrators|admin list]], indicating that while they aren't regularly engaged in day-to-day affairs, they are willing to stay on-call to step in if contacted. Such admins should ensure that they have their site preferences set to notify them by e-mail when their user talk page is edited.
Should a Standby Admin have a period of extended "known unavailability" upcoming, where they will be unable to access the wiki; the admin should leave a note on their talk page indicating the period of intended absence, so as to ensure editors know not to attempt to contact them during this time and not to await a response. Periods of "known unavailability" should not extend beyond a combined period of 2 months per year.
Admins who do not respond to their talk page in a timely manner will be presumed to have retired from their adminship and their admin rights removed as a site security measure. The general expectation is that a standby admin should typically be responsive the same or next day, but 2 weeks will be given before removal of rights to accomodate unknown one-off circumstances. However, an admin who regularly takes several days or longer to respond may be subject to a call for [[Guild Wars Wiki:Requests for adminship#Reconfirmation|Reconfirmation]] at the community's discretion. If an admin hasn't been heard from in a while, even if no direct requests have been made of them, the community may attempt to contact them to establish that they remain contactable.
Should an admin return after presumed retirement and wish to resume admin duties, bureaucrats will use their discretion whether the rights should be immediately restored or a new [[Guild Wars Wiki:Requests for adminship|RFA]] is needed.


== See also ==
== See also ==
* [[Guild Wars Wiki:Admin noticeboard]]
* [[Guild Wars Wiki:Admin noticeboard]]
* [[Guild Wars Wiki:List of administrators]]
* [[Guild Wars Wiki:List of administrators]]
* [[Guild Wars Wiki:List of bureaucrats]]
* [[Guild Wars Wiki:Requests for technical administration]]
* [[Guild Wars Wiki:Requests for adminship]]
* [[Guild Wars Wiki:Sysop guide]]
* [[Guild Wars Wiki:Sysop guide]]