FANDOM


Wiki
Open Convention Discussion

The following is an ongoing convention discussion. Please feel free to voice your opinion, but be sure to follow the rules.


You can use any of the following prior to your comments to show your opinion.

{{Support}} • {{Neutral}} • {{Oppose}}
{{Like}} • {{Dislike}} • {{Change}} • {{Comment}} • {{Question}}
Note: Neutral votes do not count in determining the outcome percentage.


Instructions

This convention discussion concerns the following topic: "Fundamental issues - Abolishing ESB:Block reviews."

At the end of the page, you have "Create New Subtopic" button, which you can use to voice your concerns, comments, or questions about what the proposal. You can use the "Refresh This Discussion" button, which you can use to make sure that all changes are included to a page.

You can also add your comments to existing subtopics.

Have a happy discussion!


Topic

I am proposing to fully abolish ESB:Block reviews. I do not believe there is any point to allowing users without user rights to be able to lift anyone's block. That is a user right only included in the administrator right, and it shouldn't be given just because of community consensus. It can be argued that it is "undemocratic" to not allow users to decide whether or not someone should be unblocked, but pure democracy would mean that users decide who to block as well, which doesn't make much sense. In addition, administrators have already been chosen by the community to perform all administrator tasks. Update: I agree with AMK's policy changes here:

Article III: Definitions

  • A. The definitions in this section apply to this entire policy page.
  • B. Definitions
  • X. Administration - includes only administrators and bureaucrats.

Article XVI: Blocking

  • A. General
  • 1. If a user is violating any rule, administrators must resolve the problem and politely notify the user of their wrongdoing by giving one (1) warning on their message wall.
  • 2. If a user breaks two (2) different rules, that counts as one (1) warning for each rule. A user that breaks the same rule twice merits a block.
  • 3. If a warned user continues to break the same rule within twenty-four (24) hours without acknowledging the warning, the administrator should try to contact that user again.
  • 4. If the warned user continues to break the same rule for twenty-four (24) hours after the administrator tried to contact them again, the user will be blocked for a maximum of fourteen (14) days.
  • 5. Any user who continues to violate the rule for which they were blocked within seven (7) days after their initial block ends will receive further penalties, depending on the rule(s) violated and the severity of the offense at the discretion of the administration.
  • B. Exceptions
  • 1. Any user who commits offenses that are very serious to the point in which they harm the wiki or threaten a user may be blocked immediately for any given amount of time at the discretion of the blocking administrator.
  • 2. Any user who spams, vandalizes, harasses, or threatens a user or the wiki as a whole as their first contribution or interaction may automatically be blocked immediately without warning. If they continue to violate such rules after their block, they shall be given an infinite block.
  • 3. Users that misuse spelling and/or grammar, unintentionally use improper formatting, and/or make an accidental edit shall not be blocked.
  • C. Blocking the user
  • 1. When an administrator blocks a user, they must use the {{Blocked}}​ template on their message wall to notify that they have been blocked. This allows the blocked user to know that they have been blocked and the reason, so that they can be linked to the policies to better understand our rules, as well as learn how to appeal a block.
  • 2. Administrators must leave the user's message wall open in order for the blocked user to make an appeal case.
  • 3. If a blocked user abuses their wall privileges by spamming, threatening, or harassing other users, before making an appeal case, they have forfeited their chance to make an appeal for the duration of the block and can have their wall privileges removed until the end of their block.
  • 4. A bureaucrat may unblock the user if they deem it an unfair block. If any other bureaucrat isa in disagreement, the bureaucrat disputing the block must start a block review. block review. [removing link, referring to section]
  • D. Block disputes
  • 1. A block dispute occurs when an administrator's action in blocking a user is challenged.
  • 2. Any user may appeal their block or another user's block they deem unfair to have the block or ban removed.
  • 3. All blocking disputes should be handled between the conflicting parties. If the conflicting parties resolve the dispute, the dispute is over.
  • 4.If neither party agrees to a compromise, any user opposing the block must start a block review and follow the procedures.
  • F. Block review. A blocked user may request their block be reviewed by the entire administration.
  • 1. Disputed blocks shall be discussed in a block review at ESB:Block reviews.
  • 2. The review will follow the discussion policies and last seven (7) days, except for the following:
  • a. A block review requires 70% opposing the block to overturn the block, not counting neutrals.
  • b. For blocks less than seven (7) days, the appeal discussion will last half the amount of time of the block.
  • 3. If the appeal fails, the block will not be reverted.
  • 4. If an infinitely blocked user fails an appeal, they must wait two (2) months before creating another appeal. The third and all subsequent appeals cannot be created until six (6) months have passed since the previous appeal concluded.
  • 5. If a block review receives unanimous opposition with no neutral votes and a majority of administrators do not support unblocking the user after three (3) days, the block review will be marked as closed.
  • 6. If a blocking dispute involving an administrator may be considered an abuse of power, a majority of uninvolved bureaucrats must decide on either a) a suspension up to fourteen (14) days or (b) an emergency user rights review
  • 1. The blocked user must first message an ESB administrator on Community Central.
  • 2. The administration will conduct an internal review of the block and decide whether or not it shall be overturned.
  • 3. A majority vote of the administration is required to overturn the block.
  • 4. The record of the result of the vote must be recorded in a table at ESB:Block reviews, with the numbered tally of the vote and a link to the blocked user's request for a review, along with the name of the recording administrator.
  • 5. If the block is not overturned, the blocked user cannot request another block review for two (2) months. Any subsequent block review requests may be conducted two (2) months succeeding the end date of the last valid review.
  • F. Blocking administrators. Blocking another administrator is strictly prohibited. All administrators are supposed to resolve disputes with each other through discussion and not blocking.
  • 1. Any administrator who blocks another administrator will be suspended from all roles (administrator, assistant, rollback, chat moderator, discussion moderator) and an emergency user rights review shall be created.
  • 2. Any exception to the rules, including an appeal from the suspended administrator, will be implemented by a vote of a majority of bureaucrats.

The most expensive boss, Alex.sapre (talk) 09:24, July 2, 2019 (UTC) 

Subtopics

Created subtopic: Agree, with policy changes

PreviewModifyComment

Note that we tried to do this in January but it failed. Perhaps this could be adjusted accordingly?

Article III: Definitions

  • A. The definitions in this section apply to this entire policy page.
  • B. Definitions
  • X. Administration - includes only administrators and bureaucrats.

Article XVI: Blocking

  • A. General
  • 1. If a user is violating any rule, administrators must resolve the problem and politely notify the user of their wrongdoing by giving one (1) warning on their message wall.
  • 2. If a user breaks two (2) different rules, that counts as one (1) warning for each rule. A user that breaks the same rule twice merits a block.
  • 3. If a warned user continues to break the same rule within twenty-four (24) hours without acknowledging the warning, the administrator should try to contact that user again.
  • 4. If the warned user continues to break the same rule for twenty-four (24) hours after the administrator tried to contact them again, the user will be blocked for a maximum of fourteen (14) days.
  • 5. Any user who continues to violate the rule for which they were blocked within seven (7) days after their initial block ends will receive further penalties, depending on the rule(s) violated and the severity of the offense at the discretion of the administration.
  • B. Exceptions
  • 1. Any user who commits offenses that are very serious to the point in which they harm the wiki or threaten a user may be blocked immediately for any given amount of time at the discretion of the blocking administrator.
  • 2. Any user who spams, vandalizes, harasses, or threatens a user or the wiki as a whole as their first contribution or interaction may automatically be blocked immediately without warning. If they continue to violate such rules after their block, they shall be given an infinite block.
  • 3. Users that misuse spelling and/or grammar, unintentionally use improper formatting, and/or make an accidental edit shall not be blocked.
  • C. Blocking the user
  • 1. When an administrator blocks a user, they must use the {{Blocked}} template on their message wall to notify that they have been blocked. This allows the blocked user to know that they have been blocked and the reason, so that they can be linked to the policies to better understand our rules, as well as learn how to appeal a block.
  • 2. Administrators must leave the user's message wall open in order for the blocked user to make an appeal case.
  • 3. If a blocked user abuses their wall privileges by spamming, threatening, or harassing other users, before making an appeal case, they have forfeited their chance to make an appeal for the duration of the block and can have their wall privileges removed until the end of their block.
  • 4. A bureaucrat may unblock the user if they deem it an unfair block. If any other bureaucrat isa in disagreement, the bureaucrat disputing the block must start a block review. block review. [removing link, referring to section]
  • D. Block disputes
  • 1. A block dispute occurs when an administrator's action in blocking a user is challenged.
  • 2. Any user may appeal their block or another user's block they deem unfair to have the block or ban removed.
  • 3. All blocking disputes should be handled between the conflicting parties. If the conflicting parties resolve the dispute, the dispute is over.
  • 4.If neither party agrees to a compromise, any user opposing the block must start a block review and follow the procedures.
  • F. Block review. A blocked user may request their block be reviewed by the entire administration.
  • 1. Disputed blocks shall be discussed in a block review at ESB:Block reviews.
  • 2. The review will follow the discussion policies and last seven (7) days, except for the following:
  • a. A block review requires 70% opposing the block to overturn the block, not counting neutrals.
  • b. For blocks less than seven (7) days, the appeal discussion will last half the amount of time of the block.
  • 3. If the appeal fails, the block will not be reverted.
  • 4. If an infinitely blocked user fails an appeal, they must wait two (2) months before creating another appeal. The third and all subsequent appeals cannot be created until six (6) months have passed since the previous appeal concluded.
  • 5. If a block review receives unanimous opposition with no neutral votes and a majority of administrators do not support unblocking the user after three (3) days, the block review will be marked as closed.
  • 6. If a blocking dispute involving an administrator may be considered an abuse of power, a majority of uninvolved bureaucrats must decide on either a) a suspension up to fourteen (14) days or (b) an emergency user rights review
  • 1. The blocked user must first message an ESB administrator on Community Central.
  • 2. The administration will conduct an internal review of the block and decide whether or not it shall be overturned.
  • 3. A majority vote of the administration is required to overturn the block.
  • 4. The record of the result of the vote must be recorded in a table at ESB:Block reviews, with the numbered tally of the vote and a link to the blocked user's request for a review, along with the name of the recording administrator.
  • 5. If the block is not overturned, the blocked user cannot request another block review for two (2) months. Any subsequent block review requests may be conducted two (2) months succeeding the end date of the last valid review.
  • F. Blocking administrators. Blocking another administrator is strictly prohibited. All administrators are supposed to resolve disputes with each other through discussion and not blocking.
  • 1. Any administrator who blocks another administrator will be suspended from all roles (administrator, assistant, rollback, chat moderator, discussion moderator) and an emergency user rights review shall be created.
  • 2. Any exception to the rules, including an appeal from the suspended administrator, will be implemented by a vote of a majority of bureaucrats.

AMK152 (Wall • Contrib) 13:56, July 2, 2019 (UTC)

Would this include rollbacks as well? The most expensive boss, Alex.sapre (talk) 02:05, July 3, 2019 (UTC) 

What do you mean? — AMK152 (Wall • Contrib) 03:01, July 3, 2019 (UTC)

Would they also have a say when it comes to blocked users? The most expensive boss, Alex.sapre (talk) 05:24, July 3, 2019 (UTC) 

No, it would just be administrators. Rollbacks can certainly give their opinion, but only administrators make the decision. — AMK152 (Wall • Contrib) 19:31, July 9, 2019 (UTC)


Create New SubtopicRefresh This DiscussionMonitor This Discussion

Community content is available under CC-BY-SA unless otherwise noted.