Wikipedia:Demoting inactive admins

From Wikipedia, the free encyclopedia

This proposal was rejected by the community. It has not gained consensus and seems unlikely to do so. Per Wikipedia:Policies and guidelines: "A rejected page is any proposal for which consensus support is not present, regardless of whether there's active discussion or not."

Fixed a bit of typing, please see the talk page for further discussion.

1 Inactive Bureaucrat Policy Proposal
2 Inactive Sysop Policy Proposal
3 Inactive Checkuser Policy Proposal
4 Inactive Oversight Policy Proposal
5 Discussion

[edit] Inactive Bureaucrat Policy Proposal

Inactive Bureaucrats with 0 logins in the past 90 days will have access suspended to the tools. They may re-obtain access after logging in and requesting it.
Inactive Bureaucrats with 0 use of tools in 120 days will lose Bureaucrat access and be reverted to Sysop. They may re-apply via RfB normal procedures.
This policy will not apply to Bureaucrats who notify the community of a Wikibreak.

[edit] Inactive Sysop Policy Proposal

Inactive Sysops with 0 logins in the past 90 days will have access suspended to the tools. They may re-obtain access via request.
Inactive Sysops with 0 use of tools in 120 days will lose Sysop access and be reverted to regular user. They may re-obtain access via request.
This policy will not apply to Sysops who notify the community of a Wikibreak.

[edit] Inactive Checkuser Policy Proposal

Inactive Checkuser clerks with 0 logins in the past 30 days will have access suspended to Checkuser, they may re-obtain access via request.
This policy will apply to clerks who notify the community of a Wikibreak.

[edit] Inactive Oversight Policy Proposal

Inactive oversight admins with 0 logins in the past 30 days will have access suspended to Oversight, they may re-obtain access via request.
This policy will apply to oversight admins who notify the community of a Wikibreak.

The status of these sysops, and bureaucrats will be monitored by a WMF controlled bot operated by the WMF, Stewards, and the Developers. The status will actually be removed by a Stewards, not a bot; after being manually confirmed.