Wikisource:Protection policy

Revision as of 14:44, 13 February 2009 by Ciphers (talk | contribs) (interwiki-ar)
Protection Policy

This page codifies cases where administrators can lock a page from editing (protect).

Page protection disallows any form of editing from either new users (semi-protection), or from all but administrators (protection or full protection). Page protection is most often used to preserve the integrity of a work once it has been completely proofread and uploaded (see also Text integrity), but also serves a number of other purposes.

Criteria for protection

The vast majority of documents hosted by Wikisource are not meant to evolve or be edited, since Wikisource collects material that has been published in the past. Wikisource hosts these published documents without corrections (including any typographical errors or historical inaccuracies). Once a page has been fully proofread, no further changes are necessary and the page should be protected.

These pages should contain the template {{locked}}.

Texts which have been selected as Featured texts are considered fully proofread and should be protected accordingly. However, an additional reason to protect derives from their prominent display on the main page. New editors may decide in good faith to correct a mistake that is present in the original work, being unaware of that fact. Alternately, a malicious user may take the opportunity to edit a heavily viewed page in an undesireable manner. Protection resolves these additional problems as well.

These pages should contain the template {{featured}}, but not {{locked}}.

Malicious edits

By its nature Wikisource is open to undesirable edits, but most are corrected by other editors within a very short time. When certain pages are repeatedly edited maliciously, it may be less effort to simply lock them temporarily while an administrator deals with the malicious user.

Edit wars

In certain circumstances, several editors may continually revert each other or edit conflictingly in good faith. This may happen because of a difference in opinion over the text of a work (where this is not clear), over the appropriate formatting to use, or for a variety of other reasons. This is termed an edit war, and has a highly negative effect on community and collaboration. Should one occur on a page, it should be protected until the users resolve their dispute through discussion.

Pages which are deleted as known copyright violations may sometimes be repeatedly re-added in good faith because users are not aware of its copyright status. These should be deleted to remove the copyright material from the history, recreated with {{deletedpage}}, and protected.

Special cases

  • The main page should always be protected, because it is by far the most heavily viewed page on the project and provides the first impression to new users. Any visible changes to the main page should be discussed on its talk page.
  • System messages: All pages in the MediaWiki namespace are protected from all but administrators by the software. These pages are deeply integrated into user interface, and much confusion would result from careless or malicious editing.
  • Discussion archives: All archives of old discussion should be protected from edit. Such discussions are no longer active and so do not need to be edited. This is to preserve the integrity of the discussion and give a reliable reference for the community. This includes but is not limited to: (1) Scriptorium archives; (2) Main Page talk archives; (3) Copyvio archives; (4) User talk archives. However, this does not include archive index pages, which do not contain discussions, and need to be edited periodically to link newly created archives.

Pages which should not be protected

Talk pages

Talk pages should not be protected except in the most extreme cases. These are the only way to communicate about or propose changes to its accompanying article. Should an error be noticed in a text that has been protected, a notice should be posted here.

User talk pages should almost never be protected as well, especially if they are blocked. In the latter case, this page is their single method of communication with the community. These should only be protected in cases where the user is editing them with blatant malice or bad faith.

Wikisource namespace

All pages in the Wikisource namespace should be unprotected. These should always be open to collaboration and improvement, and many exist specifically to be edited by all users (such as the community discussion page or Proposed deletions).

Procedure

Preservation of integrity

  1. Texts are to go through the steps laid out at Wikisource:Text quality up to the 75% stage.
  2. Once a page has reached the 75% level, i.e. when checked against a hard copy of the material by one Wikisource user, a protection request can be made at Wikisource:Protection requests. The proofreader's signature should also be placed in the appropriate places on the text info template which will be located on the article's talk page.
  3. If the page has not been changed since the protection request was made, and the page has been issued with the relevant links (author link etc.), category and infotemplate, then an admin is to protect the page, indicate that it is in the 75% level, and add the locked template to the bottom of the page.
    1. If the text has been changed since the protection request was made, then either the requesting user must approve of the changes or the text must be reverted before it can be protected.
  4. A request for unprotection of a protected page can be made for proofreading purposes by a Wikisource user at Wikisource:Protection requests.
  5. An admin can then unprotect the page so that the requesting user can proofread and correct the text.
    1. If work on the text has not started one week from the unprotection the page is to be reprotected.
  6. When the proofreading is done, the proofreading user should place his/her signature at the appropriate place in the text info template and make a request for reprotection at Wikisource:Protection requests.
  7. An admin is then protect the page and indicate that it is in the 100% state (proofread by more than one user).