| This page is an official policy of Battlestar Pegasus.
This policy is considered by the community and its leadership to be the status quo of Battlestar Pegasus and is not to be countermanded or ignored, though changes to it can be discussed on the appropriate talk page. This policy was implemented on 1 November 2007.
|
|
This policy goes over the placement and verification of such information, as well as how the viewer can be forewarned when visiting an article containing such information.
What's a spoiler?
- Main article: Help:Spoiler
Since a spoiler is a piece of information that reveals a plot point or new piece of information about a character not previously encountered by a viewer, the term "spoiler" can apply to anything, depending on how much or how little a person has been exposed to BSG. Since it is impossible to deal with all these irreconcilable, diverse view points, we have had to narrow down the definition of a spoiler.
Thus a "spoiler" has been redefined as being one or more pieces of information from an episode that has yet to air anywhere in the world, regardless of their perceived size or impact.
General Policy
This site recognizes that there are those who believe such information is detrimental to their viewing habits, while others are indifferent to being "spoiled" as it does not affect their habits either way. Therefore, the following measures are to be adhered to:
- Information on unaired episodes can be added to any article on this site, but shall be tagged with a spoiler warning message, as described below:
- For articles completely relating to an unaired episode, the tag -- {{spoiler}} -- shall go on the first line of the article's text, before any other text and templates.
- For articles containing a mix of information from aired and unaired episodes, spoiler information should be encased in the {{spoiltext}} template. For example, a person would enter: {{spoiltext|Adama gets shot in the chest by Boomer in this final act of this episode.}}. This will effectively "black out" this information to the casual viewer, allowing the viewer to select the text should he or she wish to be spoiled. {{spoilli}} does the same thing but it's used for list sections. For example, a person would enter: *{{spoilli|Your text here...}}.
- All spoiler information must have a source, whether in the form of a URL or a printed publication text, on the talk page of the spoilerific article. For printed publication text, a copy must be scanned and uploaded to the site in the form of a JPG or PNG, and posted on the talk page of the article containing the spoilerific content.
- Failure to follow the above procedure(s) shall result in removal of spoiler information. Should the behavior persist, consequences outlined further in this policy text shall be implemented.
- Information located on user or talk pages does not need to be tagged with {{spoiler}}. These are "neutral zones", though it is suggested that users keep in mind other users who may not feel the same way they do regarding spoilers when adding content to both talk and user pages.
- Once the episode has been aired -- or is airing at the time of a user's editing -- information revealed in that aired or airing episode can no longer be considered "spoilerific". This is regardless of whether or not the episode has yet to air anywhere else. (i.e. Episode 2.11 has aired in the United States, but not in England; just because it hasn't aired in England doesn't make the episode "spoilerific", as it has already aired in the U.S.)
Related Templates
- {{spoiler}}: For use with pages that contain mostly spoilerific information.
- {{spoiltext|text}}: For use with text that is spoilerific, but the page mostly contains information that is not spoilerific.
- {{spoilerbelow}}: Same as {{spoiler}}, but tell the user that below this bar is when the spoiler starts.
Enforcement of Policy
Repeated failure to obey this policy will result in the user being warned on his or her talk page. Dismissal of the warnings may result in short-term or long-term banning, depending on the circumstances.
| 
