RfA is... not broken, but not well.
I've recently rewritten this proposal from its original form. It was then modified by Xeno.
There are two sides to the problem with the current request for adminship process:
Create a process for de-sysopping (for lack of a better phrase, an RfDA) that is roughly similar to the process for gaining adminiship.
One of the reasons that this idea (a process for de-sysopping) hasn't gone forward is that, being Wikipedians, we just love to discuss and analyze every damn thing. Page after page after page of discussion and we've gotten nowhere. Why? Because we're overthinking.
Let's implement the de-sysopping process similar to the current RfA system. People propose someone be de-sysopped; if the proposal is deemed valid, the request is up for a week for questions and feedback from the community - and then bureaucrats gauge consensus. Keep it simple.
In summary, the process is initiated once a user prepares a request for de-adminship page, the request is seconded by another editor, and the candidate is notified of the request. The candidate is given one week to make a statement after which the request may submitted for certification. At least 48 hours after being submitted for certification, a bureaucrat will determine if the request has been certified and either close it as not certified or open the discussion for community questions and comment. This discussion lasts at least 7 days, at which point a bureaucrat will open a bureaucrat discussion lasting at least 48 hours in which bureaucrats gauge community consensus. Finally, a bureaucrat will close the bureaucrat discussion and implement the consensus decision.
The prerequisites to submit an RfDA request for certification are:
Once the RfDA sub-page is created and a candidate has been given one week to make a statement and arrange scheduling, it may be posted by a bureaucrat for a 48-hour certification period unless it obviously does not meet the prerequisites.
During the certification phase, community members are invited to provide their opinion on whether the prerequisites have been met.
It is important to note that the certification process is not about whether the candidate should remain an administrator, but only if the prerequisites to submit the request have been met. A user may certify the request yet still opine in the later phase to retain the administrator, and indeed if a participant feels strongly that the candidate should remain an administrator they should not oppose certification on these grounds alone - only on the grounds that the request has not met the prerequisites. Comments rejecting certification on these grounds alone may be weighed accordingly by the bureaucrat processing the certification.
Similarly, a participant should not certify a request if they feel the prerequisites have not been made out (even if they feel the candidate should not remain an administrator). The certification process is in place to ensure that requests for de-adminship do not proceed without evidence of recent and ongoing behaviour incompatible with adminship coupled with prior attempts at dispute resolution. As above, comments will be weighed accordingly.
Questions may be raised in the certification discussion but these questions should remain focused on the certification process; if certified, there will be an opportunities for questions of a wider scope.
Once the minimum certification period has elapsed, a bureaucrat will determine if the request has been certified by the community. If the bureaucrat determines the request has been certified, the request moves into the opinion phase; if not, it is closed.
Questions about certification decisions should be raised with the bureaucrat in question first, and bureaucrats noticeboard if necessary.
Once certified, a bureaucrat will open the opinion phase which is similar to an RfA:
The 7 day period is merely a minimum; the request remains open for comment until placed on hold by a bureaucrat and may be extended at bureaucrat discretion.
After at least 7 days have elapsed, a bureaucrat will place the discussion on hold and open a bureaucrat discussion which will remain open for at least 48 hours.
Uninvolved bureaucrats will review the RfDA and provide their comments as to whether community consensus exists to withdraw administrative privileges (not whether they personally feel the candidate should remain an administrator).
After at least 48 hours have elapsed, a bureaucrat will review the bureaucrat discussion to determine consensus among the bureaucrats and implement the decision. If the consensus is not obvious, the discussion should be closed by a bureaucrat who did not participate in the bureaucrat discussion.
RfA is... not broken, but not well.
I've recently rewritten this proposal from its original form. It was then modified by Xeno.
There are two sides to the problem with the current request for adminship process:
Create a process for de-sysopping (for lack of a better phrase, an RfDA) that is roughly similar to the process for gaining adminiship.
One of the reasons that this idea (a process for de-sysopping) hasn't gone forward is that, being Wikipedians, we just love to discuss and analyze every damn thing. Page after page after page of discussion and we've gotten nowhere. Why? Because we're overthinking.
Let's implement the de-sysopping process similar to the current RfA system. People propose someone be de-sysopped; if the proposal is deemed valid, the request is up for a week for questions and feedback from the community - and then bureaucrats gauge consensus. Keep it simple.
In summary, the process is initiated once a user prepares a request for de-adminship page, the request is seconded by another editor, and the candidate is notified of the request. The candidate is given one week to make a statement after which the request may submitted for certification. At least 48 hours after being submitted for certification, a bureaucrat will determine if the request has been certified and either close it as not certified or open the discussion for community questions and comment. This discussion lasts at least 7 days, at which point a bureaucrat will open a bureaucrat discussion lasting at least 48 hours in which bureaucrats gauge community consensus. Finally, a bureaucrat will close the bureaucrat discussion and implement the consensus decision.
The prerequisites to submit an RfDA request for certification are:
Once the RfDA sub-page is created and a candidate has been given one week to make a statement and arrange scheduling, it may be posted by a bureaucrat for a 48-hour certification period unless it obviously does not meet the prerequisites.
During the certification phase, community members are invited to provide their opinion on whether the prerequisites have been met.
It is important to note that the certification process is not about whether the candidate should remain an administrator, but only if the prerequisites to submit the request have been met. A user may certify the request yet still opine in the later phase to retain the administrator, and indeed if a participant feels strongly that the candidate should remain an administrator they should not oppose certification on these grounds alone - only on the grounds that the request has not met the prerequisites. Comments rejecting certification on these grounds alone may be weighed accordingly by the bureaucrat processing the certification.
Similarly, a participant should not certify a request if they feel the prerequisites have not been made out (even if they feel the candidate should not remain an administrator). The certification process is in place to ensure that requests for de-adminship do not proceed without evidence of recent and ongoing behaviour incompatible with adminship coupled with prior attempts at dispute resolution. As above, comments will be weighed accordingly.
Questions may be raised in the certification discussion but these questions should remain focused on the certification process; if certified, there will be an opportunities for questions of a wider scope.
Once the minimum certification period has elapsed, a bureaucrat will determine if the request has been certified by the community. If the bureaucrat determines the request has been certified, the request moves into the opinion phase; if not, it is closed.
Questions about certification decisions should be raised with the bureaucrat in question first, and bureaucrats noticeboard if necessary.
Once certified, a bureaucrat will open the opinion phase which is similar to an RfA:
The 7 day period is merely a minimum; the request remains open for comment until placed on hold by a bureaucrat and may be extended at bureaucrat discretion.
After at least 7 days have elapsed, a bureaucrat will place the discussion on hold and open a bureaucrat discussion which will remain open for at least 48 hours.
Uninvolved bureaucrats will review the RfDA and provide their comments as to whether community consensus exists to withdraw administrative privileges (not whether they personally feel the candidate should remain an administrator).
After at least 48 hours have elapsed, a bureaucrat will review the bureaucrat discussion to determine consensus among the bureaucrats and implement the decision. If the consensus is not obvious, the discussion should be closed by a bureaucrat who did not participate in the bureaucrat discussion.