After all concerns from concern stage of this discussion has been resolved and taken into account, proposal located in "Proposal" section above has been created and put to voting. To join the voting, you simply use buttons located in "Voting" section of this page and fill the resulting page.
Have a happy voting!
I am proposing the following changes to the promotions policy, and for this to become "Article IX: Promotions" as part of the ESB:Provisional Bylaws.
a. Promotion requests for bureaucrat, administrator, and assistant, discussion moderator, and chat moderator must be done so through an application process.
a. Promotions at ESB fall into two categories: request roles and non-request roles.
i. Request roles require a promotion request for the following positions: bureaucrat, administrator, and assistant, discussion moderator, and chat moderator.
ii. Non-request roles do not require a promotion request for the rollback position.
a.b. Rollbacks may be promotedAnyone seeking promotion to rollback may contact an administrator, as rollbacks are promoted at the discretion of any administrator.
b. When a user is promoted, they have more privileges than the average user. They are expected to use these powers with good judgment and follow all the rules. (moved to an "administrator duties" section)
2. Anyone seeking to be an administrator, bureaucrat, assistant, discussion moderator, or chat moderatorpromoted must make the request by filling out a form so the community can discuss the request.
1. Anyone making any promotion request must follow these procedures. (seems pointless as it is a given)
2. They1. Applicants must create a request page using the associated form, ensuring they answer the questions and follow the proper requirements. There are no right or wrong answers, the questions are there to help the community make a decision.
3.2. The questions for all requests are as follows:
a. Why do you believe you are qualified to be promoted to this position?
b. Have you had experience with this position before?
c. What are your best contributions to Encyclopedia SpongeBobia and why?
d. How do you plan to use your rights if your request is successful?"
e. Have you been in a situation in which you needed the user rights for this position at that moment but were unable to act?
f. Is there anything else you want to add?
4.3. Applicants shall not use any images to advertise "support" for them, so as to discourage unqualified users who seek the support of others who do not consider their qualifications.
5.4. Applicants shall not force other users to support them. Applicants are allowed to notify other users of such discussion, without imposing an agenda.(such as using images to advertise for support, as in clause 3, above). (this last part is redundant)
6.5. Nominating another user for any position requiring a request form is prohibited unless the nominating user is an administrator or bureaucrat. All other nominations will be closed as invalid.
7.6. Administrator and bureaucrat requests can be posted on the forum to seek more input, and they can also be highlighted.
a. All users are welcome to participate in promotion discussions, as long as one (1) week has passed since their first edit.
b. Any user who participates in such a discussion and is subsequently blocked, their vote will not count if they are still blocked at the point in which the request is closed.
c. Any requestee or nominee editing or removing votes from such a discussion will have their entire request or nomination invalidated and they are prohibited from making such a request for any position for thirty (30) days.
5. Length of request
a. Promotion requests are to last no shorter than seven (7) days from the time the applicant makes the request.
b. Some promotion requests may end early if one of the following criteria is met.
i. If an applicant has the support of at least 90% of participating administrators, they may be promoted after three (3) days.
ii. If more than half (50%) of active administrators do not support the user's application, the request may be closed early as unsuccessful.
iii. If a promotion request has 0% support from administrators after three (3) days, it may be closed early as unsuccessful.
6. Closing requests
a. Any applicant that has 70% support of all votes shall be promoted after the seven (7) days.
b. Successful requests may only be closed by those that have the ability to grant those rights.
b. Only bureaucrats can close successful bureaucrat, successful administrator, and successful assistant requests, as only they have the ability to grant those rights.
c. Administrators may close successful discussion moderator and successful chat moderator requests, as they have the ability to grant those rights.
d.c. Unsuccessful or invalid promotion requests may be closed by an administrator.
e.d. If a user makes a promotion request but fails to be promoted, they must wait at least seven (7) days before making another request. Any bureaucrat can waive this rule by supporting the request.
7. Invalid requests. A request is deemed invalid if one of the following is true, and may be closed accordingly.
a. Anyone who makes a promotion request in which they leave any of tThe questions remain blank, must answer the questions withinmore than two (2) hours afterof the creation of their request.or else the request will automatically be closed as invalid.
b. Anyone who makes a promotion request and does not meet the listed requirements, the request must be closed as invalid unless otherwise stated.The user is not eligible for the position.
c. Any user that receives a valid block while having a pending promotion request, the request will automatically be closed as invalid. The user will be prohibited from making any request for thirty (30) days, starting the time their block ends. Any bureaucrat can waive this rule by supporting the request.
a. General requirements apply to promotion requests and those involved in the decision process determine whether or not the user meets the requirements per the success or failure of the request.
b. The user must demonstrate that all their contributions are positive, and further the goal of improving the wiki.
c. The user must demonstrate the use of proper spelling and grammar.
d. The user must demonstrate that they can hold the position with maturity.
e. Any exceptions to these requirements may be waived by a unanimous vote of all bureaucrats.
2. Requirements for aAll positions
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 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.
3. Chat moderator requirements
a. The user must have a clean chat ban record for at least one (1) month, not counting invalid chat bans.
4. Discussion moderator requirements
a. The user must have at least five hundred (500) board thread edits.
5. Assistant requirements
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.
6. Administrator requirements
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.
7. Bureaucrat requirements
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 full support from all bureaucrats.
1. This section covers policies in regards to users who may request promotion following resignation or retirement. (we don't need to explain this)
2.1. Any user that retires, retires, or quits and returns and wishes to be repromoted, they must follow the same procedures and requirements as if they were a user who had never been promoted before.
3.2. If a retired or resigned user returns to ESB, they cannot be promoted to any position until three (3) months following the announcement of their return or decision not to retire or resign.
4.3. Any requirement of the repromotion policy can be waived by the majority vote of all bureaucrats. This can be overruled by a majority vote of all administrators (sysop only).
I am proposing the following, moved from above, be placed under "Article V: Administrator Duties" of the ESB:Provisional Bylaws. We can rename it later so it refers to all promoted users instead of just administrators.
b. When a user is promoted, they have more privileges than the average user. They are expected to use these powers with good judgment and follow all the rules.
This voting stage ends Monday, December 18, 2017 at 12:05 p.m., eastern time. — AMK152 (Wall • Contrib) 05:04, December 11, 2017 (UTC)