User:Worm That Turned/Lightweight community desysop

At the moment, the sysop can be removed through a number of processes.

Process Criteria for desysop Does not require fresh request for adminship Requires fresh request for adminship
Inactivity No edits or admin activity for 1 year
Less than 100 edits in the past FIVE years
If the administrator has made an edit in the past TWO years AND
the administrator has taken an admin action the past FIVE years
If the administrator has been completely inactive for over TWO years OR
the administrator has taken no admin actions in the past FIVE years
Voluntary removal Request by subject (normally at Bureaurcrat's Noticeboard) For most reasons that the administrator chooses to resign their userright
as long as they do not exceed the inactivity limits
If the administrator chooses to remove the userright "under a cloud", i.e. whilst their actions are under scrutiny
If the administrator has agreed to removal due to a successful "recall"
If after voluntary removal, administrator subsequently fails activity requirements
For cause For cause request (by arbitrator or clerk) N/A If the administrator has the user-right removed by Arbcom.
This requires a case, except in certain circumstances.
Other Technically, the stewards or bureaucrats have the ability to remove the tools in an emergency. Also, Jimbo Wales could theoretically also remove administrator access at his discretion.


Timeline

Initial complaint
Lightweight system end
Arbcom case end
Initial discussion
Assign group
Group deliberations
Final decision
Initial discussion
Arbcom voting
Case opening
Evidence phase
Workshop phase
Proposed Decision Drafting
Proposed Decision Voting
Final decision
0
5
10
15
20
25
30
35
40
45
50
Comparison timeline in days


Idea

edit

Current Arbcom desysop process takes nearly 2 months. Multiple admins have recently left the encyclopedia when faced with it, more after going through it (c.f. recent cases open by arbcom on hold) Create a lightweight process - similar to Wikipedia:Administrators/RfC for BARC - a community desysopping process, which closed as no consensus with 115:77 in support.

Feedback from BARC

edit
Criticism
  • Don't need a second Arbcom
  • Bureaucrats weren't elected for this
  • No community making a decision
  • Too bureaucratic
  • Power from those who can be voted out to those who can't

Suggestion: Group of Peers below like opt in jury service. Bot to choose random eligible users.

  • Proposal not fleshed out enough
    Need to be ready to use before proposing. Make clear it can be altered in the future.
  • "We already have a process that works"
    Takes too long. Admins quitting if they're subjected to it.
Positive thing to keep
  • Gate keeper to stop frivolous complaints.



Group of peers

edit

The group should consist of 11 random users who meet all the following criteria:

  • Users who have added themselves to Category:Community desysop group of peers
  • Users who are currently active (at least 50 edits in the last 30 days)
  • Users who have made at least 1000 edits and 1 year of tenure
  • Users who are not currently blocked or partially blocked
  • Users who do not currently have any editing restrictions
  • Users who not INVOLVED with the administrator

When a request is started, a bot will scour the category for random users who meet the criteria, and put a message on the talk page of the first 11. Those users will then either accept being part of the group, or not - if not, or if no response in 24 hours, the bot will request more individuals.

This group of peers will deliberate make the final decision.