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!
The following proposal takes the "Administrator duties" and "Promotions" articles of the provisional bylaws.
A few items:
Several aspects of the promotion policy have been simplified.
One item from "administrator duties" has been moved to the "user conduct" policy.
Promotion policy has been split into two articles: "Roles" and "Promotions."
For eligibility, there is no measurement for "general" requirements, so I put it all into one paragraph and reworded/expanded it.
All articles shall be renumbered accordingly, with "Roles" to replace the "administrator duties" article.
Article V. User conduct
A. User interaction
A.6. Do not pose as an administrator if you are not one. Administrators are the only ones allowed to inform a user that they have been blocked or banned.
Article #. Roles
A. Certain users are given more abilities, known as user rights, in order for the wiki to be run more effectively.
B. Additional user roles shall be bureaucrats, administrators, assistants, discussion moderators, chat moderators, and rollbacks. Other roles may be granted to certain users, including, but not limited to bots, social media managers, and Skype administrators.
a. Promotion requests for bureaucrat, administrator, and assistant, discussion moderator, and chat moderator must be done so through an application process.(merged into A, below)
b. Rollbacks may be promoted at the discretion of any administrator.(merged into A, below)
2. Anyone seeking to be promoted must make the request by filling out a form so the community can discuss the request.(merged into A, below)
B.1. 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.
C.2. Administrators are privileged with the power to block other users and are expected to have good judgment when it comes to using this tool.
A.3.Do not pose as an administrator if you are not. Administrators are the only ones allowed to inform a user that they have been blocked or banned.
Article #. Promotions
3.A. Application process
1. Users requesting promotion to bureaucrat (link), administrator (link), assistant (link), discussion moderator (link), or chat moderator (link) must do so through a formal promotion request, linked in this section. Rollbacks may be promoted at the discretion of any administrator.
1.2. 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.
2.3. 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. During the discussion
3.a. 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.
4.b. Applicants shall not force other users to support them. Applicants are allowed to notify other users of such discussion, without imposing an agenda.
5.c.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.
6.d.Administrator and bureaucrat requests canmay be posted on the forum to seek more input, and they canmay also be highlighted.
6.5. Length of request.
a. Promotion requests are to last no shorter than seven (7) days from the time the applicant makes the request. (merged into one paragraph)
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.
(Note: I removed these because it is not a huge deal between a request lasting 3 days and 7 days; we might as well be thorough. We do have criteria for invalid requests to make those end early, which is why we had some of these in the first place, so if we wanted to expand that with more specific criteria, we could do so.)
7.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.
c. Unsuccessful or invalid promotion requests may be closed by an assistant or administrator.
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.
8.7. Invalid requests. A request is deemed invalid if one of the following is true, and may be closed accordingly.
a. The questions remain blank more than two (2) hours after the creation of their request.
b. The user is not eligible for the position.
c. Any user that receives a valid block while having a pending promotion request. 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.
1. General requirements. 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.
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.(merged into paragraph at B1)
b. The user must demonstrate that all their contributions are positive, and further the goal of improving the wiki.(merged into paragraph at B1)
c. The user must demonstrate the use of proper spelling and grammar.(merged into paragraph at B1)
d. The user must demonstrate that they can hold the position with maturity.(merged into paragraph at B1)
e. Any exceptions to these requirements may be waived by a unanimous vote of all bureaucrats.(merged into paragraph at B1)
2. All 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
a. The user must have a clean chat ban record for at least one (1) month, not counting invalid chat bans.
4. Discussion moderator
a. The user must have at least five hundred (500) board thread edits.
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.
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.
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. Any user that retires, retiresresigns, 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.
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.
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).
Voting ends Sunday, April 1, 2018 at 4:52 p.m. — AMK152 (Wall • Contrib) 20:51, March 25, 2018 (UTC)
Comment - I actually noticed a common mistake on the repromotion section:
"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." That "retires" in bold is a duplicate and therefore should be removed. (Contact • Contrib) 12:57, March 26, 2018 (UTC)