Wikipedia:保護政策

呢版係粵語維基百科正式政策，維基友普遍接受，通常都要跟足。改佢之前要有共識先，重要嘅修改要響討論版傾過，同埋喺大圍報告版宣布過。

捷徑

管理員可以保護頁面去限制改嗰版。

全保護 禁止任何人改，除咗管理員。全保護檔案就可以唔畀人覆寫。
半保護 唔畀無名氏或者註冊咗少過四日嘅用戶去改。
移動保護 唔畀搬，一般全保護已經包括埋呢個功能。
連鎖保護 全保護嗰啲包括喺打算保護嗰版嘅頁。

目前，如果要請求保護或者解保護，請去WP:管理員留言板。

所有嘅保護或解除保護動作都會喺保護日誌度列出。

全保護

下面段文未譯好，歡迎你幫手。

Indefinite full protections are used for:

High visibility pages such as the Main Page in order to prevent vandalism. This includes templates transcluded to these pages.
The site's logo, press releases, and key copyright and license pages, for legal reasons. Admins should not make significant changes to these pages without prior discussion.
Certain "system administration" pages, including many editorial, deletion and stub templates, and the entire MediaWiki namespace. These are pages that need rarely be changed, and that because of widespread usage can cause large-scale disruption if vandalized, or modified ill-advisedly. Again, admins should not make significant changes to these pages without prior discussion.
Pages deleted by consensus that are repeatedly recreated. These are listed in either Category:Protected deleted pages or Wikipedia:Protected titles. Requests to overturn such a deletion should be made through the deletion review process.
Personal css and js pages like User:Example/monobook.css or User:Example/cologneblue.js are automatically fully protected by the MediaWiki software. Only the account associated with these pages and admins are able to edit them.

Temporary full protections are used for:

Enforcing a "cool down" period to stop an edit war.
A history-only review of the article during some discussions on deletion review.
Preventing abuse of the {{unblock}} template or other disruptions by a blocked user on their user talk page.

Content disputes

Except in cases of clear vandalism, or issues with legal impact such as copyright or defamation, pages protected in an edit war are protected in whatever version they happen to be currently in. Protection during an edit war is not an endorsement of the current version. Editors should not ask for a specific version of a page to be protected or, if it has already been protected, reverted to a different version. Instead, editors should attempt to resolve the dispute on the related talk page. See also m:The Wrong Version.

During edit wars, admins should not protect pages when they are involved as a party to the dispute, except in the case of simple vandalism or libel issues against living people. Admins should not edit pages that are protected due to a content dispute, unless there is consensus for the change, or the change is unrelated to the dispute. However, this should only be done with great caution, and administrators doing so should indicate this on the article's talk page.

Semi-protection

Indefinite semi-protection may be used for:

Articles subject to heavy and continued vandalism, such as George W. Bush.
Biographies subject to vandalism and/or POV-pushing that are not widely watchlisted.
User pages (but not user talk pages), when requested by the user.

Temporary semi-protection may be used for:

Preventing vandalism when blocking users individually is not a feasible option, such as a high rate of vandalism from a wide range of anonymous IP addresses.
Article talk pages that are being disrupted; this should be used sparingly because it prevents new users and anons from being part of discussions.

Semi-protection should not be used:

As a preemptive measure against vandalism before any vandalism has occurred.
In a content dispute between registered users and anonymous users, with the intention to lock out the anonymous users.
With the sole purpose of prohibiting editing by anonymous users. Protection should be used only to prevent continuing disruption.

Move protection

Page move protection is used for:

Cases of frequent or on-going page-move vandalism
During a page name dispute
High-visibility pages which have no reason to be moved, such as Wikipedia:Administrator intervention against vandalism.

Fully protected pages are by default also move protected. If a protected page is moved by an admin, the page will be protected at the new location, and the redirect will be unprotected at the page's original location.

The same restrictions that apply to full protection during a dispute also apply to move protection during a dispute (for example, admins should avoid favouring one name over another, and protection is not an endorsement of the current name).

New accounts cannot move any pages, as described at Wikipedia:User access levels.

Protection related to the main page

The main page is always fully protected, as explained by its FAQ. There is a separate (disputed) guideline, Wikipedia:Main Page featured article protection, covering semiprotection of today's featured article. At present the guideline is that semi-protection may be applied during very high levels of vandalism.

Cascading protection

Cascading protection is used

On very high visibility pages such as the Main Page.
As a new system for dealing with deleted pages that get repeatedly recreated.

Cascading protection automatically fully protects any page (e.g., template or image) that is currently transcluded onto the protected page to prevent vandalism.

Pages protected due to Office Actions

Some articles may be protected by office staff due to copyright or libel issues (among others) against the Wikimedia Foundation.

These protections should be left alone by all administrators unless explicitly told otherwise by someone from the Foundation.

Unprotection

With the exception of any pages tagged with the {{office}} or {{reset}} templates, any admin may unprotect any page after a reasonable period has elapsed, 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.

When protecting a page, an admin can set a time limit; when this limit expires, the page is automatically unprotected.