- Nutshell: Remove costly rules (soon).
- Analogy: Remove fuel from the fire.
- Misconception: Will stifle policies (no): removes costly rules but allows others.
- Example: See below #Examples. Beware rules used to censor controversies.
If not English, in what language is this proposal submitted?:
Due to common, recurring problems with some counter-productive rules, there needs to be a directive to remove rules which could cause trouble. Rules about bias (or about controversies) are very likely to spawn conflicts as costly rules.
Perhaps call the activity: "removing costly rules" as a common method to reduce counter-productive rules, which, if continued, could increase conflicts, frustration, or extra workload. Long-term results could be noted: when some rules were removed, then user conflicts were greatly reduced.
Define some quick procedure to initiate removal of counter-productive (or costly) rules, such as rules which typically increase user conflicts, frustration, or extra workload.
The important priorities are:
- The typical effects of setting rules might create impacts beyond the imagination of general users.
- Endless re-debates could be avoided, by omitting rules which would cause such debates.
- Prior costly rules could be listed to help with future decisions.
However, beware the adage, "Everyone makes mistakes". So the removal of costly rules should always be subject to further analysis, and problems should be expected, rather than consider a future disappointment to be a total condemnation of the concept of removing costly rules. Focus on avoiding future costly rules, where avoidance could make a significant difference, and reduce user conflicts and hostility.
Setting rules, often decided by complex debates via talk-pages, requires a lot of time. Also, many people do not consider the "what-could-go-wrong" aspect of rules they write. After months (or years) of working and analyzing policies or guidelines, it becomes apparent that costly rules could have been forseen and predicted, or prevented. Those costly rules (or counter-productive rules) should be prohibited to improve user interaction and reduce debates about the application of those rules.
Some extra effort would be needed to identify and stop costly rules. There are several concerns:
- Some people will be reluctant to avoid well-known, pet rules.
- Some other users might resent limitations in their rules.
- Some costly rules might be slow to prohibit, by over-analyzing the risks ("Paralysis of analysis").
- It is important to consult rules experts, with current knowledge, who are also adept at seeing general problems about setting rules.
A policy expert, in a particular field, might discourage using, perhaps, 20 rules which typically cause problems. That advice could be used to update a list, for that subject area, to warn about those costly rules.
Some disappointments should be expected. For example, prohibiting some rules, in the early days of a project, might appear to be the best strategy, but problems might grow, later, requiring adding rules which were formerly considered too costly.
The following are some examples of costly rules to avoid:
- A likely decision would be to remove rules against "content forks" (POV forks) to avoid numerous heated debates which claimed some valid articles were mere "POV forks" of another article. In an extreme case, an argument would reject having an article "George Harrison" as being a POV-fork of "The Beatles" because of less fame outside the group. In fact, each band member had considerable fame (as individual notability) after the group disbanded, but that might not be common knowledge to all debating the separate article. Consequently, by prohibiting any rules about "POV forks" then a separate article could be judged on its own merits. An article could be judged on the scope of significant text about the subject, rather than wild, intense debates claiming the separate article would be used to POV-soapbox the politics of one band member outside the group. In practice, on the English Wikipedia (enwiki), the policy "en:WP:Content_forking" has often been used in several, heated, hostile, vicious debates to claim an article is a POV-fork intended to advocate a biased, prejudiced view of some controversial aspect of a subject. (Evidence: search Google for "POV fork" and read enwiki discussions). Consequently, the following articles might be created, with less resistance and fighting:
• "Charles Darwin to Evolutionists" - considered a key figure in history
• "Charles Darwin to Creationists" - considered a heretic.
By simply allowing multiple articles to report mainstream, but conflicting views, then most long, expensive debates about POV-pushing of ideas would be stopped.
- In general, remove rules about bias which have been invoked to stop a major action (such as stopping the split of an article). The example of POV-fork rules, above, allows debates to stop creation of entire articles, regardless of any objective measure of the claimed, nefarious bias inside. The more general policy of en:WP:NPOV is not directly associated with stopping large-scale actions (such as banning article creations), so it is applied more evenly, with the focus on the neutral-tone of wording inside articles.
- For greater generality, remove rules about any controversy, where the rule could be used to stop a major action.
- Specifically, for the English Wikipedia, the following could be indicated:
- • Guideline en:WP:Content_forking would be prohibited, as defining costly rules that generate sensational arguments & long debates to kill articles about controversial subjects.
- • Guideline en:WP:CANVASS would be prohibited, as defining costly rules that suppress collaboration between users, by trying to claim users unfairly contacted people they knew, rather than a broader group.
- • Any guideline controlling email would be prohibited, as defining rules to control email outside of enwiki Wikipedia.
Other major detailed examples could be listed here.
- (broader concept, to prohibit future costly rules)
- (narrow concept, to allow 2 articles with differing POV text)
Do you have a thought about this proposal? A suggestion? Discuss this proposal by going to Proposal talk:Reduce content rules causing conflicts/en.
Want to work on this proposal?
- .. Sign your name here!