Jump to content

Wikipedia:WikiProject Council/Guide/Merging WikiProjects

From Wikipedia, the free encyclopedia

The English Wikipedia has a couple thousand WikiProjects, many of which are inactive, defunct, test pages, or too small to be viable. This page outlines a simple process for merging WikiProjects.

Establish consensus for a merger[edit]

  • Post notices on the talk pages of the parent project and the project you are proposing to convert. Please don't surprise another group of editors by moving their pages without any notice. Keep the discussion in one of the two talk pages, with one of the notices being a link to the discussion on the other. Allow ample time for participants in a less-active group to object.

Things to consider are:

  • Is the project being still active?
  • How many participants are there?
  • What overlap is there in article scope? (This can be determined using the category intersection tool)

Generally speaking, if the merge seems appropriate, then you can proceed if either of the following is true:

  • There is active agreement from the affected groups.
  • There has been no response from the affected group(s), and it has been more than a month since you proposed the merge.

For example, if you want to merge WikiProject Tulips and WikiProject Lilies into WikiProject Plants, then you can proceed if:

  • Everyone agrees, or
  • Nobody objects after a month.

If one group supports (or doesn't object) to the merger but another does not, then proceed only with those groups that have not objected. If the 'target' (the intended bigger group) objects, then the proposed merge cannot happen.

Find and redirect all the project pages[edit]

If you want to preserve separate pages, then see Wikipedia:WikiProject Council/Guide/Task forces#Converting existing projects to task forces.

  1. Redirect the project page (e.g., Wikipedia:WikiProject Tulips) to the larger group (e.g., Wikipedia:WikiProject Plants).
  2. Archive everything on the smaller group's talk page (e.g., Wikipedia talk:WikiProject Tulips).
  3. Redirect the now-empty talk page (e.g., Wikipedia talk:WikiProject Tulips) to the larger group (e.g., Wikipedia talk:WikiProject Plants).
  4. Wikipedia:Move talk page archives.
  5. Check for subpages and archive/move/redirect them as needed. Use Special:PrefixIndex to check for pages. Use Special:WhatLinksHere on each subpage to find any links that need to be updated. Most subpages can simply be redirected (e.g., WikiProject Tulips/Assessment can be redirected to Wikipedia:WikiProject Plants/Assessment). Some, such as lists of participants, may need to be merged.

[edit]

This section still needs work
The following discussion has been closed. Please do not modify it.
  1. Modify the parent project's banner to include task force parameters to match project being converted. Template:WPBannerMeta has examples on how to specify this for projects which use the meta banner. If your project doesn't use WPBannerMeta, it may help to review Advanced project banners; this doesn't cover that topic, but does cover a number of others.
    1. Redirect the moved project's banner to the parent project's banner or make it a wrapper template for the parent project's banner with appropriate pre-filled parameters
    2. Replace usage of the moved project's banner with the parent/task force banner. The moved project's previous banner template should not be used on any article talk pages once the banners have been swapped out.
      • Talk pages with both the converted project's banner and parent project's banner need to have the moved project's banner removed, and the task force's parameters added to the parent project's banner.
      • Talk pages with only the converted project's banner need to have it replaced by parent project's banner with the task force parameters.
        These steps can be performed manually, or for larger projects, with the help of a bot. A bot request can be placed (existing bots include User:AnomieBOT and User:PrimeBOT).

Categories[edit]

  1. Find all the categories that the merged-away groups have used. Generally, these are named something like Category:WikiProject Tulips or Category:WikiProject Tulips articles.
  2. Any categories from the converted project which have been renamed and emptied should now be eligible for speedy deletion under either the empty category (C1) criteria for speedy deletion. Edit the category pages and add {{db-catempty}} to the top.
  3. Check the categories on all the pages you moved or redirected, to make sure that they are not using a now-obsolete category (e.g., Category:WikiProject Tulips pages.
    1. Make sure that automated quality assessment statistics are being generated correctly. If |TF_n_ASSESSMENT_CAT = Tulips articles is set for the task force, then categories of the type Category:FA-Class Tulips articles will be generated. Bring all these categories into a parent category Category:Tulips articles by quality, and categorise it under Category:Wikipedia 1.0 assessments. Assessments will be logged at Wikipedia:Version 1.0 Editorial Team/Tulips articles by quality log and overall statistics at User:WP 1.0 bot/Tables/Project/Tulips which is transcluded on Wikipedia:Version 1.0 Editorial Team/Tulips articles by quality statistics. See Wikipedia:Version 1.0 Editorial Team/Using the bot for more information.

Links and directories[edit]

  1. Remove the old Wikipedia:WikiProject Council/Directory entry.
  2. Removed the old Article Alerts entry (if one exists).
  3. Remove the old Hot Articles entry (if one exists).
  4. Remove the old Popular pages config (if one exists).
  5. Update other project templates. Redirect, merge, or update existing userboxes, welcome and invitation message templates, and other project related templates.