This page describes two new features approved for trial, based on the concept of flagged revisions. The first feature is flagged protection, since renamed to pending changes, which uses flagging as an optional alternative to semi protection and full protection. When a page is protected in this way by an administrator, the latest flagged revision is shown to readers by default. The second feature is patrolled revisions, which uses flagging passively to coordinate the monitoring of articles, but has no effect on the version viewed by readers.

The "Flagged Revisions" feature was initially developed for the German Wikipedia (de.wikipedia.org) so that wikis could review contributions by users before allowing their publication. In 2007 and 2008, flagged revisions have been proposed to better handle several issues faced by the English Wikipedia (en.wikipedia.org), such as vandalism and violations of our policy on living people. Aggressive use of the feature was rejected by the English Wikipedia community, essentially for too drastically reducing the ability of anyone to edit Wikipedia. In late 2008 and beginning 2009, more specific implementations were discussed in order to reach a compromise, and finally the joint proposal for flagged protection and patrolled revisions reached consensus for a trial on the English Wikipedia.

Those features are principally aimed to address the lack of flexibility of our current protection mechanisms and the relative inefficiency of our basic monitoring tools such as recent changes and watchlists. Flagged protection allows more granularity than the classic page protection system: while the latter prevents any editing, flagged protection allows editing but requires review before changes by new or unregistered users are displayed on the version viewed by readers. Like classic page protection, it can be enabled only by administrators, for a fixed period of time or indefinitely. Patrolled revisions provide a way to review edits similar to Flagged Revisions but without affecting the version viewed by readers, thus it is a passive way to monitor articles much more efficient than recent changes and watchlists which tend to become ineffectual with the huge volume of editing and articles on the English Wikipedia. While recent changes and watchlists display bare edits with no possibility of organization of the reviewing at the individual or community level, patrolled revisions allow users to review changes made to an article since the latest patrolled revision, and patrol new revisions when appropriate; and thus allow to coordinate and optimize the reviewing efforts.

This feature was formerly known as "Flagged protection"

Pending changes introduces new protection levels which can be used as an alternative to regular semi-protection and full-protection. In terms of policy, the conditions for using pending changes protection at level 1 are the same as for using semi-protection, as determined by the protection policy, and the condition for using level 2 are the same as for using full-protection. Disputes should still be handled by full protection^[1]. Classic protection can and should still be used, for example in cases of exceptionally high levels of vandalism, where using flagged protection would be counter-productive. The full spectrum of protection levels are shown in the following table:

Interaction of Wikipedia user groups and page protection levels

	Unregistered or newly registered	Confirmed or autoconfirmed	Extended confirmed	Template editor  ★	Admin	Interface admin	Appropriate for (See also: Wikipedia:Protection policy)
No protection	Normal editing						The vast majority of pages. This is the default protection level.
Pending changes	All users can edit Edits by unregistered or newly registered editors (and any subsequent edits by anyone) are hidden from readers who are not logged in until reviewed by a pending changes reviewer or administrator. Logged-in editors see all edits, whether accepted or not.						Infrequently edited pages with high levels of vandalism, BLP violations, edit-warring, or other disruption from unregistered and new users.
Semi	Cannot edit	Normal editing					Pages that have been persistently vandalized by anonymous and registered users. Some highly visible templates and modules.
Extended confirmed	Cannot edit		Normal editing				Specific topic areas authorized by ArbCom, pages where semi-protection has failed, or high-risk templates where template protection would be too restrictive.
Template	Cannot edit			Normal editing			High-risk or very-frequently used templates and modules. Some high-risk pages outside of template space.
Full	Cannot edit				Normal editing		Pages with persistent disruption from extended confirmed accounts.
Interface	Cannot edit					Normal editing	Scripts, stylesheets, and similar objects central to operation of the site or that are in other editors' user spaces.
★  The table assumes a template editor also has extended confirmed privileges, which is almost always the case in practice.
Other modes of protection: Create protection Move protection Upload protection Office protection Cascade protection

Advantages over the current system

• Even though their edits are not visible immediately to readers, unregistered and new users can edit pages protected by pending changes, while they cannot edit semi-protected pages. So this allows constructive changes while disallowing vandalism and other unconstructive changes.
• Semi-protection is insufficient in certain cases, especially for articles targeted by persistent vandals or sockpuppets, or subject to extreme BLP violations; these sometimes require full protection. The option to deactivate auto-reviewing for autoconfirmed users who are not reviewers (autoconfirmation) provides a protection level adapted to handle those cases.

The aim of patrolled revisions is to coordinate and improve the monitoring of all articles, especially biographies of living people. Reviewers can mark a revision patrolled, which has no effect but only to inform that this revision contains no vandalism, no blp violations, and satisfies certain other requirements defined by a guideline. In particular, this does not affect the revision viewed by unregistered users by default, it's still the latest one (unless the article is flag protected). A new revision by a reviewer is automatically patrolled when the previous version is.

Reviewers have access to a special page listing articles that have never been patrolled and a special page listing pages patrolled at least once with an unpatrolled latest revision. They allow respectively to detect never patrolled pages, that may not have been checked for vandalism, blp violations, etc, and monitor changes to patrolled pages, on which vandalism or blp violations may have been inserted since the latest patrol. Those special pages are filterable by category (for example, Category:Living people). It can also be filtered so that only elements on your watchlist appear, and mentions how many users are watching a page.

Currently, the number of edits to articles and in particular BLPs is so large that we don't have the power to check all of them, we have no way to even coordinate our efforts. This system allows us to monitor changes to articles, in particular BLPs, much more efficiently by comparing new edits to previously patrolled revisions. Even if only one edit of 10 is patrolled, it'll allow to bring potential vandalism and BLP violations to the attention of reviewers and so significantly reduce their general visibility.

Patrolled revisions would also allow checking of edits by autoconfirmed users who are not reviewers, to flagged protected pages, as those are generally automatically confirmed when the previous revision is, but would not be automatically patrolled. To avoid work duplication, patrolled revisions are automatically confirmed.

In addition, a special page displays articles with tagged edits that have not been patrolled.

Consensus has been reached for a two-month trial of flagged protection and patrolled revisions after series of discussions and a final poll. A trial of flagged protection has been prepared by the Wikimedia Foundation and began on June 15, 2010. At the end of the trial, the Wikipedia community will decide whether to continue or discontinue using flagged protection, and whether to test alternative configurations of flagged revisions. A trial of patrolled revisions is not planned yet.

The Wikimedia foundation has set up a team for the development and implementation of those features. The mediawiki extension FlaggedRevs is the core of the technical implementation for flagged protection; testing was done at http://flaggedrevs.labs.wikimedia.org/wiki/Main_Page. Patrolled revisions is planned to be developed independently of the FlaggedRevs extension and could not be made available for the upcoming trial.^[2]

• mw:Help:FlaggedRevs
• mw:Extension:FlaggedRevs