SpongeBob SquarePants


on ESB
Encyclopedia SpongeBobia
Manual of Style
  • Administrators
  • Requests
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 following is an index to the policies of Encyclopedia SpongeBobia. These are broken into different categories:

  • I. Policies and procedures - the rules of the wiki and how different aspects function
  • II. Guidelines - the Manual of Style for the wiki in regards to content formatting, templates, etc.


The following is a key to the format of ESB policy.

  • Article - each policy is broken down into articles, which categorize a particular policy category and are designated by Roman numerals (I, II, III, etc.)
  • Section - each article is broken down into sections for organizational purposes. These are designated by capital letters (A, B, C, etc.)
  • Clause - a section may be divided into a clauses for further organizatonal purposes. These are disignated by numbers (1, 2, 3, etc.)
  • Subclauses - clauses may be divided further (a, b, c, etc. and i, ii, iii, etc.)

The Rules

I. Definitions

  • A. Introduction
  • 1. The definitions in this section apply to the entire policy page.
  • B. Definitions
  • 1. Active Administrator - any administrator of the wiki that has made contributions within one (1) month preceding the present date.
  • 2. Administrator - any user of the wiki with sysop privileges.
  • 3. Ban - a permanent removal of a user's ability to contribute to the wiki.
  • 4. Block - a temporary suspension of a user's ability to contribute to the wiki.
  • 5. Bureaucrat - any administrator of the wiki with bureaucratic privileges.
  • 6. 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.
  • 7. Content dispute - any disagreement in regards to content on the wiki.
  • 8. Edit war - a dispute in which two or more editors revert changes to an article back and forth between opposing revisions.
  • 9. 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.
  • 10. 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.
  • 11. Page header - individual headers within the article are designated by equals signs (i.e. ===Header===)
  • 12. Page title - the title of the article that appears at the top of the page and the URL
  • 13. Partial revert - reversing only part of a prior edit, while retaining other parts of it.
  • 14. Revert - reversing a prior edit, which typically results in the article being restored to a version that existed sometime previously.
  • 15. Sandbox - a page for testing.
  • 16. SpongeBob SquarePants fansite - any website that contains SpongeBob SquarePants-related information.
  • 17. Suspension - the temporary removal of an administrator's privileges.
  • 18. User - any member of the wiki's community including contributors, administrators, and bureaucrats.
  • 19. Vandalism - any change in content that is intended to be negative.

II. General policies

  • 1. Do not attack other users personally.
  • a. Do not make threats toward the wiki or any user.
  • b. Do not call any user any name directly or in reference to said user that are deemed derogatory. This includes, but is not limited to: idiot, jerk, stupid, retard, etc.
  • c. Accusing or assuming a user have a certain condition, especially in a discriminatory way.
  • 2. Do not discriminate other users based on their 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.)
  • 5. Do not correct other people's use of grammar on discussion pages, message walls, or the forums unless it is in regards to grammar use in an article.
  • 6. Any issue that anyone may have with a user may be reported to the report user page.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 1. 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.
  • 2. Extended conversations regarding topics unrelated to this wiki or SpongeBob SquarePants in general are not allowed on this wiki. Such conversations will be removed.
  • 3. Do not discuss another wiki's issues on this wiki, it is not the right place for them.
  • 1. For your own safety, you are not obliged to reveal your personal information.

III. Episode transcripts

  • 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.
  • 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).

IV. Discussions

  • 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.
  • 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).
  • 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.
  • 1. The format of discussions will be in two phases.
  • a. Phase 1: Initial voting phase
  • i. An issue, situation, and/or policy change will be brought up by a bureaucrat.
  • ii. All users will be given a chance to voice their opinion on the issue, situation, and/or policy change.
  • iii. After one (1) week of discussion, the discussion phase will be closed.
  • iv. All users are permitted to vote, but these votes are unofficial. The only officially counted votes occur in the voting phase (see subsection b, below) with the exception of clause v, below.
  • v. If there is no disagreement in the discussion, there is no need for a voting phase, and the votes from phase 1 can be tallied.
  • vi. However, if 50% or more of participants of the initial vote agree there is something wrong with the proposal, the discussion must enter the discussion phase.
  • b. Phase 2: Discussion phase
  • i. Since an agreement was not reached in phase 1, a discussion must be open for at least one (1) week to gather input from participants.
  • ii. There will not be a vote held during this phase.
  • c. Phase 3: Second voting phase
  • i. The bureaucrat closing the discussion phase will list all options collected from the discussion in a new voting phase section.
  • ii. All users will be given a chance to vote on each option.
  • iii. After one (1) week of voting, the voting phase will be closed. Exceptions are outlined in section H.
  • 2. Variations
  • a. If a discussion requests suggestions for a particular topic and any suggestion is presented, the discussion will enter a second discussion in order to incorporate any new suggestion(s).**
  • 1. Only bureaucrats are permitted to open discussions.
  • 2. Anyone who is not a bureaucrat can draft a discussion, 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.
  • 1. At the end of the voting phase, in order for a proposal or option to pass, there must be at least a three-fourths (75%) majority.
  • 2. If there is not a 75% or more majority in favor of the proposal or option, the discussion is concluded to have "no consensus" and 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.
  • 1. When a proposal passes, the decision is final.
  • 2. Unless otherwise stated, the policy change takes effect immediately.
  • 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 four (4) administrators support the proposal.
  • b. The discussion has ten (10) supports and no opposition.

V. Administration

  • 1. There are no requirements prior to making a request to be an administrator.
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.
  • 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).
  • 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 seven (7) days before making another request, unless their request is endorsed by all active administrators. (revised September 28, 2014)
  • 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.
  • 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 repromotion, 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 wish 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.

VI. Non-administrative roles

  • A. General
  • 1. In addition to administrators and bureaucrats, there are other non-administrative postitions at Encyclopedia SpongeBobia.
  • 1. An assistant serves as an in-between users and administrators for purposes such as editing protected pages, among other things. An assistant cannot block or delete.
  • 2. No application process exists and a user is appointed assistant at the discretion of the bureaucrats per clause 3, below.
  • 3. A majority of bureaucrats (50% or more) must support the promotion of a user to this position.
  • C. Rollback
  • 1. A rollback can quickly rollback the edits of the last user who edited a particular page.
  • 2. No application process exists and a user is appointed rollback at the discretion of the administration.
  • D. Moderator
  • 1. No application process exists and a user is appointed moderator at the discretion of the administration.
  • E. Chat moderator
  • 1. A user requesting to be a chat moderator must fill out an application and a discussion will follow.

VII. Blocking policy

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

VIII. 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.

IX. 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.

X. Advertising and affliation

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

XI. Signatures

I love you patrick star by thunderbulletmlp-d6cclg7

This is what 30 pixels looks like.

  • 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.
  • 1. Users are permitted to have images in their signatures, or as their signature, so long as the height does not exceed 30 pixels. This includes animated signatures, but some may stop animating below a certain pixel size. Images over 30 pixels cause the spacing between two lines of text to be disproportionate, and animated signatures can result in longer load times for discussion pages. As a general guideline, however, please do not use images or font sizes that will interfere with the lines of text.
  • 1. As said in the section above, signatures may not be more than 30 pixels high. This includes big font sizes, but also the length of a signature. A signature may not be so long that when viewed in the Wikia skin with the toolbar aside it, it is wider than one line. Also, signatures may not take up more than one line (any enters in the signature's code should be removed, as when it is used in an indented list (replies to others) it will break up the signature when there are enters in the code). The <noinclude> tag may be put around enters to make the code look cleaner, or <!-- and --> may be put around codes to prevent them from having such effects.
  • 1. Names used in signatures must be consistent with the Wikia username. In order to prevent confusion, users should not use alternate names when signing edits. Names should at least be recognizable (e.g. User:RandomUser305 signing off as "RU305"), but not differ too greatly as to mistake the signature for a different user.
  • 1. Any links on a signature that do not operate in the way they appear are forbidden as they can cause confusion among users. This includes links that log users out.
  • 2. A user's signature that has the text colored in any way that will cause confusion among users is not allowed.

XII. Meetings

  • 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 4 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.
  • 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

  • 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.
  • 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.
  • 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.
  • 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:

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.
  • 5. All tasks and points are to be listed here: ESB:Tasks
  • 6. 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.
  • 7. The person who creates the task cannot be awarded for completing the task.
  • 8. 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

  • 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.
  • 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}})
  • 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. Content dispute

  • 1. This article will outline the proper procedures in the event of an edit war and/or relating to content dispute.
  • B. Dispute
  • 1. General
  • a. Not everyone will agree on how things should be done on the wiki. However, in order to have consistency and organization within the wiki, it is important to establish policies and formatting guidelines for everyone to follow in which the community agrees upon.
  • b. As this is a collaborative environment, it is important to resolve disputes by using communication to address the problem instead of ignoring the problem.
  • C. Procedures
  • 1. Edit war
  • a. When an edit war occurs, all parties must stop editing the article and take the problem to an informal discussion on one of the editor's message walls or in a forum post and explain their reasons for their edits.
  • b. Once they have explained their reasons, they must follow the procedures below to resolve the dispute.
  • 2. Procedures
  • a. If an established policy and/or guideline can resolve the dispute, that policy and/or guideline must be followed.
  • b. If there is disagreement in regards to the policy and/or guideline, discussion is allowed, but the reverts must be halted so that the disputed content on the article is left alone until the dispute is resolved.
  • c. If the dispute is not resolved in clause 2b, above, an uninvolved administrator must step in to mediate the discussion.
  • d. If the dispute involves one (1) or more administrators, a bureaucrat uninvolved in the edit war must intervene.
  • e. If all bureaucrats are involved in the edit war, an official discussion is required.
  • f. In the event that no such policy and/or guideline exists to establish a resolution policy-wise, the dispute may require further discussion that will ultimately be decided in an official discussion to establish a policy and/or guideline.
  • 3. Conclusion
  • a. Once the dispute is resolved, the decision is final. Any edit made by the losing party in the dispute that blatantly ignores the decision is subject to a maximum three (3) day block.
  • b. If any user is in disagreement over the decision, they are free to make a petition to change the guidelines/policies/rules/etc.
  • D. 3 Revert Clause
  • 1. General
  • a. 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.
  • 2. Exceptions
  • a. Reverting your own actions ("self-reverting").
  • b. Reverting edits to pages in your own user space, so long as you are respecting the user page guidelines.
  • c. Reverting actions performed by banned users, and sockpuppets of banned and blocked users.
  • d. Reverting obvious vandalism—edits that any well-intentioned user would agree constitute vandalism, such as page blanking and adding offensive language.
  • e. Removal of clear copyright violations and any illegal content.
  • 3. After 3 reverts
  • a. During an edit war, when a page is reverted after three (3) times by the same user, the editing must stop and be reported to an administrator.
  • b. If an administrator is involved in the edit war, the following procedures must be followed:
  • i. The article must be protected by any administrator and no further reverts made in regards to the disputed content.
  • ii. An uninvolved bureaucrat must intervene to mediate the dispute.
  • iii. All succeeding procedures are outlined in the "dispute" section C2 of this article.
  • c. If the edit war continues after a user has made 3 reverts, the following must be followed:
  • i. Dispute between non-administrators
  • 1. At this point, the page should have been protected by an administrator and the edit war should have stopped.
  • ii. Dispute between non-administrators and administrators in which the administrators are in agreement.
  • 1. At this point, the page should have been protected by an administrator and the edit war should have stopped.
  • iii. Dispute between non-administrators and administrators in which the administrators are in disagreement.
  • 1. It is expected that the dispute between administrators be resolved by discussion and that the edit war does not continue.
  • 2. Any such violation of this requires an informal discussion to the matter or an official discussion if the matter is serious.
  • iv. Dispute between only administrators in which the administrators are in disagreement.
  • 1. It is expected that the dispute between administrators be resolved by discussion and that the edit war does not continue.
  • 2. Any such violation of this requires an informal discussion to the matter or an official discussion if the matter is serious.

XVII. Requests for deletion process

  • A. General
  • 1. This is an optional process; administrators can delete anything they believe is necessary
  • 2. Anyone can nominate an article the feel should be deleted.
  • B. Process
  • 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.
  • 3. A discussion will occur, centered on that particular article, template, category, etc.
  • 4. Neutral votes do not count in the final tally for concensus (75%)

Wikia Spotlight

Random Wiki