Extension merger

An extension merger is a non-automated process by which the functions of two extensions is united into one extensions. Reasons to merge an extension include unnecessary duplication of purpose or significant overlap with the uses of another extension. Merging results in a redirect of the extension's page and possibly subversion commits to the final extension. A comment in the edit summary must be made in the pages of the extensions being merged as to where they are being merged to, and it must be noted in the final extension's page edit summary where the pages of the original extensions were; this is done to preserve attribution under the Creative Commons Share-alike 3.0 license.

Rationale
There are two primary reasons to merge extensions:
 * 1) Duplicate – There are two or more pages on exactly the same purpose.
 * 2) Overlap – There are two or more extensions with significant overlap in their uses. Such as two extensions doing similar tasks on the same external web site.

Advantages:
 * Less confusion for MediaWiki wiki administrators and developers
 * More efficient use of volunteer and staff resources
 * Streamline extension usage by wikis
 * Making for easier management of MediaWiki wikis
 * Address complaints of needing several extensions to accomplish "basic" features missing from others

Merging should be avoided if
 * The resulting extension is too broad in scope and purpose to efficiently maintain

Proposing a merger
Users may request that extensions be merged. In most circumstances, a discussion should be started to attract sufficient input. This will usually occur on the proposed destination extension's discussion page. This should include proposal itself (the intent), the list of the affected extensions, and a merger rationale.

Perform the following steps:

Extensions to merge

 * Current extensions tagged for merging can be found at Category:Extensions to be merged