ESB:Proposals/Promotion policy (3)

	Proposal Archive The following proposal has been discussed and is now marked as resolved. The page has been protected and now serves as an archive. Do not edit this page. Date Resolved: March 3, 2016 Result: Moved to voting.

Instructions

This is a page for creating and resolving concerns on the topic: "Promotion policy (3)."

At the end of the page, there is a "Create New Concern" button, which you can use to voice your concerns or questions about the proposal. You can use the "Refresh This Discussion" button, which allows you to make sure that all changes have been saved.

After 7 days of discussion, the concerns stage will end. All points brought up during that phase will be taken into account and an administrator, assistant, or the proposal's creator can move the discussion to voting, modifying the original proposal with any changes discussed by the community.

You can also add your comments to existing concerns. On the other hand, if you have no concerns, then you just wait for the voting stage.

Have a happy discussion!

Proposal

This is a proposal to completely alter the administrative process to make it more efficient and ensure we have more effective and competent administrators. The proposal breaks down three positions here at ESB into three different levels: Assistant, Administrator, and Bureaucrat. While these are our current levels, I am proposing that we completely streamline the process as far as requirements and levels of positions. This involves completely revamping the promotion policy.

The key part of this proposal is requiring users to be an assistant for at least three (3) months prior to making a request to be an administrator. This, in effect, creates the following that many people have suggested over the past couple of years:

1. Ensuring we have well qualified and competent administrators.
2. Creating basic, but more effective administrator requirements.
3. Introducing "administrator trials" in the form of using the "assistant" position.
4. Invalidating more "spam requests."

Another key component of this proposed policy change is in regards to the hesitance toward creating administrator requirements that may hinder good contributors from gaining more privileges quicker. However, that's where the assistant position comes in now. We can have no requirements for assistant requests, but make stricter requirements for administrator requests.

This proposal also involves the following on the ESB:Policy page:

1. Merges administration and promotion policy into one section.
2. Separates promotion policy and demotion policy into two sections.
3. The creation of ESB:Requests for assistant with the policies associated in this proposal.

Also note that this does not change the status of current assistants, administrators, and bureaucrats. If passed, they are grandfathered in based on the old policy. This only applies to all future requests.

Additions are in bold, removed stuff is ~~struck out~~, but many other things have been moved around and reworded.

A. Promotions

1. General

a. Promotions at ESB fall into two categories: minor roles and major roles.

i. Major roles are bureaucrat, administrator, and assistant.
ii. Minor roles are all other positions, including but not limited to: rollback, chat moderator, and thread moderator.

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.

2. Anyone seeking to be an administrator, bureaucrat, or chat moderator must make the request by filling out a form so the community can discuss the request.

a. Requests for chat moderator are here: ESB:Requests for chat moderator
b. Requests for assistant are here: ESB:Requests for assistant
c. Requests for administrator are here: ESB:Requests for adminship
d. Requests for bureaucrat are here: ESB:Requests for bureaucrat

3. Application process

1. Anyone making any request for chat moderator, assistant, administrator, or bureaucrat, must follow these procedures.
2. They must create a request page using the form, ensuring they fill out the reason and follow the proper requirements.
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.
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).

4. Voting

a. All users are welcome to participate in promotion discussions.
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.

5. Length of request

a. Chat moderator, assistant, administrator, and bureaucrat, requests are to last no shorter than seven (7) days from the time the applicant makes the request.
b. Early closing

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 is unsuccessful and may be closed.

6. Closing requests

a. Any applicant that has 70% support of all votes shall be promoted after the seven (7) days.
b. Only bureaucrats can close administrator requests, as they have the ability to promote those that are successful in their application.
c. If a user makes a chat moderator, assistant, administrator, or bureaucrat request but fails to be promoted, they must wait at least seven (7) days before making another request, unless their request is endorsed by all active ~~administrators~~ bureaucrats.

7. Non-request roles

a. In addition to administrators and bureaucrats, there are other non-administrative positions at Encyclopedia SpongeBobia.
b. ~~Assistants,~~ Rollbacks and thread moderators do not require a formal request. Instead, they must contact an administrator or bureaucrat directly.
c. ~~Assistants are appointed when a majority of bureaucrats (50% or more) support the promotion of a user to this position.~~
d. Rollbacks and thread moderators are appointed at the discretion of the administration.

8. Invalid requests

a. Anyone who makes an administrator, bureaucrat, or chat moderator request in which they leave the "reason" for applying blank, must fill in the reason within twenty-four (24) hours of the creation of their request or else the request will automatically be closed as unsuccessful.
b. Anyone who makes a request for chat moderator, assistant, administrator, or bureaucrat and does not meet the listed requirements, the request must be closed as invalid unless otherwise stated.

B. Requirements

1. General requirements

a. General requirements apply to assistant, administrator, and bureaucrat 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. User must demonstrate that all their edits are positive, and further the goal of improving the wiki.
c. User must demonstrate use of proper spelling and grammar.
d. Any exceptions to these requirements may be waived by a unanimous vote of all bureaucrats.

2. Assistant requirements

a. User must have at least fifty (50) edits.

3. Administrator requirements

~~There are no requirements prior to making a request to be an administrator.~~
a. User must be a current assistant for at least three (3) months.
b. User must have a clean block record for at least three (3) months, not counting invalid blocks.
c. User must have support from a majority of all administrators.

4. Bureaucrat requirements

a. User must be a current administrator for at least two (2) years.
b. User must have at least 2,000 edits, of which at least 1,000 are main namespace edits.
c. User must demonstrate good reasons for any questionable edits.
d. User must have full support of all other active bureaucrats.
e. User must have support from a majority of ~~active~~ all administrators.
f. Any administrator requesting promotion to bureaucrat that does not meet the criteria outlined in clause a, above, may be waived if the request is supported by all other active bureaucrats and the requestor has been an active administrator for at least one (1) year.

This concern stage will end on Wednesday, March 2, 2016 at 4:30 p.m., eastern time. — AMK152 (Wall • Contrib) 21:27, February 21, 2016 (UTC)

Concerns

Created concern: looks excellent!

Preview • Modify • Comment

this will definitely eliminate spam adminship requests without the need for an arbitrary edit requirement. and i do agree that a user should be assistant before becoming administrator. ѕqυι∂∂ℓєωαя∂ ^{❮мεssαgε ωαℓℓ ● cσηтяιвυтισηs ● ε∂ιтcσυηт❯}

Created concern: Too long.

Preview • Modify • Comment

I think having to be an assistant for three months before being allowed to make an admin request is too long. Perhaps it should be lowered to 1 month. Nicko756 ^{(M•C•E) Sign!} 23:16, February 21, 2016 (UTC)

One month seems a bit too short though. ZeoSpark Talk Contribs Edits 23:28,2/21/2016

Keep in mind that any user who becomes an assistant is probably a trustworthy user. If an assistant is doing an excellent job as assistant for a month, then he/she is probably ready for the administrator position. If not, the community will oppose the request. Nicko756 ^{(M•C•E) Sign!} 23:39, February 21, 2016 (UTC)

What about 2 months? — AMK152 (Wall • Contrib) 00:01, February 22, 2016 (UTC)

Created concern: Process maybe?

Preview • Modify • Comment

I think users need to go thru this to show that they will be trustworthy:

User>Chatmod>Assistant

—Preceding unsigned comment added by SpongeFreddy777 (wall • contribs). Remember to sign your posts with ~~~~

not all users go on chat. i did not start coming on chat until about a month after i was promoted to assistant. ѕqυι∂∂ℓєωαя∂ ^{❮мεssαgε ωαℓℓ ● cσηтяιвυтισηs ● ε∂ιтcσυηт❯}

Yes, chat moderator is totally different from assistant. — AMK152 (Wall • Contrib) 04:53, February 24, 2016 (UTC)

Created concern: Assistant position

Preview • Modify • Comment

If assistant becomes "administrator trial" as the first point indicates, does this mean assistants will be forced to become admins after three months? If this is the case please don't force. I am honestly quite happy being an assistant rather than an admin for a few reasons. Auron ⚡ Yeah, that's right baby! Welcome to my locker! ⚡

No, it will only be a requirement for administrator. All it does is eliminates someone going straight from assistant to administrator. I said it's like a trial. I indicated that there will still be administrator requests, but the only valid requests will be for those who have been an assistant for at least three months. — AMK152 (Wall • Contrib) 04:54, February 24, 2016 (UTC)

Created concern: Only one concern.

Preview • Modify • Comment

I think thread moderator should be able to be a requested position, but I agree with everything else. ＳｏｎｉｃＴｈｅＥｐｉｃ (talk) 15:58, February 22, 2016 (UTC)

That is a separate discussion. — AMK152 (Wall • Contrib) 04:55, February 24, 2016 (UTC)

Created concern: Invalid requests

Preview • Modify • Comment

I would also like to adjust this in the "invalid requests" section:

a. Anyone who makes an administrator, bureaucrat, or chat moderator request in which they leave the "reason" for applying blank, must fill in the reason within ~~twenty-four (24)~~ two (2) hours of the creation of their request or else the request will automatically be closed as ~~unsuccessful~~ invalid.

— AMK152 (Wall • Contrib) 22:35, February 26, 2016 (UTC)

Create New Concern • Refresh This Discussion • Monitor This Discussion