User Rights Reviews

In addition to wikibreaks and user activity, Spongebob456 also discussed the user rights reviews. Ths discussion involves the Quarterly User Rights Reviews, the mandatory user rights reviews that occur every 3 months. We introduced these in early 2017. The opening sentence of the proposal read "Some users believe that some members of the administration are no longer qualified due to inactivity, violations of the rules, etc." We already covered inactivity in a previous policy, which is not a huge problem. As far as violations of rules, the argument was that the process was too complicated.
In reality, we can easily make the process better, but this experience in holding quarterly user rights reviews have backfired, with good user getting demoted for inactivity. We have processes for demotion that can cover any large concerns we have. In fact, we have not had an "emergency user rights review" as they are now called, since the time we adopted the rules for mandatory periodic user rights reviews.
The quarterly user rights reviews have done more harm than good, and so we feel that they have run their course. It will relieve pressure from people. Along with reducing inactivity policies in another discussion, it should make ESB an easier place to contribute, without the pressures of demotion for volunteer positions. We understand that people have lives outside of ESB, but still want to contribute here, and make ESB the best that it can be. Therefore, we are proposing that we end mandatory quarterly user rights reviews. We can reform the other parts of the policy later, this is just to remove the mandatory quarterly reviews.
See original the original proposal here (the policies have changed several times since then.)
*ESB:Proposals/Administration Reviews
*ESB:Proposals/Administration Reviews/voting
===Changes to "Article XII: User Rights Reviews" bylaws===
*A. Quarterly User Rights Reviews
::*1. Every three (3) months, all bureaucrats, administrators, assistants, discussion moderators, and chat moderators will be put through a review process so the community can assess their status to ensure the most qualified people remain in their positions.
::*2. Administration reviews will occur four times per year, beginning on the following dates: February 10, May 10, August 10, and November 10.
::*3. If a user was promoted within one (1) week prior to the creation of the review, they will be exempt from the review.
::*4. The community shall vote on whether each promoted user should remain in their position or be demoted.
::*5. Each review period will last two (2) weeks. After two weeks, those users with a majority of all participants and participating administrators (more than 50%) supporting the removal of their position (excluding neutrals) will be subject to demotion.
:*6. Bureaucrats will discuss in private to determine the final verdict.
*B. Emergency User Rights Review
:*1. General
::*a. An Emergency User Rights Review may occur between the quarterly user rights reviews if a promoted user is abusing their powers and needs to be demoted.
::*b. In such a case, a promoted user may be suspended, pending review, in accordance with this section.
:::*i. In the event that a promoted user is not following the rules and/or are abusing their powers, a bureaucrat must inform them of their wrongdoing, in case of any misinterpretations.
:::*ii. If the promoted user does not stand down or admit to wrongdoing and thus the bureaucrat fails to resolve the issue, they may demote the promoted user for a suspension of one (1) week.
:::*iii. After the suspension (clause b, above), the said bureaucrat must then create an Emergency User Rights Review discussion.
:::*iv. Any administrator who is demoted after their adminship is terminated, obtains "former administrator" status.
::*c. Creating a User Rights Review discussion by any non-administrator to have another user demoted from any position is prohibited and will result in the deletion of that discussion.
:*2. Process
::*a. If a user feels that an administrator should be demoted, they must contact an administrator to make a request.
::*b. The administrators will discuss whether or not the promoted user in question should have a review discussion to let the community decide if that user should be demoted.
::*c. A majority of administrators must support a review discussion in order for it to be created in the first place. If it is determined that a majority of administrators do not support such a discussion taking place, the request is dropped.
::*d. Once a majority of administrators support the creation of a review discussion, they must notify the administrator in question to give them the following choices:
:::*i. Resign from the position. The administrators can then decide if that user should remain as an assistant or not if the user in question chooses to resign.
:::*ii. Write up a paragraph defending their keeping the position so that it can be presented before the demotion discussion begins. Once their defense has been submitted, the review discussion can be started immediately.
:::*iii. If the user does neither of these, the review discussion will be posted three (3) days after the user in question is notified.
::*e. Once the review discussion is posted, it will be in the following format.
:::*i. The administrators will list all the administrators who supported the creation of the discussion to show validation of the discussion.
:::*ii. Each user will have the opportunity to voice their opinion on the matter, summing up on what should be done, whether it is a complete demotion, demotion to another position, suspension, block, and/or combination.
:::*iii. After seven (7) days of discussion, the first stage will close. All listed options will be put up for a vote.
::*f. In order to terminate or suspend a bureaucrat or administrator, a majority of participating administrators (50% or more) and 70% of all participants must support the termination or suspension in order for it to be valid, not counting neutrals. The discussion must last no less than seven (7) days. The promoted user in question does not have a vote or is counted in the percentage for the decision but may make comments.
::*g. If the termination is successful, the terminated user cannot be repromoted unless they go through a successful request process.
::*h. If the termination is unsuccessful, another demotion discussion cannot take place until one (1) month after the close of the preceding demotion discussion.
----
Additional note: upon passing of this policy, all lettering shall be adjusted (1,2,3-->A,B,C; abc-->123; i,ii,iii-->abc; etc.)