User:Spongebob456/User rights policy write-up

Eligibility

Generally, a user seeking promotion must demonstrate that all their contributions are positive, and further the goal of improving the wiki. They must demonstrate understanding of the how the wiki operates, familiarity with the policies, proper use of spelling and grammar, and they must also show they can hold the position with maturity. The community shall make an assessment on whether or not the user shall be promoted based on their standards that includes these as well as others. They must also demonstrate good reasons for any questionable contributions.

The requirements for all positions are:

a. At least one (1) month must have passed since the user's first edit.
b. The user must have at least one hundred (100) edits, of which at least fifty (50) are main namespace edits.
c. The user must have a clean block record for at least three (3) months, not counting invalid blocks.
~~d. The user must have support from the active administrators.~~
e. The user must have support from the active bureaucrats. If the request fails to do so, it requires 75% support of administrators who are not bureaucrats for the request to pass unless otherwise stated.
d. If the nominee has a rate of support of 80% or above, the rights are granted.
e. If the nominee has a rate of support between 70% and 80%, bureaucratic discretion is to be used in determining whether rights are granted. Arguments from the votes provided and the responses of the nominee to questions will be considered.
f. If the nominee has a rate of support of 70% or below, the rights are not granted.
g. All votes must have at reasons. Votes without reasons and votes without good reasons (eg, "I don't like him") will be stricken, with a note for the user to add a reason applied. Admins may mediate a conflict around a vote and make a judgment on whether it should be stricken or not.

User Rights Reviews

A. Biannual User Rights Reviews

1. Every six (6) months, all bureaucrats, administrators, assistants, discussion moderators and Discord moderators are 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 twice per year, beginning on the following dates: April 15 and October 15
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, 80% of all participants must support the termination or suspension, including a majority of participating administrators (in case of support rate at 50%) not counting neutrals, in order for the user to be subject to demotion.
6. Bureaucrats will discuss in private to determine the final verdict.

e. In order to terminate or suspend a crew member, ~~70%~~ The discussion must last no less than seven (7) days. The promoted user in question does not have a vote and is not counted in the percentage for the decision but may make comments.

B. Emergency User Rights Reviews

2. Process

a. If a promoted user is deemed to have met the conditions to have an emergency rights review created for them outlined above, then the bureaucrats and 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.
b. All active bureaucrats and a majority of the active administrators must support a review discussion in order for it to be created in the first place. If it is determined that this is not the case, the request is dropped and the promoted user retains their rights.
c. Once all bureaucrats support the creation of a review discussion, they must notify the promoted user in question to give them the following choices:

i. Resign from your current position. The bureaucrats can then decide whether this user should remain: an administrator, if this is a bureaucrat, or an assistant, if this user was an administrator.
ii. If the user does not do so, they will be given the opportunity to write a defense for themselves to be posted in the user rights review, and the review discussion will be published three (3) days after the relevant user is notified, regardless of whether or not the user has provided a defense.

d. Once the review discussion is posted, it will be in the following format.

i. Each user will have the opportunity to voice their opinion on the matter, summing up what they believe should be done, whether it is a complete demotion, demotion to another position, suspension, block, and/or combination.
ii. After seven (7) days of discussion, the first stage will close. All listed options will be put up for a vote.

e. In order to terminate or suspend a crew member, ~~70%~~ 80% of all participants must support the termination or suspension in order for it to be valid, including a majority of participating administrators (in case of support rate at 50%), not counting neutrals. The discussion must last no less than seven (7) days. The promoted user in question does not have a vote and is not counted in the percentage for the decision but may make comments.
f. If the termination is successful, the promoted user will be demoted, suspended, blocked, and/or combination. The promoted user will only be able to apply for the rights fourteen (14) days after the Emergency User Rights Review was archived.
g. If the termination is not successful, the promoted user retains their rights on the same basis as any other user with those user rights.

ESB:User rights policy

A. Biannual User Rights Reviews

1. Every six (6) months, all bureaucrats, administrators, assistants, discussion moderators and Discord moderators are 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 twice per year, beginning on the following dates: April 15 and October 15.
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, 80% of all participants must support the termination or suspension, including a majority of participating administrators (in case of support rate at 50%) not counting neutrals, in order for the user to be subject to demotion.
6. Bureaucrats will discuss in private to determine the final verdict.

B. Emergency User Rights Reviews

2. Process

a. If a promoted user is deemed to have met the conditions to have an emergency rights review created for them outlined above, then the bureaucrats and 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.
b. All active bureaucrats and a majority of the active administrators must support a review discussion in order for it to be created in the first place. If it is determined that this is not the case, the request is dropped and the promoted user retains their rights.
c. Once all bureaucrats support the creation of a review discussion, they must notify the promoted user in question to give them the following choices:

i. Resign from your current position. The bureaucrats can then decide whether this user should remain: an administrator, if this is a bureaucrat, or an assistant, if this user was an administrator.
ii. If the user does not do so, they will be given the opportunity to write a defense for themselves to be posted in the user rights review, and the review discussion will be published three (3) days after the relevant user is notified, regardless of whether or not the user has provided a defense.

d. Once the review discussion is posted, it will be in the following format.

i. Each user will have the opportunity to voice their opinion on the matter, summing up what they believe should be done, whether it is a complete demotion, demotion to another position, suspension, block, and/or combination.
ii. After seven (7) days of discussion, the first stage will close. All listed options will be put up for a vote.

e. In order to terminate or suspend a crew member, ~~70%~~ 80% of all participants must support the termination or suspension in order for it to be valid, including a majority of participating administrators (in case of support rate at 50%), not counting neutrals. The discussion must last no less than seven (7) days. The promoted user in question does not have a vote and is not counted in the percentage for the decision but may make comments.
f. If the termination is successful, the promoted user will be demoted, suspended, blocked, and/or combination. The promoted user will only be able to apply for the rights fourteen (14) days after the Emergency User Rights Review was archived.
g. If the termination is not successful, the promoted user retains their rights on the same basis as any other user with those user rights.

ESB:Requests for assistant

Requirements

Per the eligibility section of the promotion policy, the requirements are:

a. At least three (3) months must have passed since the user's first edit.
b. The user must have at least 1,000 edits, of which at least five hundred (500) are main namespace edits.
c. The user must have a clean block record for at least three (3) months, not counting invalid blocks.
~~d. The user must have support from a majority of all administrators.~~
e. The user must have support from a majority of all bureaucrats. If the request fails to do so, it requires 75% support of administrators who are not bureaucrats for the request to pass unless otherwise stated.
d. If the nominee has a rate of support of 80% or above, the rights are granted.
e. If the nominee has a rate of support between 70% and 80%, bureaucratic discretion is to be used in determining whether rights are granted. Arguments from the votes provided and the responses of the nominee to questions will be considered.
f. If the nominee has a rate of support of 70% or below, the rights are not granted.
g. All votes must have at reasons. Votes without reasons and votes without good reasons (eg, "I don't like him") will be stricken, with a note for the user to add a reason applied. Admins may mediate a conflict around a vote and make a judgment on whether it should be stricken or not.

ESB:Requests for adminship

Requirements

Per Section B of the promotion policy, the requirements are:

a. The user must be a current assistant for at least two (2) months.
b. The user must have at least 2,000 edits, of which at least 1,000 are main namespace edits.
c. The user must have a clean block record for at least six (6) months, not counting invalid blocks.
~~d. The user must have support from a majority of all administrators.~~
e. The user must have support from a majority of all bureaucrats. If the request fails to do so, it requires 75% support of administrators who are not bureaucrats for the request to pass unless otherwise stated.
d. If the nominee has a rate of support of 80% or above, the rights are granted.
e. If the nominee has a rate of support between 70% and 80%, bureaucratic discretion is to be used in determining whether rights are granted. Arguments from the votes provided and the responses of the nominee to questions will be considered.
f. If the nominee has a rate of support of 70% or below, the rights are not granted.
g. All votes must have at reasons. Votes without reasons and votes without good reasons (eg, "I don't like him") will be stricken, with a note for the user to add a reason applied. Admins may mediate a conflict around a vote and make a judgment on whether it should be stricken or not.

ESB:Requests for bureaucrat

Requirements

Per Section B of the promotion policy, the requirements are:

a. The user must be a current administrator for at least one (1) year.
b. The user must have at least 4,000 edits, of which at least 2,000 are main namespace edits.
c. The user must have a clean block record for at least one (1) year, not counting invalid blocks.
d. The user must demonstrate good reasons for any questionable edits.
~~e. The user must have support from a majority of all administrators.~~
~~f. The user must have full support from all bureaucrats.~~
d. If the nominee has a rate of support of 80% or above, the rights are granted.
e. If the nominee has a rate of support between 70% and 80%, bureaucratic discretion is to be used in determining whether rights are granted. *Arguments from the votes provided and the responses of the nominee to questions will be considered.
f. If the nominee has a rate of support of 70% or below, the rights are not granted.
g. All votes must have at reasons. Votes without reasons and votes without good reasons (eg, "I don't like him") will be stricken, with a note for the user to add a reason applied. Admins may mediate a conflict around a vote and make a judgment on whether it should be stricken or not.

ESB:Requests for discussion moderator

Requirements

Per Section B of the promotion policy, the requirements are:

a. At least one (1) month must have passed since the user's first edit.
b. The user must have at least fifty (50) main namespace edits.
c. The user must have at least five hundred (500) Discussions posts.
d. The user must have a clean block record for at least three (3) months, not counting invalid blocks.
~~e. The user must have support from a majority of all administrators.~~
f. The user must have support from a majority of all bureaucrats. If the request fails to do so, it requires 75% support of administrators who are not bureaucrats for the request to pass unless otherwise stated
d. If the nominee has a rate of support of 80% or above, the rights are granted.
e. If the nominee has a rate of support between 70% and 80%, bureaucratic discretion is to be used in determining whether rights are granted. *Arguments from the votes provided and the responses of the nominee to questions will be considered.
f. If the nominee has a rate of support of 70% or below, the rights are not granted.
g. All votes must have at reasons. Votes without reasons and votes without good reasons (eg, "I don't like him") will be stricken, with a note for the user to add a reason applied. Admins may mediate a conflict around a vote and make a judgment on whether it should be stricken or not.