Warcraft Wiki talk:Protection policy
This policy is under proposal.
|
|
|
Votes
- Yes
- Yes Pcj (T •C ) 19:28, 23 July 2017 (UTC) - (Originally proposed)
- Yes Xporc (talk) 20:00, 23 July 2017 (UTC) - (optional comment)
- No
- No — foxlit (talk) 17:49, 27 July 2017 (UTC) - (If "this policy will serve as a guideline", it might as well be a guideline rather than a policy.)
- No — Surafbrov T / C 05:58, 26 February 2018 (UTC) - (It's pretty much when it is deemed appropiate. I agree with foxlit on this. It would seem better as a guideline.)
- No Alayea (talk / contrib) 21:52, 24 October 2018 (UTC) - (See below.)
- No DDC (talk) 01:54, 30 October 2021 (UTC) - (Right now it reads as a guideline, so I agree with eitehr foxlit (make it a guideline) or Alayea (merge with WP:Protected pages).)
Comments
The single motivating example for this presented in Forum:Protection policy seems unconvincing to me (Wrath of the Lich King, indefinite autoconfirmed protection applied was equivalent to the page not being protected at all); it's unclear why this policy is necessary. Are any editors actually negatively affected by the current set of protected pages?
On the surface, the guidelines appear to call for unprotecting e.g. {{Infobox Alliance}}, but I'm not sure whether this is actually an intended effect or not. — foxlit (talk) 17:49, 27 July 2017 (UTC)
- The go-to practice for administrators is to indefinitely protect articles when they don't deserve it, which is sub-optimal. The purpose of this policy is to lay out a rationale to be able to determine an appropriate duration for protection, or decide if it is even required. Re: {{Infobox Alliance}}, it's included only on Alliance, why is it protected anyway? ---Pcj (T •C ) 17:55, 27 July 2017 (UTC)
- The go-to practice for administrators is to do what they think is appropriate. After taking a random sample of recently unprotected articles, I fail to see the sub-optimality: autoconfirmed protection doesn't actually affect anyone (and most instances of it were inherited from long ago), and a few cases of "this page should not be edited anymore" seemed justified. Do we have an epidemic of pages that prevent edits without cause somewhere? — foxlit (talk) 18:31, 27 July 2017 (UTC)
Bump. Xporc (talk) 13:38, 26 August 2017 (UTC)
I have to agree with foxlit that it's much more of a guideline than an actual policy. That being said, I much prefer the re-write pcj did. I suggest moving this page onto Project:Protected pages while keeping the protected page example from the original lede section. -- Alayea (talk / contrib) 21:52, 24 October 2018 (UTC)
- If this is to be a 'policy' then should emphasize the process for appealing the decision to protect a page. If this is to be a 'guideline' then it is basically well written already, save for not calling it a policy. DDC (talk) 00:20, 1 November 2021 (UTC)
I don't really have an opinion on the subject, but I think that after so many years, it deserves either to be discussed again or to conclude the vote! WardsJames (talk) 22:30, 9 September 2023 (UTC)