ESB:Proposals/Procedures revision

	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: August 31, 2016 Result: AMK152, ZeoSpark, and Nicko756 voted in favor of closing discussion early; there are too many topics here and should be discussed separately.

Instructions

This is a page for creating and resolving concerns on the topic: "Procedures revision."

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

So this is what I am proposing: (~~struck out means taken out~~, bolded means new)

I. Discussions

A. General (revised November 24, 2015)

1. All major issues must be resolved with discussions in the format outlined in this chapter.
2. Discussions outside of the regular discussion thread (such as message walls) are not valid places to make major decisions and/or policy changes. They can be used to bring up important issues that can be put up for official discussion, as long as they follow the rules.
3. Discussions are completely open to all contributors, except if it involves a demotion of suspension of a particular user, in which that case the user in question does not have a vote. They are, however, allowed to comment, ask, and answer questions.
4. Anyone can open a discussion at stage one, but only bureaucrats or the person that opened the discussion are permitted to open the voting stage.

B. Format (revised November 24, 2015)

1. All discussions ~~will be~~ are to be conducted in two stages: 1) concern stage and 2) voting stage.

a. Stage 1: Concern stage

i. An ~~issue, situation, and/or policy change~~ topic for discussion will be brought up by any user.
ii. All users will be given a chance to voice their opinion unless they are blocked on the ~~issue, situation, and/or policy change~~ discussion, without voting.
iii. After ~~ten (10)~~ seven (7) days of discussion, the concern stage can be closed. If the discussion requires more input, it can remain open for a longer period of time.
iv. If no concerns are brought up after ~~three (3) days~~ two (2) days, the concern stage can be closed.

b. Stage 2: Voting stage

i. Any bureaucrat and the user who opened the discussion are to consider everything that was concluded in the concern stage and create a new updated proposal together, thus concluding the concern stage and starting a voting stage.
ii. All users will be given a chance to vote.
iii. After ~~ten (10)~~ seven (7) days of voting, the voting stage will be closed.

~~2. Exceptions~~

a. If a discussion requires more input, or contains a series of discussions, the discussion may be open for a longer period of time and close a different way.

b. In the case of non-controversial discussions, a proposal may end after 3 days of discussion if both of the following are true:

~~i. At least four (4) administrators support the proposal.~~

~~ii. The discussion has ten (10) supports and no opposition.~~

C. Closing discussions (revised November 24, 2015)

1. At the end of the voting stage, in order for a proposal or option to pass, there must be at least a 70% majority in support of the particular proposal.
2. If there is not a 70% or more support in favor of the proposal or option, the discussion is concluded to have not passed and the discussion can be closed.
3. In the event that a discussion is closed and an agreement is not reached, another discussion may be created for further discussion.
4. Any bureaucrat or administrator can close the voting stage, as long as the above procedures are followed.

D. Post-discussion (revised November 24, 2015)

1. When a proposal passes, the decision is final unless a discussion nulls and/or changes the matter.
2. Unless otherwise stated, the policy change takes effect immediately.

II. User of the Month

A. User of the Month (revised June 1, 2014)

1. This is awarded to one user each month, who will be featured on the homepage, and contain a link to a page that highlights why they received the award and the work they have done.
2. Procedures

a. These clauses outline the process of the User of the Month award.
b. Eligibility

i. A user must have contributed for at least one (1) month in order to qualify.
ii. A user must have made at least ~~one hundred (100)~~ three hundred (300) edits in order to qualify.
iii. Anyone can nominate any other user except themselves.
iv. Anyone who requests that another user nominate them will be disqualified for six (6) months.
v. Anyone who complains that they have not been nominated will be disqualified for six (6) months.

c. Nomination process

i. The nominator will create a nomination page and list reasons why the person should be nominated.
ii. Everyone except the user who is nominated can contribute to the discussion and show their support or oppose for the nomination.
iii. Nomination discussions expire after (3) months. After this, a user can be renominated.
iv. On the last day of each month the next month's User of the Month will be determined based on the following formula: (Number of Supports)-(Number of Opposed)=Nomination Rating. The current user with the highest nomination rating at the time will be awarded "User of the Month" for the following month.

III. Article of the Month

A. Article of the Month (revised June 2, 2014)

1. This section outlines the process by which an article become featured on the home page for each month.

2. Procedures

a. These clauses outline the process of the Article of the Month award.

b. Eligibility

i. The article must follow all relevant guidelines.

ii. The article must be free of spelling/grammar issues.

iii. The article must be at least 3,000 bytes (see history to find the size).

iv. The article must be free of any editing controversy.

v. The article must be of the highest quality.

vi. The article must contain at least one image.

c. Nomination process

i. The nominator will create a nomination page and list reasons why the article is good enough to be featured.

ii. Everyone can contribute to the discussion and show their support or oppose for the nomination.

iii. Nomination discussions expire after (3) months. After this, an article can be renominated.

iv. On the last day of each month the next month's Article of the Month will be determined based on the following formula: (Number of Supports)-(Number of Opposed)=Nomination Rating. The current article with the highest nomination rating at the time will become the "Article of the Month" for the following month.

IV. Tasks

A. General (revised April 14, 2015)

1. A task is a specific item that needs to be completed on the wiki.

B. Task procedures (revised April 14, 2015)

1. All users are allowed to create tasks.

2. All tasks will be created using a form similar to RFA, RFB, UOTM, and AOTM. These are called "task pages" and will be used to describe the tasks and help determine the winner (or winners) of the task once complete.

3. All open tasks will be listed on one page to show users which tasks they may work on.

4. Once a task is complete, a bureaucrat will close the task. Note that the term "finishing" or "finish" is used loosely as such may not be complete in the future, or require minor adjustments.

5. All tasks and points are to be listed here: ESB:Tasks

V. Quote contests

A. General (revised September 7, 2014)

1. Quotes will be allowed to return to the episode articles through this contest only.

2. The community will decide which quotes are notable enough for inclusion in that section.

B. Process (revised September 7, 2014)

1. At the start of each contest, each episode will have a "quotes nomination" page.

2. Everyone can submit quotes to the contest, and support or oppose whether or not they believe the quote is notable for inclusion.

3. Every two (2) weeks, quotes nomination pages for 20 episodes will be set up.

4. Everyone will have one (1) month to participate in the discussion.

5. At the end of the discussion period, the quotes that have 90% support or more will be deemed "notable quotes."

6. The "winning" quotes will be placed in a protected template. (example: {{Quotes/Help Wanted}})

C. Additional details (revised September 7, 2014)

1. At one time only 40 episodes will be discussed (starting two weeks after the beginning of the contest) to keep the list shorter. This will result in the contest lasting about 10 months.

2. At the end of the cycle, the contest will begin again, and continue forever.

3. All new episodes must wait for the cycle to arrive before they are in the contest. This allows time for people to figure out what quotes are notable.

~~4. A contest page will be set up for easy access to all current contests.~~

VI. Deletion policy

A. General (revised July 2, 2015)

1. The requests for deletion process is an optional process; administrators can delete anything ~~they believe is necessary~~that breaks the policy.
2. If there is any controversy over deleting a certain page, abstain from a deletion war, do not delete the page, and bring the page in question to discussion.
3. Anyone can nominate an article they feel should be deleted.

B. Process (revised July 2, 2015)

1. Fill out a form to create a deletion discussion.
2. Once the discussion is created, the nominator must explain why they feel the article should be deleted.

a. If no explanation is give after twenty-four (24) hours, it will we closed as invald.

3. A discussion will occur, centered on that particular article, template, category, etc.
4. Neutral votes do not count in the final tally for consensus (70%)

C. Closing discussions (revised July 2, 2015)

1. Only administrators and bureaucrats can close deletion discussions.
2. If a discussion closes and the result is deletion, the page can be redirected to another article if there is a useful redirect.
3. If a deletion discussion does not recieve a consensus (70%) either way after six (6) months, the discussion can be closed as "no consensus" and the article is kept.

VII. Contests

A. General (revised August 14, 2015)

1. Contests can be used to choose backgrounds, logos, or anything else requiring user submissions and votes.
2. Only administrators or bureaucrats can open or close contests.
3. Contests must have at least a two week voting period; there may be some exceptions with some contests having a shorter voting period.

B. Background contests (revised August 14, 2015)

1. Every decision about the current background of the wiki is determined by the outcome of background contests.
2. You are allowed to submit multiple backgrounds.
4. All backgrounds must relate to SpongeBob and/or the show or they will be removed for being invalid.
5. If you submit a background that won the previous year, it will be removed. You are allowed to submit backgrounds that did not win the previous year.

a. For Summer background contests, this rule does not apply. However, if a background from the previous year has placed in the same position as in the previous year, then it will be disqualified and the next position will be the winner of that placement.

6. You can make your own background or add an image from the internet. While there's no size requirement, bigger is usually better.
7. When making an entry, please use the correct format. This format should be provided on the contest page. If you are unable to do so, ask for help or someone will fix the form for you. You will not be penalized for doing this incorrectly.

C. Decision process (revised August 14, 2015)

1. At the beginning of the final week, the current standings should be added in a table. It should be removed when the winner is announced.
2. The ranking of a submission is determined by the difference of likes vs. dislikes. For example, if a submission has 4 likes and 3 dislikes, it has 1 point.
3. Tiebreakers will be determined by another contest page with the finalists, usually shortly before the background is set to go up.
~~4. When the winners are announced, it's common courtesy to give each of them a message telling them that they won.~~

Thank you for reading my discussion on the procedures revision. — Cans48 _(Messages)

Concerns

Created concern: Concerns

Preview • Modify • Comment

I.A: A regular user cannot move a discussion to a voting stage, not at all. II.A: Should still be 100 edits. AOTM, Quote contests, and Tasks should not be marked off. ➞§σпιҫᵀʰᵉξριҫッ 17:06, August 25, 2016 (UTC)

I.A. Regular users that started the discussion can move it. Not regular users.
II.A. I crossed them off because they haven't been used in years.
- — Cans48 _(Messages)

Created concern: Too much to discuss

Preview • Modify • Comment

We should discuss things separately. There are just too many changes here:

1. Getting rid of discussion exceptions is a terrible idea. Some non-controversial proposals need to be closed early.
2. We have had discussions in the past that follow a different format; we need that discussion.
3. It would be better to keep the AOTM policies in case we decide to use them. Anyone can go ahead and manage that. I never really had the time to do that and UTOM, but we still need the policies.
4. Quote contests policies should remain open too, as it is not hurting anything in the event we may need it.
5. You keep adding bureaucrats to some areas, but bureaucrats ARE administrators, so it is redundant.

— AMK152 (Wall • Contrib) 12:52, August 26, 2016 (UTC)

Create New Concern • Refresh This Discussion • Monitor This Discussion