This is a WikiProject, a collaboration area and open group of editors dedicated to organizing an internal process on Wiki English. New participants are welcome; please feel free to participate! |
August 2023 | 8 |
September 2023 | 48 |
October 2023 | 129 |
November 2023 | 183 |
December 2023 | 254 |
January 2024 | 335 |
February 2024 | 250 |
March 2024 | 400 |
April 2024 | 400 |
Undated articles | 1 |
Articles to be merged after an Articles for deletion discussion | |
---|---|
All articles | 229 |
Several Wikipedians have formed this collaboration resource and group dedicated to improving the merging process. This page and its subpages contain their suggestions and various resources; it is hoped that this project will help to focus the efforts of other Wikipedians interested in the merge process. If you would like to help, please join the project, inquire on the talk page and see the to-do list below.
The main project focus at this time is reducing the articles to be merged backlog!
To-do list for WikiProject Merge:
|
A merge is a process by which the content of two pages are united on one page for one or more of the following reasons:
A copy paste merge creates "attribution dependency". To license the content from the originating article you must, at minimum, provide a direct link to the original article in the edit summary of the page where content is being placed. You should also place the {{Copied}} tag on the originating article as well as the target article.
Merging should be avoided if the articles are sufficiently distinct to stand on their own and the resulting article will be too long or "clunky"; the separate topics could be expanded into longer standalone (but cross-linked) articles; the topics are discrete subjects and deserve their own articles even though they may be short.
If you need direction for making a new merge proposal see Wiki: Proposed mergers. On Wikipedia, articles may be boldly merged without any proposal taking place, though it is recommended where the merge is expected to be controversial. If you boldly merge an article and it is reverted, this should be considered part of the BOLD, revert, discuss cycle and not undone until discussion takes place—do not edit war.
A merge is listed once a tag is placed on the article, such as {{Merge}} or {{Merge to}}. Removing the tag delists the article. Never remove a proposed merge tag unless you are intending to delist the article and only do so when all issues have been addressed. If the proposer of the merge did not start a discussion for the merge, and it is not obvious why the articles should be merged, it is acceptable to remove the tags. If the reason for the merge is obvious, you can either merge the articles boldly, or start a new discussion.
Editors should always close a proposal uncontroversially. Complex cases can be referred to the project's talk page. Merging an article where there was a consensus-based decision to do so at an AfD discussion that has been closed by an administrator is not controversial, and may be undertaken with no further discussion or closing procedure.
If there has been no discussion generated after a reasonable amount of time then the merge proposal is stale. If there are no active AfD, ANI, or other dispute resolution discussions involving any of the affected pages (see below), stale merge proposals with no discussion after six months should be immediately delisted if any of the following apply:
If the articles listed for merge meet the above standards then you may simply remove the tags as a stale merge/old proposal with no consensus. No merging takes place. Otherwise, you may participate in the discussion if you have an opinion on the merits of the proposed merge, or consider closing the discussion according to merge discussion closing procedures.
To carry out the merge, be sure and follow the steps as laid out by Wiki: Merging#How to merge.
Editors should not merge content during an AFD. AfD participants should not work "around" consensus by beginning a merge process on their own, before discussion. While preservation of content is a good consideration, copying may be contentious and may create additional steps and administrative work if undoing any copying is necessary. Such a merge also causes an attribution dependency breakage between articles that may require the merging of article history that would be lost if the source page is deleted. AFD participants may offer proposals and negotiate with the other participants during the discussion. If needed, editors may ask the closing admin how to rescue the content or what additional steps that need to be taken.
Any editor may add contents and references if the prose used is completely original. In this manner the merged content is not merely copied and pasted but all original content makes use of the available references (see Wiki: EDITATAFD). Rather than merging, the content can be rewritten. In this case, there is no attribution problems as the content is new. However, one should exercise extreme caution BEFORE undertaking such a controversial merge. While it is not strictly prohibited, Wikipedia:WikiProject Merge recommends that all editors refrain from such tasks in the spirit of collaboration. Unless there is a strong case for the merge specified by deletion policy it is preferred that editors wait until the discussion period is complete.
Once the content is merged do not forget to blank the originating page and add:
#REDIRECT [[PAGENAME]] {{R from merge}}
At minimum, attribution must be provided in the edit summary of the page into which content is placed. This step is required in order to conform with Wiki's licensing requirements. Do not omit it nor omit the page name. It is important to remember, once a merge has been made and the redirect set or even when a redirect is not set in place, to add this template on both the target and originating article talkpage and fill out completely:
{{Copied |from= |from_oldid= |to= |diff= }}
See the Template:Copied documentation for instructions.
Please feel free to add yourself here, and indicate any areas of particular interest.Please post new entries at the end of the list.
To display all subcategories click on the "►": |
---|
To display all subcategories click on the "►": |
---|
WikiProject Merge pages (47 P) |
The following tags should be placed on top the pages or sections which require merging.
|
{{User WikiProject Merge}}
produces: This user is a participant in WikiProject Merge. |
{{User merge}}
produces: {{User mergist}}
produces: This user is a member of the Association of Mergist Wikipedians. |
The following template can be placed along with other project banners. Rate the article for class and importance to project. This template also has the additional attribution template added to be used on each page after merge.
{{WikiProject Merge Copied}}
Merge | ||||
|
which contains contents copied from:
{{Copied}}
This template goes on the merge article talk page and target article project listings
{{Merge done}}
Merger complete.
If a nomination for deletion results in a merge with delete, add:
{{afd-merged-from}}
For a list of all merge templates, go to Category:Merge templates or Wiki: Template messages/Merging.
This barnstar could be given to a prolific merger or a user who has contributed significantly to the project. It is the official barnstar for this project.
{{subst:WikiProject Merge Barnstar|Message}}
produces:
The Merging Barnstar | ||
Message Here |
This article uses material from the Wikipedia English article Wiki:WikiProject Merge, which is released under the Creative Commons Attribution-ShareAlike 3.0 license ("CC BY-SA 3.0"); additional terms may apply (view authors). Content is available under CC BY-SA 4.0 unless otherwise noted. Images, videos and audio are available under their respective licenses.
®Wikipedia is a registered trademark of the Wiki Foundation, Inc. Wiki English (DUHOCTRUNGQUOC.VN) is an independent company and has no affiliation with Wiki Foundation.