Article snapshot taken from Wikipedia with creative commons attribution-sharealike license.
Give it a read and then ask your questions in the chat.
We can research this topic together.
(6 intermediate revisions by the same user not shown)
Line 55:
Line 55:
''Never'' edit someone's words to change their meaning, even on your own talk page. Editing others' comments is sometimes allowed, but you should exercise caution in doing so. Some examples of appropriately editing others' comments:
''Never'' edit someone's words to change their meaning, even on your own talk page. Editing others' comments is sometimes allowed, but you should exercise caution in doing so. Some examples of appropriately editing others' comments:
* If you have their permission
* If you have their '''permission'''
* Removing '''prohibited material''' such as libel and personal details
* Removing '''prohibited material''' such as libel and personal details
* Deleting material not relevant to improving the article (per the above subsection ]).
* Deleting material not relevant to improving the article (per the above subsection ]).
Line 67:
Line 67:
* If a thread has veered off its original subject, it may be desirable to '''split threads''', especially if the new topic is deemed to merit extensive discussion. When part of a discussion is made into its own thread, the new thread should include an opening sentence or paragraph explaining the reason for the move and containing a link to the original thread. As well, a note should be placed at the location the discussion was moved ''from'', with a link to the new thread. It is also important that the format of the existing discussion remains essentially the same. Simple cutting and pasting will not always ensure that this happens; a bit of reformatting may be necessary. When splitting a thread, '''always''' preview how your changes appear and check to see whether the flow of the thread remains the same as it was previously (i.e. that all replies are in the correct places.) Splitting a thread should '''not''' in any way alter the meaning of any comments therein; hence the need for links, proper formatting, and an explanation.
* If a thread has veered off its original subject, it may be desirable to '''split threads''', especially if the new topic is deemed to merit extensive discussion. When part of a discussion is made into its own thread, the new thread should include an opening sentence or paragraph explaining the reason for the move and containing a link to the original thread. As well, a note should be placed at the location the discussion was moved ''from'', with a link to the new thread. It is also important that the format of the existing discussion remains essentially the same. Simple cutting and pasting will not always ensure that this happens; a bit of reformatting may be necessary. When splitting a thread, '''always''' preview how your changes appear and check to see whether the flow of the thread remains the same as it was previously (i.e. that all replies are in the correct places.) Splitting a thread should '''not''' in any way alter the meaning of any comments therein; hence the need for links, proper formatting, and an explanation.
* '''Section headers''': Because threads are shared by multiple users, the original title becomes communal property. To avoid disputes it is best to discuss changes with the editor who started the thread, if possible, but it is generally acceptable to change section headers when a better header is appropriate. This is under the purview of threads themselves being shared property rather than a single editor's comments.
* '''Section headers''': Because threads are shared by multiple users, the original title becomes communal property. To avoid disputes it is best to discuss changes with the editor who started the thread, if possible, but it is generally acceptable to change section headers when a better header is appropriate. This is under the purview of threads themselves being shared property rather than a single editor's comments.
* '''Disambiguating''' or '''fixing''' links (if the linked-to page has moved, or a talk page section has been archived, or the link is simply broken by a typographical error, for instance).
* Hiding or resizing '''images''': You may re-seize over-large images; or hide an image (e.g. change <nowiki>]</nowiki> to <nowiki>]</nowiki> by adding a colon) ''once discussion of it has ended''.
*'''De-linking categories''': you may make category links in active (e.g. change <nowiki>]</nowiki> to <nowiki>]</nowiki> by adding a colon) to prevent the page from being added to a discussed category.
*'''Code samples''': You may redact (replace with a note, or collapse) large code samples ''once discussion of the sample has ended''; for instance fulfilled {{tl|editprotected}} requests.
The purpose of a Misplaced Pages talk page is to provide space for editors to discuss changes to its associated article or project page. Article talk pages should not be used by editors as platforms for their personal views.
When writing on a talk page, certain approaches are counter-productive, while others facilitate good editing. The prime values of the talk page are communication, courtesy and consideration. The following list is designed to help Wikipedians use talk pages effectively.
Central points
Maintain Misplaced Pages policy
The policies that apply to articles also apply (if not to the same extent) to talk pages, including Misplaced Pages's verification, neutral point of view and no original research policies. There is of course some reasonable allowance for speculation, suggestion and personal knowledge on talk pages, with a view to prompting further investigation, but it is usually a misuse of a talk page to continue to argue any point that has not met policy requirements.
Editors should remove any negative material about living persons that is either unsourced, relies upon sources that do not meet standards specified in Misplaced Pages:Reliable sources, or is a conjectural interpretation of a source.
How to use article talk pages
Communicate: If in doubt, make the extra effort so that other people understand you, and you get a proper understanding of others. Being friendly is a great help. It is always a good idea to explain your views; it is less helpful for you to voice an opinion on something and not explain why. Explaining an opinion helps in convincing others and reaching consensus.
Keep on topic: Talk pages are for discussing the article, not for general conversation about the article's subject (much less other subjects). Keep discussions on the topic of how to improve the associated article. Irrelevant discussions are subject to removal.
Be positive: Article talk pages should be used to discuss ways to improve an article; not to criticize, pick apart, or vent about the current status of an article or its subject. This is especially true on the talk pages of biographies of living people. However, if you feel something is wrong, but are not sure how to fix it, then by all means feel free to draw attention to this and ask for suggestions from others.
Stay objective: Talk pages are not a forum for editors to argue their own different points of view about controversial issues. They are a forum to discuss how the different points of view obtained from secondary sources should be included in the article, so that the end result is neutral and objective (which may mean including conflicting viewpoints). The best way to present a case is to find properly referenced material (for an alternative forum for personal opinions, see the Wikibate proposal).
Deal with facts: The talk page is the ideal place for all issues relating to verification. This includes asking for help to find sources, comparing contradictory facts from different sources, and examining the reliability of references. Asking for a verifiable reference to support a statement is often better than arguing against it.
Share material: The talk page can be used to store material from the article which has been removed because it is not verified, so that time can be given for references to be found. New material can sometimes be prepared on the talk page until it is ready to be put into the article.
Discuss edits: The talk page is particularly useful to talk about edits. If one of your edits has been reverted, and you change it back again, it is good practice to leave an explanation on the talk page and a note in the edit summary that you have done so. The talk page is also the place to ask about another editor's changes. If someone queries one of your edits, make sure you reply with a full, helpful rationale.
Make proposals: New proposals for the article can be put forward for discussion by other editors if you wish. Proposals might include changes to specific details, page moves, merges or making a section of a long article into a separate article.
Good practice
Sign your posts: To sign a post, type four tildes (~~~~), and they will be replaced with your username and time stamp, like this: Example13:21, 9 May 2008 (UTC). Please note that it is impossible to leave an anonymous comment because your user name or IP address is recorded in the page history.
Avoid excessive markup: It undermines a reasoned argument with the appearance of force through Italic text, Bolded text, and especially CAPITAL LETTERS, which are considered SHOUTING, and RANTING!!!!! Italics, however, can be usefully employed for a key word, to distinguish quoted text from new text and, of course, book titles etc.
Be concise: If your post is longer than 100 words, consider shortening it. Long, rambling messages are difficult to understand, and are frequently either ignored or misunderstood. If you need to make a detailed, point by point discussion, see below for how to lay this out.
Keep the layout clear: Keep the talk page attractively and clearly laid out. Avoid repetition, muddled writing, and unnecessary digressions. Talk pages with a good signal-to-noise ratio are more likely to attract continued participation.
Keep discussions focussed: Discussions naturally should finalize by agreement, not by exhaustion.
Read the archives: Many article talk pages contain links to archives, which contain earlier discussions. If you are a new editor to an article, be sure to read them, as they often deal with common content disputes and resolutions to them. You may well find your questions and/or objections have already been answered.
Use English: No matter to whom you address a comment, it is preferred that you use English on English Misplaced Pages talk pages. This is so that comments may be comprehensible to the community at large. If the use of another language is unavoidable, try to also provide a translation of the comments. If you are requested to do so and cannot, it is your responsibility to either find a third party to translate or to contact a translator through the Misplaced Pages:Embassy.
How to provide an opinion: Some pages invite you to provide an opinion on a topic. Many people add their opinion as a bullet (*) underneath the relevant topic and bold (''') a brief one- or two-word summary of that opinion. This practice is optional (and somewhat controversial). Your opinion will typically carry more weight depending on the quality of the rationale you provide for making it. Take your time considering a good rationale, based on how the project operates. Make sure to sign your post (~~~~), as described above. Note that polling is not a substitute for discussion.
Centralized discussion: Avoid posting the same thread in multiple forums. This fragments discussion of the idea, creating discussions in separate places with no interchange of ideas. This is rarely desirable, and leads to redundant effort where an idea that has already been adequately addressed has to be considered all over again. Instead, solicit discussion in only one location, either an existing talk page or a new project page, and if needed advertise that in other locations using a link. See also: meatball:ForestFire If you find a fragmented discussion, it may be desirable to move all posts to one of the locations, removing them from the other locations and adding a link.
Be welcoming to newcomers: People new to Misplaced Pages may be unfamiliar with policy and conventions. Please do not bite the newcomers. If someone does something against custom, assume it was an unwitting mistake. Politely and gently point out their mistake, reference the relevant policy/guideline/help pages, and suggest a better approach.
Behavior that is unacceptable
Please note that some of the following are of sufficient importance to be official Misplaced Pages policy. Violations (and especially repeated violations) may lead to the offender being blocked or banned from editing Misplaced Pages.
No personal attacks: A personal attack is saying something negative about another person. This mainly means:
No insults: Do not make ad hominem attacks, such as calling someone an idiot or a fascist. Instead, explain what is wrong with an edit and how to fix it.
Do not threaten people: For example, threatening people with "admins you know" or having them banned for disagreeing with you.
Do not make legal threats: Threatening a lawsuit is highly disruptive to Misplaced Pages, for reasons given at the linked page.
Never post personal details: Users who post what they believe are the personal details of other users without their consent may be blocked for any length of time, including indefinitely.
Do not misrepresent other people: The record should accurately show significant exchanges that took place, and in the right context. This usually means:
Be precise in quoting others.
When describing other people's contributions or edits, use diffs. The advantage of diffs in referring to a comment is that it will always remain the same, even when a talk page gets archived or a comment gets changed.
As a rule, do not edit others' comments, including signatures. Exceptions are described in the next section.
Editing comments
Others' comments
It is not necessary to bring talk pages to publishing standards, so there is no need to correct typing errors, grammar, etc. It tends to irritate the users whose comments you are correcting. Do not strike out the comments of other editors without their permission.
Never edit someone's words to change their meaning, even on your own talk page. Editing others' comments is sometimes allowed, but you should exercise caution in doing so. Some examples of appropriately editing others' comments:
If you have their permission
Removing prohibited material such as libel and personal details
Unsigned comments: You are allowed to append {{unsigned}} or one of its variants to the end of someone's comment if they have failed to sign it. The form is {{subst:unsigned|USER NAME OR IP|DATE AND TIME}}, which results in —The preceding unsigned comment was added by USER NAME OR IP (talk • contribs) DATE AND TIME.
Interruptions: In some cases, it is OK to interrupt a long contribution, either with a short comment (as a reply to a minor point) or with a heading (if the contribution introduces a new topic). In that case, add "<small>Heading added to (reason) by ~~~~</small>"). In such cases, please add {{subst:interrupted|USER NAME OR IP}} before the interruption.
When a long comment has formatting errors, rendering it difficult to read. In this case, restrict the edits to formatting changes only and preserve the content as much as possible. Generally, page formatting can be fixed as well (i.e. to move a new comment from the top of a page to the bottom and adding a header to the comment).
On your own user talk page, you may remove others' comments, although archiving is generally preferred.
In the past it was standard practice to refactor talk pages, although this practice has fallen somewhat into disuse.
If a thread has veered off its original subject, it may be desirable to split threads, especially if the new topic is deemed to merit extensive discussion. When part of a discussion is made into its own thread, the new thread should include an opening sentence or paragraph explaining the reason for the move and containing a link to the original thread. As well, a note should be placed at the location the discussion was moved from, with a link to the new thread. It is also important that the format of the existing discussion remains essentially the same. Simple cutting and pasting will not always ensure that this happens; a bit of reformatting may be necessary. When splitting a thread, always preview how your changes appear and check to see whether the flow of the thread remains the same as it was previously (i.e. that all replies are in the correct places.) Splitting a thread should not in any way alter the meaning of any comments therein; hence the need for links, proper formatting, and an explanation.
Section headers: Because threads are shared by multiple users, the original title becomes communal property. To avoid disputes it is best to discuss changes with the editor who started the thread, if possible, but it is generally acceptable to change section headers when a better header is appropriate. This is under the purview of threads themselves being shared property rather than a single editor's comments.
Disambiguating or fixing links (if the linked-to page has moved, or a talk page section has been archived, or the link is simply broken by a typographical error, for instance).
Hiding or resizing images: You may re-seize over-large images; or hide an image (e.g. change ] to ] by adding a colon) once discussion of it has ended.
De-linking categories: you may make category links in active (e.g. change ] to ] by adding a colon) to prevent the page from being added to a discussed category.
Code samples: You may redact (replace with a note, or collapse) large code samples once discussion of the sample has ended; for instance fulfilled {{editprotected}} requests.
It is best to avoid changing your own comments. Other users may have already quoted you with a diff (see above) or have otherwise responded to your statement. Therefore, use "Show preview" and think about how your amended statement may look to others before you save it.
Altering a comment after it has been replied to robs the reply of its original context. It can also be confusing. Before you change, consider taking one of the following steps:
Contact the person(s) who replied (through their talk page) and ask if it is okay to delete or change your text.
use strike-through or a place-holder to show the comment has been altered.
Strike-through is typed <s>like this</s> and ends up like this.
A placeholder is a phrase such as "". This will ensure that your fellow editors' irritated responses still make sense. In turn, they may then wish to replace their reply with something like, ""
Please do not apply strike-through to other editors' comments without permission.
Creating a communal property section
Occasionally it may be helpful to make a talk page section into communal property, so that other users have the prerogative to edit it just for the purpose of improving it. Examples of this include lists of potential sources or subtopics for the article, or just a proposed addition to the article (if the article is locked, for instance.) A talk page section becomes communal property if it is signed with five tildes (~~~~~) instead of four, as your username is then hidden. But do not include in this comments which others have already made without receiving their permission.
Start new topics at the bottom of the page: If you put a post at the top of the page, it is confusing and can easily be overlooked. The latest topic should be the one at the bottom of the page. Then the next post will go underneath yours and so on. This makes it easy to see the chronological order of posts. A quick way to do this is to use the + tab next to the edit button on the talk page you are on.
Separate multiple points with whitespace: If a single post has several points, it makes it clearer to separate them with a paragraph break (i.e. a blank line). Whitespace is not necessary if your post is indented with colons, simply starting another line with the same indentation level will have an appropriate gap in the output. Whitespace is also not necessary between any lines within an indented or bulleted list, and actually increases the complexity of the generated HTML code, which can have accessibility implications.
Thread your post: Use indentation as shown in WP:TP (or, more specifically, Misplaced Pages:Indentation) to clearly indicate who you are replying to, as with usual threaded discussions. Normally colons are used, not bullet points (although the latter are commonly used at AfD, CfD, etc.).
Start new topics at the bottom of the page: If you put a post at the top of the page, it is confusing and can also get easily overlooked. The latest topic should be the one at the bottom of the page.
Make a new heading for a new topic: It will then be clearly separated into its own section and will also appear in the TOC (table of contents) at the top of the page. A heading is easy to create with == either side of the words, as in == Heading ==. The "Post a comment" feature can be used to do this automatically. (If you are using the default Misplaced Pages:Skin, you can use the "+" tab next to the "Edit this page" tab instead.) Enter a subject/heading in the resulting edit page, and it will automatically become the section heading.
Keep headings on topics related to the article. It should be clear from the heading which aspect of the article you wish to discuss. Do not write "This article is wrong" but address the specific issue you want to discuss.
Keep headings neutral: A heading should indicate what the topic is, but not communicate a specific view about it.
Do not praise in headings: You may wish to commend a particular edit, but this could be seen in a different light by someone who disagrees with the edit.
Do not be critical in headings: This includes being critical about details of the article. Those details were written by individual editors, who may experience the heading as an attack on them.
Never address other users in a heading: A heading should invite all editors to respond to the subject addressed. Headings may be about a user's edits but not specifically to a user.
Never use headings to attack other users: While NPA and AGF apply everywhere at Misplaced Pages, using headings to attack other users by naming them in the heading is especially egregious, since it places their name prominently in the Table of Contents, and can thus enter that heading in the edit summary of the page's edit history. Since edit summaries and edit histories aren't normally subject to revision, that wording can then haunt them and damage their credibility for an indefinite time period, even though edit histories are excluded from search engines. Reporting on another user's edits from a neutral point of view is an exception, especially reporting 3RR violations or other incidents to administrators.
Create subsections if helpful. Talk page discussions should be concise, but if a single discussion becomes particularly long, it may be helpful to add a subsection (such as ===Arbitrary break===) for ease of editing. This is preferable to using templates like {{hide}} and may facilitate the involvement of editors with slower computers and Internet connections.
Links, time and page name
Make links freely: Links to articles are as useful on talk pages as anywhere else, and links to non-existent articles can help get them onto the most wanted articles list.
Use UTC when referring to a time, e.g. the time of an edit or page move.
When mentioning the name of the page, cite the current name: This applies when a page is moved (i.e. retitled). In such a case, the Talk page is usually also moved. If you continue to use the old name, it will be confusing, especially for new editors to the article.
When pages get too long
Archive—do not delete: When a talk page has become too large or a particular subject is no longer being discussed, do not delete the content—archive it. See Help:Archiving a talk page for details on why and how to.
Users may freely remove comments from their own talk pages, though archiving is preferred. They may also remove some content in archiving. The removal of a warning is taken as evidence that the warning has been read by the user. This specifically includes both registered and anonymous users.
Notes
URLs of edit histories and revision differences begin with http://en.wikipedia.org/w/, and Misplaced Pages's robots.txt file disallows /w/.
