Encyclopedia SpongeBobia
Encyclopedia SpongeBobia
Line 130: Line 130:
   
 
===IV. Administration===
 
===IV. Administration===
''This section was revised on August 18, 2014.''
+
''This section was revised on September 14, 2014.''
   
 
*A. Definitions
 
*A. Definitions
Line 142: Line 142:
 
:In order for a contributor to qualify for the administration, they must meet the following.
 
:In order for a contributor to qualify for the administration, they must meet the following.
 
:*1. User must have at least 750 edits of which at least 400 of these are main namespace edits.
 
:*1. User must have at least 750 edits of which at least 400 of these are main namespace edits.
:*2. User must have been active for at least 60 days from the date of their earliest edit prior to making the request.
+
:*2. User must have been active for at least thirty (30) days from the date of their earliest edit prior to making the request.
 
:*3. User must be able to demonstrate that they are willing to help and show good judgment.
 
:*3. User must be able to demonstrate that they are willing to help and show good judgment.
 
:*4. User must have a reason that is at least five sentences long, demonstrates their understanding of the position, and uses proper spelling and grammar.
 
:*4. User must have a reason that is at least five sentences long, demonstrates their understanding of the position, and uses proper spelling and grammar.
Line 165: Line 165:
   
 
*E. Decision Process
 
*E. Decision Process
 
::*1. Length of request
::*1. Any contributor can participate in the nomination discussion, as long as they meet the following criteria:
 
:::*a. Participants must have at least one hundred (100) main namespace edits.
 
:::*b. Participants must have been an active contributor for at least one (1) month.
 
:::*c. <font color="red">Participants must leave a comment along with their support, oppose, or neutral, otherwise their opinion doesn't count in the final decision.</font>
 
:::*d. All administrators within the SpongeBobia network are allowed to participate in the discussions.
 
::*2. Length of request
 
 
:::*a. Administrator and bureaucrat requests are to last no shorter than seven (7) days from the time the applicant makes the request.
 
:::*a. Administrator and bureaucrat requests are to last no shorter than seven (7) days from the time the applicant makes the request.
 
:::*b. If an applicant has the support of at least 90% of participating administrators, they may be promoted after three (3) days.
 
:::*b. If an applicant has the support of at least 90% of participating administrators, they may be promoted after three (3) days.
::*3. The applicant is promoted under the following circumstances:
+
::*2. The applicant is promoted under the following circumstances:
 
:::*a. They have at least three quarters (75%) support.
 
:::*a. They have at least three quarters (75%) support.
 
:::*c. If more than half (50%) of active administrators do not support the user's application, the request is unsuccessful and may be closed.
 
:::*c. If more than half (50%) of active administrators do not support the user's application, the request is unsuccessful and may be closed.
::*4. Only bureaucrats can close the discussion, as they have the ability to promote those that are successful in their application.
+
::*3. Only bureaucrats can close the discussion, as they have the ability to promote those that are successful in their application.
::*5. If a user makes an administrator request but fails to be promoted, they must wait at least thirty (30) days before making another request, unless their request is endorsed by all active administrators.
+
::*4. If a user makes an administrator request but fails to be promoted, they must wait at least thirty (30) days before making another request, unless their request is endorsed by all active administrators.
   
 
*F. Administrator Duties
 
*F. Administrator Duties
Line 186: Line 181:
 
:*5. Any administrator who is demoted after their adminship is terminated, obtains "former administrator" status.
 
:*5. Any administrator who is demoted after their adminship is terminated, obtains "former administrator" status.
   
  +
*G. Retirement, resignation, and inactivity: some changes, additions, and clarifications
*G. Demoting Administrators
 
  +
:*1. General
:*1. All administrators keep their administrative powers as long as they want, with the exceptions outlined in this section.
+
::*a. All administrators keep their administrative powers as long as they want, with the exceptions outlined in this section.
:*2. A bureaucrat may temporarily demote an administrator if they break a rule (see section E).
+
::*b. A bureaucrat may temporarily demote an administrator if they break a rule (see section E).
:*3. If an administrator resigns or quits, they must notify a bureaucrat so their powers can be removed. The bureaucrat, when demoting them, must refer to the thread in which they quit or resign to show they were responding to that resignation or quitting.
 
  +
:*2. Retirement and resignation
:*4. If an administrator is inactive for at least one (1) month, they are given "inactive" status and their administrative powers are removed.
 
:*5. If an inactive administrator returns after their period of inactivity, their administrative powers may be returned. However, this is limited, per clause 6, below.
+
::*a. Any user who wishes to no longer have their administrative powers and thus retires or resigns can demote themselves. They may notify a bureaucrat to have their powers removed as well.
  +
::*b. If they are a bureaucrat and have not removed their powers but have announced their retirement, resignation, or quitting, a discussion must be created.
:*6. If an administrator is inactive for at least three (3) months, they obtain "former administrator" status.
 
 
::*c. If a user retires or resigns, they cannot receive their rights back immediately. They must make the appropriate request for whatever position.
 
 
::*d. All administrators and chat moderators who say they are going to retire have their rights removed immediately (or pending reasoning/discussion). They must reapply for the rights if they want to resume their position once/if they return.
*H. Returning administrators
 
  +
:*3. Inactivity
:*1. If a former administrator wishes to return, they must request to be an administrator once again.
 
 
::*a. If an administrator is inactive for at least one (1) month, they are given "inactive" status and their administrative powers are removed, with the exception outlined in clause 3e, below.
:*2. If a user retires, resigns, or quits, they cannot recieve their rights back immediately. They must make the appropriate request for whatever position.
 
  +
::*b. If an inactive administrator returns after their period of inactivity, their administrative powers may be returned. However, this is limited, per clause 3c, below.
 
  +
::*c. If an inactive administrator returns after a period of inactivity and wishes to return to the administration, they must consult the demoting bureaucrat. If the demoting bureaucrat does not agree to their reprobation, they must reapply for administrator status.
*I. Announcements of retirement/resignation
 
 
::*d. If an administrator is inactive for at least three (3) months, they obtain "former administrator" status. If they wishe to return to the administration, they must request to be an administrator once again.
:*1. All Admins and Chat Mods who say they're going to retire have their rights removed immediately (or pending reasoning/discussion). They must reapply for the rights if they want to resume their position once/if they return.
 
  +
::*e. If an active administrator goes on an extended vacation or leave of absence with intentions of returning, they obtain "wikibreak" status and clauses 3a, 3b, 3c, and 3d, do no apply to them unless the extended vacation or leave of absence is one (1) year.
   
 
===V. Blocking policy===
 
===V. Blocking policy===

Revision as of 18:13, 14 September 2014

Encyclopedia SpongeBobia
Wiki
General
Policies
Community
Manual of style
Administration
  • Administrators
  • Requests
  • Reviews
Nominations
Social chatrooms
Other
Main page

There are very few policies which apply across all Wikia. These can be found on the Central Wikia at Wikia:Category:Policy.

The policies specific to Encyclopedia SpongeBobia are found below. These rules must be obeyed.

The Rules

I. General policies

  • A. Definitions
  • 1. User - any member of the wiki's community including contributors, administrators, and bureaucrats.
  • 2. Vandalism - any change in content that is intended to be negative.
  • 3. Fanon - any SpongeBob SquarePants in-universe or merchandise-related content not officially released by Viacom via a press conference or the Nickelodeon TV channel, and information that can be derived from that.
  • B. User conduct
  • 1. Do not attack other users personally. This includes threats and name calling.
  • 2. Do not discriminate other users, whether it is religion, political affiliation, sexual preference, or anything else. It is strongly recommended that users do not mention their religion, political affiliation, sexual preference or anything else that could cause tension. A minor biography is all that is necessary, however the administration will never stop you from adding more to your user page, unless any problem arises from comments made.
  • 3. Do not use profanity. You can say "damn" as it was used in the movie, possibly "hell" if in the context. This also means no use of the words such as "f***", even when used as an expletive.
  • a. Any use of profanity in general will result in consequences.
  • b. Any use of profanity directly toward other users will result in a more severe consequence.
  • 4. Do not add or link to content that is inappropriate for younger readers/contributors (someone that is under 8 years old.)
  • C. Vandalism
  • 1. Do not vandalize anything on the wiki.
  • a. Spam
  • b. Nonsense edits
  • c. Removal of good quality content
  • d. Blanking of pages
  • 2. Any user who continues to revert or change articles to a previously lower quality version will be blocked per the blocking policy.
  • D. Fanon
  • 1. Fanon is not allowed on the wiki.
  • 2. All fan-made content is to be placed at the Fanonia SpongeBobia, which was specifically created for such content.
  • 3. Do not insert information that is not true.
  • 4. Do not intentionally insert false dates and/or ages on any article without a source.
  • 5. Any user who violates #4 after an administrator requests a source be provided will result in an infinite block.
  • E. Content
  • 1. This is an encyclopedia and providing accurate information is the top priority.
  • 2. Do not speculate anything. Facts are facts and nothing else matters. Only add if you know it is true. Users are allowed to add paragraphs explaining possibilities on certain topics, but this must worded to let readers know that there is not a definitive fact.
  • 3. Do not create links to articles that do not exist and are not relevant to SpongeBob SquarePants. This is not Wikipedia.
  • 4. Do not create articles that have nothing to do with SpongeBob SquarePants.
  • 5. All guidelines must be follow in regards to article formatting, content, and layout. (See here)
  • 6. Do not use the words "We, I, you, etc." This creates confusion between users and the articles. Refer to everything in the third person.
  • F. Forums
  • 1. When using the forums make sure that the topic presented has something relevant to the topic of the Wiki and SpongeBob SquarePants. Any off topic discussion may result in the closing or removal of the thread, along with any necessary warnings or blockings.
  • G. User Pages/Walls
  • 1. You do not own your userspace, it is given to you to help people know you better. The administration reserves the right to remove any content they feel is inappropriate.
  • 2. Do not forbid anyone from leaving you a message on your message wall.
  • H. Administrators
  • 1. Do not directly ask for the sysop, bureaucrat, rollbacker, or any other similar tool directly. Use the request form here and make sure you qualify.
  • 2. 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.
  • I. Multiple Accounts
  • 1. Each user is only allowed one account, unless you have a good reason that can be approved by the administration. In that event, all users must identify themselves as the owner of the accounts on the user pages.
  • 2. Only administrators may have a bot account. This account must be flagged after a discussion.
  • J. Communication
  • 1. When two or more editors continually revert changes to an article back and forth, this is an edit war. Both parties, when they realize the war is going on, must stop and take the problem to discussion. If the situation cannot be resolved, an administrator may have to step in.
  • 2. If an administrator requests a response from a user regarding an issue, that user must acknowledge and respond to them. If the user makes more than twenty edits after the time of the administrator's message, this will be considered ignoring and consequences will follow.
  • 3. Extended conversations regarding topics unrelated to this wiki or SpongeBob SquarePants in general are not allowed on this wiki. Such conversations will be removed.
  • 4. Do not discuss another wiki's issues on this wiki, it is not the right place for them.
  • K. Personal stuff
  • 1. For your own safety, you are not obliged to reveal your personal information.

II. Episode transcripts

This chapter outlines episode transcript policies.

  • A. Definitions
  • 1. SpongeBob SquarePants fansite - any website that contains SpongeBob SquarePants-related information.
  • 2. Sandbox - a page for testing.
  • B. Policies
  • 1. All episode transcript articles, present and future, will be protected by the administration.
  • 2. Only administrators will be allowed to change the content of the episode transcripts.
  • 3. Contributors outside the administration will have to use the review process to submit and/or make changes to the episode transcripts.
  • 4. All users may use sandboxes to work on transcripts.
  • 5. From the date of the passage of these policies, all future transcripts, in part or in full, that are copied from another SpongeBob SquarePants fansite, is strictly prohibited.
  • 6. Any attempts by any member of the administration to return (including reverting) episode transcript(s) that contain copied material from another SpongeBob SquarePants fansite is strictly prohibited.
  • 7. Any administrator that violates clauses #5 and #6 (see above) will have their powers suspended for thirty (30) days, pending discussion for permanent removal.
  • C. Review Process
  • 1. From the date of the passage of these policies, all episode transcripts must go through a review process before publication.
  • 2. A transcript submission page will be set up for users to submit transcripts (and suggest corrections) to be published here at the wiki.
  • 3. Administrators may submit changes to the transcript articles without the submission process, as long as they do not violate the policies outlined in section B (see above).

III. Discussions

This chapter outlines how we handle discussions.

  • A. Definitions
  • 1. Consensus – when 75% or more of the participants of a discussion are in favor of the proposal after seven (7) days or more of discussion.
  • B. General
  • 1. All major issues must be resolved from 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 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.
  • C. Participants
  • 1. Discussions are completely open to all contributors, except if it involves certain contributors (see clause 2).
  • 2. Any discussion that involves certain contributors, they are excluded from voicing their support or opposition, as they are bias and their opinion is obvious. They are, however, allowed to comment, ask, and answer questions.
  • 3. The person who begins the discussion must make note of those excluded from participating in the decision process (see clause 2).
  • D. Opening discussions
  • 1. Only bureaucrats are permitted to open discussions.
  • 2. Anyone who is not a bureaucrat can draft a proposal, and must receive an endorsement from at least one (1) bureaucrat before the discussion is open. As soon as they receive an endorsement, they or the endorsing bureaucrat can create the discussion.
  • 3. If a non-bureaucrat creates a bureaucrat-endorsed discussion, they must link to the endorsement to show the discussion is valid.
  • 4. After the discussion is created, the endorser must make note of their endorsement on that discussion page for clarification, if the proposal was created by a non-bureaucrat.
  • E. Discussions
  • 1. The discussions must last at least seven (7) days from the date of the creation of the discussion.
  • F. Closing discussions
  • 1. At the end of the seven-day period, in order for a proposal to pass, there must be at least a three-fourths (75%) majority on one side.
  • 2. If there is not a 75% or more majority in favor of the proposal, the discussion continues until it reaches the fourteen (14) day mark. At the point if there is no consensus, the discussion will be closed.
  • 3. In the event that a discussion is closed and an agreement is not reached, another discussion must be created that takes into account compromises discussed in the closed discussion.
  • 4. Any bureaucrat or administrator can close the discussion, as long as the above policies are followed.
  • G. Post-discussion
  • 1. When a proposal passes, the decision is final.
  • 2. Unless otherwise stated, the policy change takes effect immediately.
  • H. Exceptions
  • 1. 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.
  • 2. In the case of non-controversial discussions, a proposal may end after 3 days of discussion if:
  • a. At least 3 administrators support the proposal.
  • b. The discussion has 7 supports and no opposition.
  • c. The discussion has 10 supports and no opposition if the discussion was promoted outside of the community corner.

IV. Administration

This section was revised on September 14, 2014.

  • A. Definitions
  • 1. Administrator - any user of the wiki with sysop privileges.
  • 2. Bureaucrat - any administrator of the wiki with bureaucratic privileges.
  • 3. Active Administrator - any administrator of the wiki that has made contributions within one (1) month preceding the present date.
  • 4. Inactive Administrator - any administrator of the wiki that has not made contributions within one (1) month preceding the present date, but within three (3) months preceding the present date.
  • 5. Suspension - the temporary removal of an administrator's privileges.
  • B. Adminship Requirements
In order for a contributor to qualify for the administration, they must meet the following.
  • 1. User must have at least 750 edits of which at least 400 of these are main namespace edits.
  • 2. User must have been active for at least thirty (30) days from the date of their earliest edit prior to making the request.
  • 3. User must be able to demonstrate that they are willing to help and show good judgment.
  • 4. User must have a reason that is at least five sentences long, demonstrates their understanding of the position, and uses proper spelling and grammar.
  • C. Bureaucrat Requirements
In order for a contributor to qualify for bureaucrat, they must meet the following.
  • 1. User must be a current member of the administration who has been an administrator for at least two (2) years.
  • 2. User must have at least 2,000 edits, of which at least 1,000 are main namespace edits.
  • 3. User must demonstrate that all their edits are positive, and further the goal of improving the wiki.
  • 4. User must demonstrate use of proper spelling and grammar.
  • 5. User must demonstrate good reasons for any questionable edits.
  • 6. User must have full support of all other active bureaucrats.
  • 7. User must have support from a majority of active administrators.
  • 8. Any administrator requesting promotion to bureaucrat that does not meet the criteria outlined in clause 1, 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.
  • D. Application Process
  • A user seeking to be an administrator or bureaucrat must follow these procedures:
  • 1. They must follow the requirements, or their application will be deleted by an administrator.
  • 2. They must create a request page using the form, and provide a reason that follows the above criteria.
  • 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).
  • E. Decision Process
  • 1. Length of request
  • a. Administrator and bureaucrat requests are to last no shorter than seven (7) days from the time the applicant makes the request.
  • b. If an applicant has the support of at least 90% of participating administrators, they may be promoted after three (3) days.
  • 2. The applicant is promoted under the following circumstances:
  • a. They have at least three quarters (75%) support.
  • c. If more than half (50%) of active administrators do not support the user's application, the request is unsuccessful and may be closed.
  • 3. Only bureaucrats can close the discussion, as they have the ability to promote those that are successful in their application.
  • 4. If a user makes an administrator request but fails to be promoted, they must wait at least thirty (30) days before making another request, unless their request is endorsed by all active administrators.
  • F. Administrator Duties
  • 1. When a user is promoted to the administration, they have more privileges than the average user. They are expected to use these powers with good judgment and follow all the rules.
  • 2. In the event that an administrator is not following the rules and/or are abusing their powers, a bureaucrat must inform them of their wrongdoing, in case of any misinterpretations.
  • 3. If after #2 above, the administrator does not stand down or admit to wrongdoing and thus the bureaucrat fails to resolve the issue, they may demote the administrator for a suspension of one (1) week.
  • 4. After the suspension (clause 3, above), the said bureaucrat must then create a discussion for the community to discuss the situation, and decide whether or not the user should be demoted permanently, temporarily, or reinstated.
  • 5. Any administrator who is demoted after their adminship is terminated, obtains "former administrator" status.
  • G. Retirement, resignation, and inactivity: some changes, additions, and clarifications
  • 1. General
  • a. All administrators keep their administrative powers as long as they want, with the exceptions outlined in this section.
  • b. A bureaucrat may temporarily demote an administrator if they break a rule (see section E).
  • 2. Retirement and resignation
  • a. Any user who wishes to no longer have their administrative powers and thus retires or resigns can demote themselves. They may notify a bureaucrat to have their powers removed as well.
  • b. If they are a bureaucrat and have not removed their powers but have announced their retirement, resignation, or quitting, a discussion must be created.
  • c. If a user retires or resigns, they cannot receive their rights back immediately. They must make the appropriate request for whatever position.
  • d. All administrators and chat moderators who say they are going to retire have their rights removed immediately (or pending reasoning/discussion). They must reapply for the rights if they want to resume their position once/if they return.
  • 3. Inactivity
  • a. If an administrator is inactive for at least one (1) month, they are given "inactive" status and their administrative powers are removed, with the exception outlined in clause 3e, below.
  • b. If an inactive administrator returns after their period of inactivity, their administrative powers may be returned. However, this is limited, per clause 3c, below.
  • c. If an inactive administrator returns after a period of inactivity and wishes to return to the administration, they must consult the demoting bureaucrat. If the demoting bureaucrat does not agree to their reprobation, they must reapply for administrator status.
  • d. If an administrator is inactive for at least three (3) months, they obtain "former administrator" status. If they wishe to return to the administration, they must request to be an administrator once again.
  • e. If an active administrator goes on an extended vacation or leave of absence with intentions of returning, they obtain "wikibreak" status and clauses 3a, 3b, 3c, and 3d, do no apply to them unless the extended vacation or leave of absence is one (1) year.

V. Blocking policy

  • A. Definitions
  • 1. Block - a temporary suspension of a user's ability to contribute to the wiki.
  • 2. Ban - a permanent removal of a user's ability to contribute to the wiki.
  • B. General
  • 1. Administrators are privileged with the power to block other users and are expected to have good judgment when it comes to using this power.
  • 2. Administrators must follow the established blocking policy. Any exceptions require a community discussion.
  • 3. Any administrator who fails to follow the blocking procedures after one (1) warning from a bureaucrat will be suspended for seven (7) days.
  • 4. After the administrator's 7-day suspension, their administrative powers shall be returned. If the administrator continues to violate the blocking procedures after one (1) warning from a bureaucrat, they will be given a 14-day suspension, pending discussion on the administrator's user rights.
  • C. Procedures
  • 1. Administrators that find a user violating any of the policies must revert any changes and must 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 must break the same rule two (2) times before being blocked.
  • 3. If a warned user continues to edit 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 edit for twenty-four (24) hours after the administrator have 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 severity of the offense. The blocks will follow this format:
  • a. 3rd offense: 1-month block
  • b. 4th offense: 3-month block
  • c. 5th offense: 6-month block
  • d. 6th offense: 1-year block
  • e. 7th offense: infinite block
  • 6. The preceding clauses (1 through 5, above) are the blocking policy and must be followed, except for the clauses outlined in section D, "Exceptions," below.
  • D. Exceptions
  • 1. Any user who makes any contributions that are very serious to the point in which they harm the wiki or threaten a user, they may be infinitely blocked immediately, pending a block review (see section D, clause 4, below).
  • 2. The administrator who infinitely blocks a user due to section D, clause 3, above, must create a block review to determine that the block is legitimate. Three administrators must endorse the block before it is legal. These two clauses are in place for emergencies in which a user may do seriously harm on the wiki.
  • 3. Any user who spams and/or vandalizes as their first edit will automatically be blocked for a maximum of fourteen (14) days. If they continue to spam and/or vandalize after their block, they shall be given an infinite block.
  • 4. This clause outlines items that are not block-worthy, and such are deemed "unfair."
  • a. Anyone who misspells a word or misuses grammar shall not be blocked.
  • b. Anyone who begins a page without proper formatting shall not be blocked.
  • c. Anyone who makes an accidental edit shall not be blocked.
  • E. Appealing a block
  • 1. Any user who is blocked or banned may appeal to have the block or ban removed if they deem it unfair.
  • 2. The appeal will be in the form of a discussion that will follow the discussion policies and last seven (7) days.
  • 3. In this case, it is required to allow the user to edit their talk page/message wall no matter what the issue is.
  • 4. If the blocked user handles the block without verbally/personally attacking the blocking administrator or violating any other user conduct rules, they will be allowed to make an appeal on their talk page/message wall.
  • 5. If the blocked user violates any user conduct rules, the will be blocked from using their talk page/message wall and the opportunity to appeal a block.
  • 6. If the appeal fails, the block will not be reverted.
  • 7. If a banned user fails an appeal, they must wait six (6) months before creating another appeal.

VI. Page names

  • A. Definitions
  • 1. Page title - the title of the article that appears at the top of the page and the URL
  • 2. Page header - individual headers within the article are designated by equals signs (i.e. ===Header===)
  • B. Policy
  • 1. All page titles and headers may only use capitals if:
  • a. The beginning word in the title and/or header
  • b. Proper nouns in the title and/or header
  • 2. The only exception is that only a word directly after a colon (:) or slash (/) may or may not use capital letters.

Examples:

Correct Incorrect
Bikini Bottom bikini bottom
Galley Grub Galley grub
SpongeBob SquarePants:Discussions/Page titles and headers SpongeBob SquarePants:Discussions/Page Titles and Headers
List of food and drinks List of Foods and Drinks
Plankton's cousins Plankton's Cousins
List of instances in which the fourth wall is broken List of Instances in Which the Fourth Wall is Broken
==External links== ==External Links==
==See also== ==See Also==

VII. User of the Month

  • A. User of the Month
  • 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) 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.
  • 3. Any contributor can participate in the nomination discussion, as long as they meet the following criteria:
  • a. Participants must have at least one hundred (100) main namespace edits.
  • b. Participants must have been an active contributor for at least one (1) month.
  • c. Participants must leave a comment along with their support, oppose, or neutral, otherwise their opinion doesn't count in the final decision.
  • d. All administrators within the SpongeBobia network are allowed to participate in the discussions.

VIII. Article of the Month

  • A. Article of the Month
  • 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.

IX. Advertising and affliation

  • A. Advertising
  • 1. Advertising other wikis at Wikia is okay, as long as the following policies are followed:
  • a. Do not send messages to specific individuals through their message wall to visit a certain wiki.
  • b. The forums are the only place one can advertise another wiki at Wikia.
  • c. Do not create more than one forum topic in advertising a website, unless any previous forum topics have been deleted.
  • 2. Advertising other websites that are not on Wikia requires administrative approval.
  • a. If you want to advertise a non-Wikia website, you must first send a request to an administrator and such request will be discussed at the next meeting.
  • 3. Any violation of these policies will result in a deletion of anything relating to that website and a warning.
  • B. Affiliation
  • 1. An affiliation page will be set up to list our affiliates. If you want to affiliate with us, send a message to an administrator and such will be discussed at the next meeting.
  • 2. If you affiliate with any site in the SpongeBobia network, you must link to us from your website, otherwise you will be removed from our affiliates page.

X. Signatures

  • 1. All signatures must contain a person's username or something that lets people know who the user is.
  • 2. All signatures linking to their message wall and/or contributions must indicate what the page is.
  • 3. All signatures must not exceed the height of a line of text, unless they are an image that follows #4, below.
  • 4. All signatures must not disturb the layout or text of the page in any way.
  • 5. Administrators reserve the right to adjust signatures according to the guidelines.

XI. Stubs

  • 1. A stub is an article that is less than 1,000 bytes.
  • 2. Any article that is defined as a stub but also is an article in which all information is complete, is no longer considered a stub, no matter the length. Example: Since a stub is considered to be less than 1,000 bytes, and a certain article is 700 bytes, yet it is almost impossible to add any more information, the article can no longer be considered a stub.

XII. Meetings

  • A. General
  • 1. Every two weeks, the SpongeBobia network community is to hold meetings to discuss many different aspects of the wiki, including projects, tasks, design, ideas, issues, and others.
  • 2. Meetings will be held at 3 p.m. eastern time in the SpongeBobia chat room.
  • 3. All community members are invited to attend the meetings.
  • 4. Anyone who is disruptive to the flow of the meeting may be asked to leave or kicked. If they are persistant in disrupting the meeting, they will be banned for 2 hours (or until the meeting ends).
  • 5. If a meeting is cancelled, the meeting will be held the following week, and continue in the "every two weeks" meeting schedule.
  • B. Procedures
  • 1. Each week, an agenda of topics will be gathered for the meeting, which will serve as the order in which the topics are discussed, with more important topics first.
  • 2. Each item will be discussed before moving on to the next one.
  • 3. Ideas for each item will be collected and a summary will be presented at the end.

XIII. Chat

  • A. General
  • 1. All ESB policies apply in the chat room.
  • 2. No spamming. This includes blank messages and typing gibberish.
  • 3. No trolling. Such violation results in an immediate ban.
  • 4. No profanity (except for the words "damn" and "hell," which are allowed if they are used in context and not against another user)
  • 5. Be respectful toward all users, their views, and their opinions. Do not discriminate or harrass anyone.
  • 6. Do not pose as a chat moderator or administrator if you are not.
  • 7. Do not post anything inappropriate or links to inappropriate sites. This includes links content not suitable for children under the age of 13. The chatroom is to remain clean.
  • 8. Do not ask users for personal information. (age, phone numbers, addresses, ASL (age/sex/location), etc.)
  • 9. If you are going to exchange social networking information, do it in a private message (such as Skype, Facebook, Twitter, YouTube, etc.).
  • 10. Do not argue or get into a heated debate. Friendly, civil debates are allowed.
  • B. Underage users
  • 1. It is against Wikia policy for a person under the age of 13 to use Wikia. It is against ESB policy for persons under the age of 13 to reveal their age.
  • 2. Any users who is underaged or claims to be underaged will not be blocked or banned.
  • 3. All underaged users will be dealt with by Wikia Staff, not by ESB staff.
  • C. Moderators
  • 1. All administrators and bureaucrats are chat moderators. A selected few chatters are granted chat moderator status because they are active in chat and trusted to keep the peace.
  • 2. Do not kick or ban users for no reason.
  • 3. Any abuse of chat moderator powers will result in immediate demotion. Any continued abuse may result in a block.
  • 4. Chat moderators have no jurisdiction over what happens in a private message. If someone bothers you, ignore them. There is no definite way to prove what is in a private message.
  • 5. There is a hierarchy in the chatroom. Chat Moderators are outranked by Administrators, and Admistrators are outranked by Bureaucrats. Therefore, if a user is breaking a rule in chat, the users highest in command will deal with them. If they are unresponsive, the responsibility goes down the chain of hierarchy.
  • D. Reporting
  • 1. If you see anything in the chatroom that is a violation of any policies, please report it.
  • 2. You can report it to the following places:
  • a. Chat report - list your report here.
  • b. Private message an administrator or bureaucrat. You can find a list here: ESB:Administration.

XIV. Tasks

  • A. General
  • 1. A task is a specific item that needs to be completed on the wiki.
  • 2. Tasks are not like badges, because while badges are awarded based on edits, tasks awards are given based on article quality/completion.
  • 3. Tasks function like quests, in which all users have the opportunity to win these specific awards on a leader board and attain certain titles.
  • B. Task procedures
  • 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 and update the leaderboard with the correct number of points. Note that the term "finishing" or "finish" is used loosely as such may not be complete in the future, or require minor adjustments.
  • a. Minor tasks (10 points) - such as copy editing a section, fixing a certain image (such as obtaining something of higher quality).
  • b. Adding a source for something unsourced (20 points)
  • c. Converting a list into a table (100 points)
  • d. Finishing a gallery (100 points)
  • e. Finishing an "appearance" list (150 points)
  • f. Finishing a transcript (250 points)
  • 5. Points are not awarded to the above items if they were not specifically put up as a task. Example: If a user finishes a transcript without that being a task, the points do not count.
  • 6. The person who creates the task cannot be awarded for completing the task.
  • 7. When a task does not have a predetermined amount for a point value, such must be discussed and passed before it applies.

XV. Quote contests

  • A. General
  • 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
  • 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
  • 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.

XVI. 3 Revert Rule

  • A. 3 Revert Rule
  • 1. An editor must not perform more than three reverts on a single page—whether involving the same or different material—within a 24-hour period. An edit or a series of consecutive edits that undoes other editors' actions—whether in whole or in part—counts as a revert. Any appearance of gaming the system by reverting a fourth time just outside the 24-hour slot is likely to be treated as an edit-warring violation.
  • B. Exceptions to 3 Revert Rule
  • 1. Reverting your own actions ("self-reverting").
  • 2. Reverting edits to pages in your own user space, so long as you are respecting the user page guidelines.
  • 3. Reverting actions performed by banned users, and sockpuppets of banned and blocked users.
  • 4. Reverting obvious vandalism—edits that any well-intentioned user would agree constitute vandalism, such as page blanking and adding offensive language.
  • 5. Removal of clear copyright violations and any illegal content.
  • C. After 3 reverts
  • 1. When a page is reverted after 3 times by the same user, the editing must stop and be reported to an administration.
  • 2. If the edit war continues after intervention, those users are subject to a 24-hour block.