Wikipedia:Pending changes/Request for Comment March 2016

This is a failed proposal.

Consensus for its implementation was not established within a reasonable period of time. If you want to revive discussion, please use the talk page or initiate a thread at the village pump.

Closed as no consensus. RfC open for 1 month and six days already. Insufficient participation to establish a consensus. Recommend implementing the suggestions made by KrakatoaKatie and starting again. --Kudpung กุดผึ้ง (talk) 06:01, 17 April 2016 (UTC)[reply]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Pending changes discussions

I would like to re-open the PC2, as the last PC discussion was held in 2012. And the PC2 discussion in 2014 ended as no consensus. 333 -blue 11:57, 12 March 2016 (UTC) [reply]

About pending changes

Protection levels and their impact on various Wikipedia user groups^[α]
F	Protection level	New or unregistered editors	Confirmed	Extended confirmed	Template editor^[β]	Admin	Interface admin^[γ]	Appropriate for...
Editing	None	Normal editing						The vast majority of pages.^[δ]
	Pending changes	Can edit Changes are only visible to logged-in users until reviewed by a pending changes reviewer or administrator.^[ε]	Can edit Changes are visible to everyone if there aren't any unreviewed pending changes. Otherwise, they are only visible to logged-in users until reviewed by a pending changes reviewer or administrator.^[ε]			Can edit If there are any unreviewed pending changes, the administrators will be required to review them before they can edit the page.^[ε]		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 newly registered users. Some highly visible templates and modules.
	Extended confirmed	Cannot edit		Normal editing				Contentious topics 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				Can edit^[ζ]		Pages with persistent disruption from extended confirmed accounts.
	Office	Cannot edit				Can edit^[η]		Pages that the Foundation has determined to be exceptionally sensitive.
	Cascade^[θ]	Cannot edit				Can edit		Particularly visible pages, such as the Main Page, to prevent vandalism to pages that are transcluded onto them.
	Interface^[ι]	Cannot edit					Normal editing	Scripts, stylesheets, and similar objects fundamental to operation of the site or that are in other editors' user spaces.
Creating pages	None	Cannot create^[κ]^[λ]	Can create					The vast majority of page titles.^[δ]
Creating pages	Create	Cannot create^[λ]		Adjustable Protection may be applied to neither, either, or both groups.		Can create		Pages that have been repeatedly and problematically re-created. This form of protection is often called "salting".
Moving pages	None	Cannot move	Can move					The vast majority of pages.^[δ]
Moving pages	Move	Cannot move		Adjustable Protection may be applied to neither, either, or both groups.		Can move		Pages that have been the subject of move wars. Pages that are edit-protected are usually also move-protected at the same level.
Uploading files	None	Cannot upload	Can upload					The vast majority of file names.^[δ]
Uploading files	Upload	Cannot upload		Adjustable Protection may be applied to neither, either, or both groups		Can upload		Files that have been repeatedly uploaded after deletion
Notes: ^ Details about historical protection levels and user groups no longer in use are available at Wikipedia:Protection policy § Retired protections. ^ This table assumes that template editors are also extended confirmed, which is almost always the case for non-bot accounts. ^ This table assumes that an interface administrator is also a "regular" administrator, which is almost always the case in practice. ^ ^a ^b ^c ^d This is the default protection level. ^ ^a ^b ^c However, if any editors (including unregistered editors) revert all unreviewed pending changes back to the latest accepted version, that revision is automatically accepted and pending changes reviewers and administrators aren't prompted or notified. ^ Only noncontroversial changes or requested changes following an achieved consensus should be performed. ^ Only with the approval from the Wikimedia Foundation. ^ Cascade protection extends to all pages that are transcluded onto the protected page, unless the transcluded page is at the same protection level or higher. Cascade protection can only be applied to pages that are fully or office-protected because otherwise it creates a workflow flaw. ^ The interface protection level is automatically set by the MediaWiki software to a specific set of pages, such as pages in the MediaWiki namespace, system-wide CSS and JavaScript pages, and personal CSS and JavaScript pages of other users. It is not a protection level that an administrator can manually apply to any page, nor is it a protection level that can be modified on pages currently under interface protection. Because of this, administrators also cannot cascade-protect pages that are Interface-protected. ^ This has been in effect for unregistered users since 5 December 2005. The restriction was extended to newly registered users on a six month trial basis starting on 14 September 2017. The extension became permanent on 18 April 2018. ^ ^a ^b Under the default no protection, unregistered and newly registered users can create talk pages in all namespaces and draft articles in the Draft namespace. For these namespaces, it would therefore be possible for the creation protection to only apply to unregistered and newly registered users view talk edit

Reason

Some articles may vandalize by autoconfirmed users, and anonymous editors keep undoing their vandals, just in case if this happens. 333 -blue 12:58, 12 March 2016 (UTC)[reply]

Support

Support I would only use this instead of full protection or user blocking if an article had continuous vandalism by autoconfirmed users, but that same article had lots of useful edits from autoconfirmed users too. Peter Sam Fan 20:44, 4 April 2016 (UTC)[reply]

Discussion

@333-blue: You need to be very specific here. In the last RFC, there were three proposals that had consensus. Are you asking for comment on whether those proposals should be now implemented? Are you asking for different criteria to be used? You have to spell it out, because vagueness kills RFCs like kryptonite and it makes closing them next to impossible. I also suggest that, after your proposal has been refined, that you list it at WP:CENTRAL, as this is a major policy change that needs wide input. Katie^talk 17:04, 16 April 2016 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

[1] Details about historical protection levels and user groups no longer in use are available at Wikipedia:Protection policy § Retired protections.

[2] This table assumes that template editors are also extended confirmed, which is almost always the case for non-bot accounts.

[3] This table assumes that an interface administrator is also a "regular" administrator, which is almost always the case in practice.

[default-4] This is the default protection level.

[unless-5] However, if any editors (including unregistered editors) revert all unreviewed pending changes back to the latest accepted version, that revision is automatically accepted and pending changes reviewers and administrators aren't prompted or notified.

[6] Only noncontroversial changes or requested changes following an achieved consensus should be performed.

[7] Only with the approval from the Wikimedia Foundation.

[8] Cascade protection extends to all pages that are transcluded onto the protected page, unless the transcluded page is at the same protection level or higher. Cascade protection can only be applied to pages that are fully or office-protected because otherwise it creates a workflow flaw.

[interface-9] The interface protection level is automatically set by the MediaWiki software to a specific set of pages, such as pages in the MediaWiki namespace, system-wide CSS and JavaScript pages, and personal CSS and JavaScript pages of other users. It is not a protection level that an administrator can manually apply to any page, nor is it a protection level that can be modified on pages currently under interface protection. Because of this, administrators also cannot cascade-protect pages that are Interface-protected.

[10] This has been in effect for unregistered users since 5 December 2005. The restriction was extended to newly registered users on a six month trial basis starting on 14 September 2017. The extension became permanent on 18 April 2018.

[creation-11] Under the default no protection, unregistered and newly registered users can create talk pages in all namespaces and draft articles in the Draft namespace. For these namespaces, it would therefore be possible for the creation protection to only apply to unregistered and newly registered users

[α]

[β]

[γ]

[δ]

[ε]

[ζ]

[η]

[θ]

[ι]

[κ]

[λ]