Misplaced Pages

:Protection policy: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 18:04, 26 December 2006 view sourceTreyd500 (talk | contribs)183 editsm Fixed Link← Previous edit Revision as of 16:50, 1 January 2007 view source Steel (talk | contribs)20,265 edits Update and cleanup. Removing redundancies and info specific to semi-protection, general rephrasing, etcNext edit →
Line 1: Line 1:
{{policy|]<br />]}} {{policy|]<br />]}}


] have the ability to protect pages so that they cannot be edited, or images so that they cannot be overwritten, except by other administrators. Administrators can also protect pages from ] only. Administrators have the additional ability to protect pages from being edited by unregistered users or users with accounts less than four days old. ] have the ability to protect pages so that they cannot be edited except by other administrators. In addition, protected images cannot be overwritten. If necessary, pages can be protected just against ] or ].


During an ], do not ask for a page to be protected on a specific version or, if it has already been protected, reverted to some other version the current one. Protection is '''not an endorsement of the current version'''. Instead, go to the talk page and attempt to resolve the dispute. Non-admins can propose changes to protected pages on the talk page.
These abilities are only to be used in limited circumstances as ].


If a protected page is moved, the page will be protected at the new location, and the redirect will be unprotected at the page's original location.
Administrators '''must not''' protect pages they are actively engaged in editing, except in the case of ].

If a page is protected because of an edit war, please do not ask for it to be protected in some other version than it currently is. A protection is ''not'' an endorsement of the current version. Instead, go to the talk page and attempt to resolve the dispute. Non-admins can propose changes to protected pages on the talk page.

If an administrator moves a protected page, the page will be protected at the new location, and the redirect will be unprotected at the page's original location.


==Uses== ==Uses==
===A permanent or semi-permanent full-protection is used for:===

*Protecting high visibility pages such as the ] from vandalism. This includes templates transcluded to these pages.
===A permanent or semi-permanent protection is used for:===
*Protecting high visibility pages such as the ] from vandalism.
*Maintaining the integrity of the site's logo, press releases, and key copyright and license pages (for legal reasons). *Maintaining the integrity of the site's logo, press releases, and key copyright and license pages (for legal reasons).
*Protecting certain ''"system administration"'' pages. This includes many editorial templates, such as deletion notices and stub templates. *Protecting certain "system administration" pages. This includes many editorial templates, such as deletion notices and stub templates.
*Protecting the MediaWiki namespace and pages transcluded to it. These pages affect the system interface for all users. *Protecting the MediaWiki namespace and pages transcluded to it. These pages affect the system interface for all users.
*Protecting deleted articles that are repeatedly created. See ] for more information.
*User talk pages and their subpages that are subject to repeated vandalism, following a user's blocking (note the fact that blocked users can still edit their own user talk pages).
*Protecting deleted articles that are repeatedly created; in this case {{]}} is used. See ] for more info.


===A temporary protection is used for:=== ===A temporary full-protection is used for:===
*Enforcing a "cool down" period to stop an "]," upon ]. *Enforcing a "cool down" period to stop an edit war.
*Protecting a page or image that has been a recent target of ''persistent'' vandalism or ''persistent'' edits by a banned user.
*Preventing changes to a page while investigating a possible bug in the ] software. *Preventing changes to a page while investigating a possible bug in the ] software.
*Allowing for history-only review during discussions on article restoration. *Allowing for history-only review during discussions on article restoration.
*Preventing abuse of the {{tl|unblock}} privilege or other disruption from a blocked user on their talk page while they are blocked.

The protection of a page on any particular version is not meant to express support for that version and requests should therefore not be made that the protected version be reverted to a different one.

Talk pages and user talk pages are not protected as a rule, except in extreme circumstances.

'''Important Note:''' When a page is particularly high profile, either because it is linked off the main page, or because it has recently received a prominent link from offsite, it will often become a target for vandalism. It is rarely appropriate to protect pages in this case. Instead, consider adding them to your watchlist, and ].


==How== ==How==
Line 41: Line 29:
#Remove <nowiki>{{protected}}</nowiki> from the top of an unprotected page and make mention of the removal in the edit summary #Remove <nowiki>{{protected}}</nowiki> from the top of an unprotected page and make mention of the removal in the edit summary


Admins should '''not''' protect pages in which they are involved. Involvement includes making substantive edits to the page (fixing vandalism does not count), or expressing opinions about the article on the talk page before the protection. Admin powers are not editor privileges &mdash; admins should only act as servants to the user community at large. If you are an admin and you want a page in an edit war in which you are somehow involved to be protected, you should contact another admin and ask them to protect the page for you. Not only is this the preferable method, it is also considered more ethical to do so as it helps reduce any perceived conflict of interest. Admins should '''not''' protect pages in which they are involved, except in the case of ] or libel issues against ]. At any rate, semi-protection usually suffices in these cases. Involvement includes making substantive edits to the page (fixing vandalism does not count), or expressing opinions about the article on the talk page before the protection. Admin powers are not editor privileges &mdash; admins should only act as servants to the user community at large. If you are an admin and you want a page in an edit war in which you are somehow involved to be protected, you should ] in the way a normal user would. Admins should avoid favouring one version of the article over another in general.

In addition, admins should avoid favouring one version of the article over another, unless one version is ]. In this case, the protecting sysop may choose to protect the non-vandalism version. In cases of 3RR violations, admins may protect the version immediately before the first violation i.e. immediately before the first occurrence of a fourth revert.

In general, temporarily protected pages should not be left protected for very long, and discussion pages should be left open.


There is no need to protect personal css and js pages like user/monobook.css or user/cologneblue.js. Only the account associated with these pages and administrators are able to edit them. There is no need to protect personal css and js pages like user/monobook.css or user/cologneblue.js. Only the account associated with these pages and administrators are able to edit them.


== Editing protected pages == == Editing protected pages ==
Edits to protected pages should be made with the full agreement of all parties involved in the dispute. In the following specific cases, an exception is made:

Administrators should be cautious about editing protected pages and do so in accordance with consensus and any specific guidelines on the subject. In most cases, administrators should first raise the issue on the relevant talk page, unless a case of obvious trolling and/or revert warring, or blatantly unsuitable content.

In the following specific cases, an exception is made:


* Adding a {{tl|protected}} or {{tl|vprotected}} template * Adding a {{tl|protected}} or {{tl|vprotected}} template
* Adding a link to ] or ], or a similar disclaimer about the current state of an article. * Adding a link to ] or ], or a similar disclaimer about the current state of an article.
* Reverting to an old version of the page from a week or so before the controversy started ''if'' there is a clear point before the controversy.
* Reverting to a clean version, as described above.
* Correcting spelling mistakes or typos. * Correcting spelling mistakes or typos.


Special caution is needed in editing permanently and semi-permanently protected pages. In nearly all cases, administrators should not make substantial changes to pages protected for legal reasons, excepting cases of obvious trolling and/or vandalism. Because of their visibility and importance, most MediaWiki namespace pages should be approached with extreme caution and only by those who adequately understand the consequences of their changes. Special caution is needed in editing permanently and semi-permanently protected pages. In nearly all cases, administrators should not make substantial changes to pages protected for legal reasons. Because of their visibility and importance, most MediaWiki namespace pages should be approached with extreme caution and only by those who adequately understand the consequences of their changes.


Edits can be made to already protected pages via <nowiki>{{</nowiki>]}} requests. Non-admins can request edits to a protected page with the {{tl|edit protected}} template.


== Page-move protection == == Page-move protection ==
Similar considerations apply to protecting a page against being moved only. Page move protection is appropriate in cases of frequent or on-going page-move vandalism, during a page name dispute, or to high visibility/risk pages which have no reason to be moved (this includes many project pages like ])

Similar considerations apply to protecting a page against being moved, only. In particular, page move protection is appropriate:
*in cases of frequent or on-going page-move vandalism;
*for persistent page-move disputes, on ];
*or where such a dispute continues during the course of a listing on ].

==Protecting the talk page of a blocked user==
Users can edit their own User Talk pages, even while ]. This is in order to allow appeals and discussion about blocks. However, if a user abuses this feature, and continues with ] or ] such as excessive personal attacks on his own User Talk page, the page can be protected from editing, thus disabling this one ability blocked users have at the time of blockage.


==Pages protected due to ] policy== ==Pages protected due to ] policy==
{{further|]}} {{further|]}}
Per ], some articles may be protected by ] or his alias for official duties ], due to complaints at the Wikimedia Foundation Office. Per ], some articles may be protected by ] due to copyright or libel issues (among others) against the Wikimedia Foundation. Danny has stated he will use his alias ] when acting in an official capacity for the Foundation.


'''Do not unprotect or revert a WP:OFFICE edit unless and until you are authorized by Danny or the Wikimedia Foundation to do so. There may at times be legal reasons for this.''' '''<font color=red>Do not unprotect or revert a WP:OFFICE edit unless and until you are authorized by Danny or the Wikimedia Foundation to do so. There may at times be legal reasons for this.</font>'''


== List of protected pages == == List of protected pages ==
At present, a ] is maintained by ].

If you protect (or move-protect) a page, or find a protected page not listed on ], please add it to the ]. Please also add a '''short''' description of ten words or fewer indicating why you protected it. If you need to say more, discuss on the talk page of the page you protected.


==Unprotecting== ==Unprotecting==
With the exception of any pages tagged with the {{tl|office}} or {{tl|reset}} templates, any admin may unprotect any page after a reasonable period has lapsed, particularly if there is no discussion on the talk page. However, unless a request for unprotection has been made on ], pages should not be unprotected soon after protection without prior consultation with the admin who first locked the page. This is particularly important in the case of controversial pages, where the conflict may start up again and the protecting admin may be in touch with the disputants. See ]. With the exception of any pages tagged with the {{tl|office}} or {{tl|reset}} templates, any admin may unprotect any page after a reasonable period has lapsed, particularly if there is no discussion on the talk page. However, unless consensus has been reached, pages should not be unprotected soon after protection without prior consultation with the admin who first protected the page. This is particularly important in the case of controversial pages, where the conflict may start up again and the protecting admin may be in touch with the disputants. See ].


== User css/js == == User css/js ==
To stop other users from changing other Wikipedians' ]/] pages, they are automatically protected. They can only be edited by the user or a SysOp. To stop other users from changing other Wikipedians' ]/] pages, they are automatically protected. They can only be edited by the user or an administrator.


==See also== ==See also==

Revision as of 16:50, 1 January 2007

This page documents an English Misplaced Pages policy.It describes a widely accepted standard that editors should normally follow, though exceptions may apply. Changes made to it should reflect consensus.Shortcut
  • ]

Administrators have the ability to protect pages so that they cannot be edited except by other administrators. In addition, protected images cannot be overwritten. If necessary, pages can be protected just against anonymous and newly registered users or moves.

During an edit war, do not ask for a page to be protected on a specific version or, if it has already been protected, reverted to some other version the current one. Protection is not an endorsement of the current version. Instead, go to the talk page and attempt to resolve the dispute. Non-admins can propose changes to protected pages on the talk page.

If a protected page is moved, the page will be protected at the new location, and the redirect will be unprotected at the page's original location.

Uses

A permanent or semi-permanent full-protection is used for:

  • Protecting high visibility pages such as the Main Page from vandalism. This includes templates transcluded to these pages.
  • Maintaining the integrity of the site's logo, press releases, and key copyright and license pages (for legal reasons).
  • Protecting certain "system administration" pages. This includes many editorial templates, such as deletion notices and stub templates.
  • Protecting the MediaWiki namespace and pages transcluded to it. These pages affect the system interface for all users.
  • Protecting deleted articles that are repeatedly created. See Category:Protected deleted pages for more information.

A temporary full-protection is used for:

  • Enforcing a "cool down" period to stop an edit war.
  • Preventing changes to a page while investigating a possible bug in the MediaWiki software.
  • Allowing for history-only review during discussions on article restoration.
  • Preventing abuse of the {{unblock}} privilege or other disruption from a blocked user on their talk page while they are blocked.

How

  1. Do not edit or revert a temporarily protected page, except to add a protected page notice, a link to Misplaced Pages:Accuracy dispute or Misplaced Pages:NPOV dispute, or a similar disclaimer about the current state of an article, unless there is widespread agreement that the page was protected in violation of these policies.
  2. Do not protect a page you are involved in an edit dispute over.
  3. Add an appropriate protection template (e.g. {{protected}} or {{vprotected}} for vandalism) to the top of the temporarily protected page and make mention of the protection in the edit summary. If protecting a template, place the notice inside <noinclude></noinclude> tags so that it does not show up when the template is transcluded. Alternatively, the tag can go on the template's talk page.
  4. List pages you protect on Misplaced Pages:Protected page
  5. Consider encouraging a resolution between the disputing parties
  6. Remove {{protected}} from the top of an unprotected page and make mention of the removal in the edit summary

Admins should not protect pages in which they are involved, except in the case of simple vandalism or libel issues against living people. At any rate, semi-protection usually suffices in these cases. Involvement includes making substantive edits to the page (fixing vandalism does not count), or expressing opinions about the article on the talk page before the protection. Admin powers are not editor privileges — admins should only act as servants to the user community at large. If you are an admin and you want a page in an edit war in which you are somehow involved to be protected, you should request protection in the way a normal user would. Admins should avoid favouring one version of the article over another in general.

There is no need to protect personal css and js pages like user/monobook.css or user/cologneblue.js. Only the account associated with these pages and administrators are able to edit them.

Editing protected pages

Edits to protected pages should be made with the full agreement of all parties involved in the dispute. In the following specific cases, an exception is made:

Special caution is needed in editing permanently and semi-permanently protected pages. In nearly all cases, administrators should not make substantial changes to pages protected for legal reasons. Because of their visibility and importance, most MediaWiki namespace pages should be approached with extreme caution and only by those who adequately understand the consequences of their changes.

Non-admins can request edits to a protected page with the {{edit protected}} template.

Page-move protection

Similar considerations apply to protecting a page against being moved only. Page move protection is appropriate in cases of frequent or on-going page-move vandalism, during a page name dispute, or to high visibility/risk pages which have no reason to be moved (this includes many project pages like Misplaced Pages:Articles for deletion)

Pages protected due to WP:OFFICE policy

Further information: ]

Per Jimbo Wales, some articles may be protected by Danny due to copyright or libel issues (among others) against the Wikimedia Foundation. Danny has stated he will use his alias User:Dannyisme when acting in an official capacity for the Foundation.

Do not unprotect or revert a WP:OFFICE edit unless and until you are authorized by Danny or the Wikimedia Foundation to do so. There may at times be legal reasons for this.

List of protected pages

At present, a list of protected pages is maintained by User:VoABot.

Unprotecting

With the exception of any pages tagged with the {{office}} or {{reset}} templates, any admin may unprotect any page after a reasonable period has lapsed, particularly if there is no discussion on the talk page. However, unless consensus has been reached, pages should not be unprotected soon after protection without prior consultation with the admin who first protected the page. This is particularly important in the case of controversial pages, where the conflict may start up again and the protecting admin may be in touch with the disputants. See Misplaced Pages:Wheel war.

User css/js

To stop other users from changing other Wikipedians' css/js pages, they are automatically protected. They can only be edited by the user or an administrator.

See also

Categories:
Misplaced Pages:Protection policy: Difference between revisions Add topic