Requests for Comment/Creating a consensus policy

I am proposing a policy to (somewhat) require community consensus when making possibly controversial changes to custom headers, removal of page sections, and moving pages. This will help prevent edit warring. Particularly, I'm making it in response to Requests for Comment/Ban custom headings from the Reception Wikis again (ended as disputed no consensus), which the creator, SuperStreetKombat, cited "Another problem with them is that users also change the headings of pages every, like, 9 or 10 seconds, like the Funimation page or the Teen Titans GO! page on Terrible TV Shows Wiki and I had to protect both of the pages because of it."

There's also a RFC for preventing users from moving pages that is still open, but I believe a consensus policy will be a more neutral solution.

The policy

 * 1) "Controversial" is defined as a change that is possible to receive opposition, even a slight chance, and opposition not being w:WP:SNOWBALL clauses.
 * 2) Uncontroversial changes can be made without consensus (see the specifics below for more details)
 * 3) *If someone still disagrees with the change and believes it may be a controversial change, they are not to engage in edit warring, and create a discussion to receive consensus.
 * 4) Any possible, or even slight controversial changes or removal require consensus.
 * 5) If someone makes a possibly controversial change, it can be reverted. If they disagree with the revert, they must create a consensus discussion. Users who persist (not adhering to this consensus policy), will receive a warning on their talk page.
 * 6) Edits with obvious intents to vandalize can be reverted as uncontroversial.

Here are some specifics:

Custom headers

 * 1) Generally, consensus will be required for changes or removal of custom headers. There are some exceptions, mentioned below.
 * 2) If there is no custom header, any contributor can create a custom header without consensus.
 * 3) *However, it must adhere to the current policy of them not being overly negative or positive, or offensive.
 * 4) *If it is undisputably noncompliant to the policy mentioned above, it can be replaced with the default as an uncontroversial change.
 * 5) *If it can be possibly disputed, consensus is required for change or removal.

Page moves

 * 1) Consensus will be required for page moves that involve changing the year.
 * 2) Consensus is not required for changes in capitalization, grammar, or otherwise standardization.
 * 3) Pages prone to move warring can be move protected.

Major removal of content

 * 1) This applies to removal of entire sections, lists, NSFW/mature tags, etc.
 * 2) In default, bold removal of content does not require consensus.
 * 3) Unexplained bold removal of content can be reverted without consensus.
 * 4) Bold removal of content, with a understandable explanation in edit summary or unexplained, can be reverted once. After that, consensus is required to prevent edit warring.

Feel free to make suggestions or changes in the votes. - 17:02, 5 May 2022 (UTC)

EDIT May 5, 2022: The RFC about moving pages that I previously mentioned was closed as successful, although I oppose it. Ignore the parts in this RFC about moving pages. - 23:00, 20 May 2022 (UTC)

Support

 * 1) as creator  -  17:02, 5 May 2022 (UTC)
 * 2) I agree with this. Also, note that there shouldn't just be a consensus for changing the year, the seasons should apply to this as well. FatBurn0000 (sandbox | CentralAuth) 20:43, 5 May 2022 (UTC)
 * 3) I made a similar proposal, though regarding specifically deletions and restorations. Blubabluba9990 (talk) 19:59, 17 May 2022 (UTC)