Wiki Cleanup

This describes plans for improving the Mercurial wiki.

1. Goal

The wiki aims to be a moderately coherent body of useful documentation to supplement the following resources:

• Mercurial's built-in documentation and man pages

• The Mercurial book

• Mercurial's mailing lists

As such, it makes sense to have things like the following:

• in-depth information and How-tos that are beyond the scope of the book

• information about extensions and third-party tools
• links to other resources
• FAQs, tips, and other useful recipes
• best practices
• migration and conversion assistance
• documentation of internals
• development plans and other information for contributors

Things that probably don't make sense for the wiki include:

• duplication of book and help content
• discussion - use the mailing lists
• non-best practices
• advertising

2. Improvement plan

As of October 2010, much of the wiki suffers from:

• inconsistent formatting and style
• poor linking and organization
• excessive duplication
• pages that duplicate help or book content
• lots of stub pages
• random commentary and non-canonical advice
• irrelevant pages courtesy of Moin distribution

This page describes a collection of janitorial tasks for incrementally improving this situation over time. Regular wiki users and editors should consider some of these tasks as they visit the wiki.

At some point, as the style and structure plans for the wiki become more firm, we may add all pages to CategoryAudit so that we can mark and sweep everything into the desired structure.

If you have questions or suggestions, please ask on IRC.

3. Tasks

3.1. Spam removal

Watch the RecentChanges page for the introduction of spam pages and other vandalism. Revert vandalized pages and delete newly-created spam pages and add offending users to BannedUsers (or ask an admin).

3.2. Update pages and page names to match wiki style

Consult RecentChanges and PageHits for popular pages to normalize.

See the wiki style guide for guidelines on page style and edit pages appropriately. Add pages that need further editing to CategoryAudit.

Add redirects to renamed pages to avoid breaking existing links.

3.3. Remove discussion

Some pages have discussion questions that belong elsewhere. Either move these to a '/Talk' subpage or delete them.

3.4. Fix orphaned and abandoned pages

Visit OrphanedPages and AbandonedPages to find pages that need attention and add appropriate categories and links from other pages.

3.5. Mark pages needing merging

There are a number of pages that contain very similar content on the wiki. Use the search tool to find related pages and add them to CategoryProposedMerge. Include a marker like the following under the title of each page to be merged:

This page's contents should be merged with PageFoo and PageBar.

{i} This page's contents should be merged with PageFoo and PageBar

If you undertake the consolidating of page contents, remember to redirect the old pages to the new one.

3.6. Link to built-in help and book topics

There are a lot of topics on the wiki that are now covered in help, manpages, and the book. Add links to such content where appropriate. To link to built-in help topics (for instance the hg branch command), use a link like the following:

[[http://selenic.com/hg/help/branch|hg branch]]

For pages whose contents are completely covered by these resources, see the section below on page deletion.

3.7. Page deletion

Add pages that don't seem appropriate for the wiki (irrelevant stubs, random commentary, etc.) to CategoryProposedDeletion and include a marker like the following under the title:

This page is proposed for deletion.

/!\ This page is proposed for deletion.

Use the 'Local Site Map' action to find pages that link to a page and remove those links.

3.8. Fix broken links

Visit WantedPages and point broken links to appropriate pages or remove them as appropriate.

3.9. Expand stubs and create needed pages

Visit CategoryStubs and WantedPages and expand wiki content.

CategoryWiki