Meta:Interface administrators: Difference between revisions
Redirected page to Meta:User groups#Interface administrators Tag: New redirect |
→Appointment: revise Tag: Mobile |
||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Meta policy}} | |||
'''[[Interface administrators]]''' on Meta are local users with the ability to edit sitewide CSS and JS pages and other users' personal CSS/JS pages. | |||
Editing CSS/JS that gets executed in other users' browsers is very powerful and potentially dangerous in the hands of a malicious user; interface administrators should be users who are highly trusted, have at least a basic understanding of CSS and JS, are aware of the privacy expectations of wikis, and have a good understanding of account security. | |||
On Meta, some CSS and JavaScript pages (such as [[MediaWiki:Global.css]]) also have global effects, and interface administrators can edit these as well. | |||
== Appointment == | |||
After discussion on [[Meta:Requests for permissions]], interface administrators may be appointed on Meta, either temporarily or indefinitely. Candidates must: | |||
* Have a user page on Meta. | |||
* Have a valid contact address (either a confirmed email address in preferences or a valid email address on the user page). | |||
* Be an active contributor on Meta (this is a subjective, not objective, measure; there is no official edit count). | |||
* Enable [[Help:2FA|two-factor authentication]]. | |||
Adminship is not a strict requirement for interface adminship, but it may be used as a factor in determining whether a user is sufficiently trusted and experienced for the interface administrator role. | |||
== Removal == | |||
[[Meta:Bureaucrats|Bureaucrats]] are authorized to remove interface administrator access in the following cases: | |||
* No local edits or logged actions for 1 year. | |||
* Reasonable suspicion of [[account compromise]] or abuse of the tool. | |||
* Consensus on the community portal. | |||
* When an interface administrator has resigned. | |||
* When an account does not meet or no longer meets the two-factor authentication requirement. | |||
[[Stewards]] may also use their discretion to remove the permission: | |||
*When the authentication or inactivity requirement is not met and no bureaucrat action is forthcoming. | |||
*In emergencies to protect the best interests of the WickedGov sites. |
Latest revision as of 19:54, 22 April 2025
![]() | This page documents an official policy on WickedGov Meta-Wiki. It represents broad consensus, and compliance is mandatory for all users. It should not be modified without prior community approval. |
Interface administrators on Meta are local users with the ability to edit sitewide CSS and JS pages and other users' personal CSS/JS pages.
Editing CSS/JS that gets executed in other users' browsers is very powerful and potentially dangerous in the hands of a malicious user; interface administrators should be users who are highly trusted, have at least a basic understanding of CSS and JS, are aware of the privacy expectations of wikis, and have a good understanding of account security.
On Meta, some CSS and JavaScript pages (such as MediaWiki:Global.css) also have global effects, and interface administrators can edit these as well.
Appointment[edit source]
After discussion on Meta:Requests for permissions, interface administrators may be appointed on Meta, either temporarily or indefinitely. Candidates must:
- Have a user page on Meta.
- Have a valid contact address (either a confirmed email address in preferences or a valid email address on the user page).
- Be an active contributor on Meta (this is a subjective, not objective, measure; there is no official edit count).
- Enable two-factor authentication.
Adminship is not a strict requirement for interface adminship, but it may be used as a factor in determining whether a user is sufficiently trusted and experienced for the interface administrator role.
Removal[edit source]
Bureaucrats are authorized to remove interface administrator access in the following cases:
- No local edits or logged actions for 1 year.
- Reasonable suspicion of account compromise or abuse of the tool.
- Consensus on the community portal.
- When an interface administrator has resigned.
- When an account does not meet or no longer meets the two-factor authentication requirement.
Stewards may also use their discretion to remove the permission:
- When the authentication or inactivity requirement is not met and no bureaucrat action is forthcoming.
- In emergencies to protect the best interests of the WickedGov sites.