উইকিপিডিয়া:আলাপ পাতার নির্দেশাবলী

আলাপ পাতার সাধারণ তথ্যের জন্য উইকিপিডিয়া:আলাপ পাতা দেখুন

উইকিপিডিয়াতে কোনো নিবন্ধ বা প্রকল্পের পাতাতে কোনো প্রকার পরিবর্তনের আলোচনা করার জন্য আলাপ পাতা ব্যবহার করা হয়। কোন নিবন্ধের আলাপ পাতাকে সম্পাদকদের ব্যক্তিগত মতামতের স্থান হিসাবে ব্যবহার করা যাবে না।

একটি টক পাতা লেখার সময়, কিছু পন্থা পাল্টা-উত্পাদনশীল, অন্যরা ভাল সম্পাদনাকে সহজ করে দেয়। কথোপকথনের প্রধান মানগুলি হল যোগাযোগ, সৌজন্যে এবং বিবেচনা। নিম্নোক্ত তালিকাটি উইকিপিডিয়ানদের বক্তৃতাগুলি কার্যকরভাবে ব্যবহার করার জন্য ডিজাইন করা হয়েছে।

কেন্দ্রীয় পয়েন্ট

উইকিপিডিয়া নীতি বজায় রাখুন

নিবন্ধগুলিতে প্রযোজ্য নীতিগুলি উইকিপিডিয়া এর যাচাইকরণ, নিরপেক্ষ দৃষ্টিভঙ্গি এবং কোনও মূল গবেষণা নীতি সহ পৃষ্ঠাগুলিতে কথা বলার ক্ষেত্রে (একই ক্ষেত্রে নাও) প্রয়োগ করে। আরও তদন্ত করার জন্য একটি দৃষ্টিভঙ্গির সাথে, অবশ্যই বক্তৃতা পাতায় বক্তৃতা, প্রস্তাবনা এবং ব্যক্তিগত জ্ঞানের জন্য কিছু যুক্তিসঙ্গত ভাতা রয়েছে, তবে এটি সাধারণত কোনও পন্থা অবলম্বন করার জন্য একটি টক পৃষ্ঠাের অপব্যবহার যা নীতিগত প্রয়োজনীয়তা পূরণ করে না।

উইকিপিডিয়া: জীবিত ব্যক্তির জীবনী বিশেষ মনোযোগ দিন:

সম্পাদকগণ জীবিত ব্যক্তিদের সম্পর্কে যেকোন নেতিবাচক উপায়ে সরিয়ে ফেলতে পারেন যেটি নিঃসন্দেহে অসুরক্ষিত, সেগুলি উৎসের উপর নির্ভর করে যা নির্ভরযোগ্য উত্সগুলিতে নির্দিষ্ট মানগুলি পূরণ করে না বা উত্সের একটি ধারণাগত ব্যাখ্যা।

নিবন্ধ আলোচনা পৃষ্ঠাগুলি কীভাবে ব্যবহার করবেন

• যোগাযোগ: সন্দেহ থাকলে, অতিরিক্ত প্রচেষ্টা যাতে অন্য মানুষ আপনাকে বুঝতে পারে, এবং আপনি অন্যদের সঠিক বুঝতে পারেন। বন্ধুত্বপূর্ণ হচ্ছে একটি মহান সাহায্য। আপনার মতামত ব্যাখ্যা করার জন্য সবসময়ই একটি ভাল ধারণা; কিছু বিষয়ে আপনার মতামত কমাবার জন্য এটি কম সহায়ক এবং কেন তা ব্যাখ্যা করে না। একটি মতামত ব্যাখ্যা করা অন্যদের বিশ্বাসী এবং ঐক্যমতে পৌঁছানোর মধ্যে সাহায্য করে।
• বিষয় রাখুন: নিবন্ধ পৃষ্ঠাটি নিবন্ধের বিষয় নিয়ে আলোচনা করার জন্য নয়, নিবন্ধের বিষয় সম্পর্কে সাধারণ কথোপকথনের জন্য নয় (অনেক কম বিষয়)। কীভাবে সংশ্লিষ্ট নিবন্ধটি উন্নত করতে হবে সে বিষয়ে আলোচনা করুন। অপ্রাসঙ্গিক আলোচনা অপসারণের বিষয়।
• ইতিবাচক হোন: নিবন্ধের আলোচনা পাতায় একটি নিবন্ধ উন্নত করার জন্য আলোচনা করা উচিত; একটি নিবন্ধ বা তার বিষয় বর্তমান অবস্থা সম্পর্কে সমালোচনা করা, পৃথক্ বা বাছাই বা বিনিময় না। এই জীবন্ত মানুষদের জীবনীসমূহের আলাপ পাতায় বিশেষভাবে সত্য। যাইহোক, যদি আপনি কিছু মনে করেন ভুল হয়, কিন্তু এটি কীভাবে ঠিক করতে হয় তা নিশ্চিত না হলে, সব উপায়ে এই দিকে মনোযোগ আকর্ষণ করতে ভুলবেন না এবং অন্যদের কাছ থেকে পরামর্শ চাইতে পারেন।
• অবগত থাকুন: একটি বিতর্কিত বিষয় সম্পর্কে তাদের ব্যক্তিগত দৃষ্টিকোণকে তর্ক করার জন্য সম্পাদকের জন্য আলোচনা পাতারা একটি ফোরাম নয়। তারা আলোচনায় একটি ফোরাম আছে যে কীভাবে সেকেন্ডারি সূত্র থেকে প্রাপ্ত বিভিন্ন পয়েন্টের প্রবন্ধ নিবন্ধে অন্তর্ভুক্ত করা উচিত, যাতে শেষ ফলাফলটি নিরপেক্ষ ও উদ্দেশ্যমূলক (যা বৈপরীত্য দৃষ্টিভঙ্গি সহ হতে পারে)। একটি মামলা উপস্থাপন করার সর্বোত্তম উপায় হল সঠিকভাবে উল্লিখিত সামগ্রী (ব্যক্তিগত মতামতের জন্য একটি বিকল্প ফোরামের জন্য, উইকিবিট এর প্রস্তাব দেখুন)।
• ঘটনা নিয়ে লেনদেন: কথোপকথন যাচাইয়ের সমস্ত বিষয়গুলির জন্য আদর্শ পাতাটি আদর্শ স্থান। এটি উত্স খুঁজে পেতে সাহায্য চাইতে, বিভিন্ন উত্স থেকে বিপরীতমূলক তথ্য তুলনা, এবং রেফারেন্সের নির্ভরযোগ্যতা পরীক্ষা অন্তর্ভুক্ত। একটি বিবৃতি সমর্থন একটি যাচাইযোগ্য রেফারেন্স জন্য জিজ্ঞাসা করা এটি বিরুদ্ধে তর্ক বিতর্ক তুলনায় প্রায়ই ভাল।
• ভাগ উপাদান: আলাপ পাতাকে নিবন্ধ থেকে উপাদান সংরক্ষণ করতে ব্যবহার করা যেতে পারে যা মুছে ফেলা হয়েছে কারণ এটি যাচাই করা হয়নি, তাই পাওয়া যাবে রেফারেন্সের জন্য সময় দেওয়া যেতে পারে। নতুন উপাদানে মাঝে মাঝে আলোচনা পাতায় প্রস্তুত করা যায় যতক্ষন পর্যন্ত তা প্রবন্ধটি লিখতে প্রস্তুত না হয়।
• সম্পাদনাগুলি নিয়ে আলোচনা করুন: কথোপকথ সম্পর্কে কথা বলার জন্য আলাপ পাতাটি বিশেষভাবে দরকারী। আপনার সম্পাদনাগুলির একটি যদি প্রত্যাবর্তন করা হয়েছে, এবং আপনি এটি আবার এটিকে পরিবর্তন করে ফেলেন, তবে আলোচনা পাতায় একটি ব্যাখ্যা ত্যাগ করতে এবং আপনার সম্পাদনার সারাংশে একটি নোট রাখা ভাল। আলাপ পাতায় আরেকটি সম্পাদকের পরিবর্তন সম্পর্কে জিজ্ঞাসা করার জায়গাও রয়েছে। যদি কেউ আপনার সম্পাদনাগুলির একটি জিজ্ঞাসা করে, আপনি একটি পূর্ণ, সহায়ক যুক্তি সঙ্গে উত্তর নিশ্চিত করুন।
• প্রস্তাবগুলি তৈরি করুন: আপনি যদি চান তবে অন্যান্য সম্পাদকদের দ্বারা নিবন্ধের নতুন প্রস্তাবগুলি এগিয়ে নিয়ে যেতে পারে। প্রস্তাবগুলিতে নির্দিষ্ট বিশদ পরিবর্তন, পৃষ্ঠা চালানো, একজায়গায় একটি পৃথক নিবন্ধে একটি দীর্ঘ নিবন্ধের একটি বিভাগ তৈরির অন্তর্ভুক্ত হতে পারে।

ভাল অনুশীলন

• আপনার পোস্টগুলি সাইন করুন: একটি পোস্ট সাইন ইন করার জন্য, চারটি টিল্ড (~~~~) টাইপ করুন এবং তাদের আপনার ব্যবহারকারী নাম এবং টাইম স্ট্যাম্প দিয়ে প্রতিস্থাপিত হবে, যেমন: উদাহরণ 13:21, 9 মে 2008 (UTC)। দয়া করে মনে রাখবেন এটি একটি বেনামী মন্তব্য ছেড়ে অসম্ভব কারণ আপনার ব্যবহারকারী নাম বা IP ঠিকানা পৃষ্ঠা ইতিহাসে রেকর্ড করা আছে।
• Avoid excessive emphasis: CAPITAL LETTERS are considered shouting and are virtually never appropriate. Bolding may be used to highlight key words or phrases (most usually to highlight "oppose" or "support" summaries of an editor's view), but should be used judiciously, as it may appear the equivalent of the writer raising his voice. Italics may be used more frequently for emphasis or clarity on key words or phrases, but should be avoided for long passages. Remember that overuse of emphasis can undermine its impact. If adding emphasis to quoted text, be sure to say so. Italics can also be used to distinguish quoted text from new text and, of course, book titles, ship names, 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, using standard indentation and formatting conventions. Avoid repetition, muddled writing, and unnecessary digressions. Talk pages with a good signal-to-noise ratio are more likely to attract continued participation. See Talk page layout.

• Keep discussions focused: Discussions naturally should finalize by agreement, not by exhaustion.
• Read the archives: If you are a new editor to an article, be sure to read the archives. Not only are content disputes valuable examples of talk page behavior, but they contain a lot of expert knowledge surrounding the topic. You may quickly find your questions and/or objections have already been answered if you try searching all the archives for that article at once using the prefix parameter.
• Use English: No matter to whom you address a comment, it is preferred that you use English on English Wikipedia 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, you should either find a third party to translate or to contact a translator through the Wikipedia:Embassy.

• Avoid posting the same thread in multiple forums. This fragments discussion of the idea. Instead, start the discussion in one location, and, if needed, advertise that in other locations using a link. (See meatball:ForestFire.) If you find a fragmented discussion, it may be desirable to move all posts to one location, and linking to it. Make sure you state clearly in edit summaries and on talk pages what you have done and why.
• Be welcoming to newcomers: People new to Wikipedia 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.
• Comment on content, not on the contributor: Keep the discussions focused upon the topic of the talk page, rather than on the personalities of the editors contributing to the talk page.
• Use minor for minor changes only: The minor flag in your edits should be used as it is with article pages and should only be used for superficial differences between the current and previous versions such as typographical corrections, formatting and presentational changes or rearrangement of text without modification of content. Adding new text to the talk pages should not be marked as minor.

Behavior that is unacceptable

Please note that some of the following are of sufficient importance to be official Wikipedia policy. Violations (and especially repeated violations) may lead to the offender being blocked or banned from editing Wikipedia.

• 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. Explaining to an editor the consequences of violating Wikipedia policies, like being blocked for vandalism, is permitted however.
  • Do not make legal threats: Threatening a lawsuit is highly disruptive to Wikipedia, 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.
  • DO NOT ask for another's personal details.
• Do not impersonate other editors
• Do not claim to be an administrator or claim to have an access level that you do not have, as this can be highly disruptive and may cause other editors trouble in the cleanup process. User access levels can be checked at Special:ListUsers by anyone.
• Do not use the talk page as a forum or soapbox for discussing the topic. The talk page is for discussing improving the article.

Editing comments

Others' comments

It is not necessary to bring talk pages to publishing standards, so there is no need to correct typing/spelling errors, grammar, etc. It tends to irritate the users whose comments you are correcting. The basic rule – with some specific exceptions outlined below – is, that you should not strike out or delete the comments of other editors without their permission.

Never edit someone's comment to change its meaning, even on your own talk page. Do not edit apparent mistaken homophone contractions in comments of others. One may only ask the poster what they meant to say.

Editing – or even removing – 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, personal details, or copyright violations.
• Removing harmful posts, including personal attacks, trolling and vandalism. This generally does not extend to messages that are merely incivil; deletions of simple invective are controversial. Posts that may be considered disruptive in various ways are another borderline case and are usually best left as-is or archived.
• Refactoring for relevance: Archiving material not relevant to improving the article (per the above subsection #How to use article talk pages). Formerly it was not uncommon to simply delete off-topic posts, but this has led to disputes from time to time, and it is generally better to move such threads to an archive page. It is still common, and uncontroversial, to simply delete gibberish, rants about the article subject (as opposed to its treatment in the article) and test edits, as well as harmful or prohibited material as described above. Another form of refactoring is to move a thread of entirely personal commentary between two editors to the talk page of the editor who started the off-topic discussion.
• Attributing unsigned comments: You are allowed to append attribution (which can be retrieved from the page history) to the end of someone's comment if they have failed to sign it. This typically takes the form — {{User|USERNAME}} TIMESTAMP OF EDIT (UTC). The template {{unsigned}} or one of its variants can be used to do this more explicitly: {{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.
• Signature cleanup: If a signature violates the guidelines for signatures, or is an attempt to fake a signature, you may edit the signature to the standard form with correct information (— {{User|USERNAME}} TIMESTAMP OF EDIT (UTC)) or some even simpler variant. Do not modify others' signatures for any other reason. If the user's signature has a coding error in it, you will need to contact the editor to fix this in their preferences.
• Interruptions: In some cases, it is okay 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 or subtopic; in that case, one might add :<small>Heading added for REASON by ~~~~</small> below the heading to make the nature of the change clearer). When introducing an interruptive break, please add {{subst:interrupted|USER NAME OR IP}} before the interruption. One may also manually ensure that attribution is preserved by copy-pasting the original signature to just before the interruption.
• Fixing format errors that render material difficult to read. In this case, restrict the edits to formatting changes only and preserve the content as much as possible. Examples include fixing indentation levels, removing bullets from discussions that are not consensus polls or RfCs, using <nowiki> and other technical markup to fix code samples, and providing wikilinks if it helps in better navigation.
• Fixing layout errors: This could include moving a new comment from the top of a page to the bottom, adding a header to a comment not having one, repairing accidental damage by one party to another's comments, correcting unclosed markup tags that mess up the entire page's formatting, accurately replacing HTML table code with a wikitable, etc.
• Sectioning: If a thread has developed new subjects, it may be desirable to split it into separate discussions with their own headings or subheadings. When a topic is split into two topics, rather than subsectioned, it is often useful for there to be a link from the new topic to the original and vice versa. A common way of doing this is noting the change at the [then-]end of the original thread, and adding an unobtrusive note under the new heading, e.g. :<small>This topic was split off from [[#FOOBAR]], above.. Some reformatting may be necessary to maintain the sense of the discussion to date and to preserve attribution. It is essential that splitting does not inadvertently alter the meaning of any comments.
• Section headings: Because threads are shared by multiple editors (regardless how many have posted so far), no one, including the original poster, "owns" a talk page discussion or its heading. It is generally acceptable to change headings when a better header is appropriate, e.g. one more descriptive of the content of the discussion or the issue discussed, less one-sided, more appropriate for accessibility reasons, etc. To avoid disputes it is best to discuss a heading change with the editor who started the thread, if possible, when a change is likely to be controversial. It can also sometimes be appropriate to merge entire sections under one heading (often preserving the later one as a subheading) if their discussions are redundant.
• Disambiguating or fixing links, if the linked-to page has moved, a talk page section has been archived, the link is simply broken by a typographical error, etc. Do not change links in others' posts to go to entirely different pages. If in doubt, ask the editor in question to update their own post, or add a follow-up comment of your own suggesting the alternative link. Only fix a link to a template that has been replaced or deprecated if the effect of the new template is essentially the same as what the poster used (otherwise, simply allow the post to redlink to the old template, as a broken post is preferable to one with altered meaning).
• Hiding or resizing images: You may hide an image (e.g. change [[File:foo.jpg|<var>...details...</var>]] to [[:File:foo.jpg|<var>...details...</var>]] by adding a colon) once discussion of it has ended. This is especially appropriate for "warning" and "alert" icons included in bot-posted notices which are usually quickly resolved. Another common image-related edit is re-sizing images that were posted in full size and take up too much room on the talk page.
• De-linking categories: you may make category links inactive (e.g. change [[Category: foobar]] to [[:Category: foobar]] by adding a colon) to prevent the page from being added to a discussed category.
• Hiding old 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.
• Personal talk page cleanup: On your own user talk page, you may archive threads at your discretion. Simply deleting others' comments on your talk page is not forbidden by policy, but is discouraged. It is also rather pointless. Many new users believe they can hide critical comments by deleting them. This is not true. Such comments can always be retrieved from the page history.

In the past, it was standard practice to "summarize" talk page comments, but this practice has fallen into disuse. Refactoring and archiving are still appropriate.

Own comments

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.

Substantially altering a comment after it has been replied to may deny the reply of its original context. It can also be confusing. Before you change your own comment, 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 deletion and insertion markup or a place-holder to show the comment has been altered.
  • Deletion (which in most browsers is rendered as struck-through text, is coded <del>like this</del> and ends up like this.
  • An insertion, which in most browsers is rendered as underlined text, is coded <ins>like that</ins> and ends up like that.
  • A placeholder is a phrase such as "[Thoughtless and stupid comment removed by the author.]". 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, "[Irritated response to deleted comment removed. Apology accepted.]"
  • Please do not apply any such changes to other editors' comments without permission.
• When modifying a comment, you can add a parenthetical note pointing out the change. You can also add an additional timestamp by typing ~~~~~ (five tildes).

Disputes

If you have a disagreement or a problem with someone's behavior, please read Wikipedia:Dispute resolution.

Technical and format standards

Layout

আরও দেখুন: Wikipedia:Talk page layout

• 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 "new section" 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 Wikipedia:Talk page#Indentation (or, more specifically, Wikipedia: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.).

New topics and headings on talk pages

See also Wikipedia:Manual of Style

• 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 == on 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 Wikipedia: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 Wikipedia, 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 edit warring 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 Coordinated Universal Time, 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 to condense pages

Large talk pages become difficult to read and strain the limits of older browsers. It is helpful to archive or refactor a page either when it exceeds 50 KB, or has more than 10 main topics.

• Archive—do not delete: When a talk page has become too large or a particular subject is not discussed any more, do not delete the content—archive it. See Help:Archiving a talk page for details on why and how to.
• Summarize ("refactor"): See Wikipedia:Refactoring talk pages for details on why and how to refactor talk pages.

ব্যবহারকারীর আলাপ পাতা

আরও দেখুন: WP:User page

While the purpose of article talk pages is to discuss the content of articles, the purpose of user talk pages is to draw the attention or discuss the edits of a user. Wikipedia is not a social networking site, and all discussion should ultimately be directed solely toward the improvement of the site.

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.

আরও দেখুন

• উইকিপিডিয়া:শিষ্টাচার
• উইকিপিডিয়া:ব্যবহারকারীর পাতা
• উইকিপিডিয়া কোনো ব্লগ নয়