Marvel Cinematic Universe Wiki

With the release of Deadpool & Wolverine we'd like to remind the community of some things. Please DO NOT add info from the Fox X-Men movies when it comes to pages. Only information stated within the movie itself is eligible to be added. In addition, do not upload pirated images from cam copies. We'd also like to ask that universe pages NOT be created if the universe name has a Placeholder template on it, as that indicates it is not the intended final name. Thank you.

READ MORE

Marvel Cinematic Universe Wiki
Advertisement
Marvel Cinematic Universe Wiki
The Marvel Cinematic Universe Wiki is continually revising our policies.
If you locate any unwritten rule that should be clarified, use the talk page to make a proposal


The Consensus and Voting Policy is a basic guideline and set of rules to denote how community consensus and voting operates on the wiki, how the community can participate in those decisions, and how collaboration can work between Staff members and editors.

Defining Consensus

Consensus refers to a general agreement by members of the Marvel Cinematic Universe Wiki community. Consensus occurs every day whenever an edit is not contested or reverted, as this is considered presumed consensus. When an edit is altered, this new contribution is considered consensus unless it is overturned. When two or more editors have a disagreement on an edit, they are to use the talk page or Message Wall to begin discussion and seek consensus. Consensus is the resolution when these opposing parties come to an agreement and/or a compromise. If they cannot reach consensus, Staff members are to provide a resolution to the discussion, which should take into account pre-existing policies alongside all arguments, concerns and objections both parties stated.

What is Consensus Voting

Most discussions and debates on Marvel Cinematic Universe Wiki receive resolution by editing and discussion, not voting. However, for certain discussions, Staff may induce a voting process in Talk pages. While consensus itself is not defined as the preference of the majority vote, the outcome of a community vote can be used by Staff to determine consensus (the general agreement of the community) and provide the best solution for the wiki. The Consensus and Voting Policy allows for the community to have a say in certain wiki matters through a community voting process, with the goal of achieving overall acceptance and approval of the majority. Unanimity does not apply during this process, meaning the outcome of a vote does not require all participants to support one side unanimously.

Voting is to take place primarily on the Talk: namespace on the wiki (Talk pages for the page in question) although Staff may also seek a vote within the Treehouse and/or the Citadel. Votes/community agreement that occur on the official Discord server may also taken into account as official community input by Staff when finalizing decisions. During these voting and/or discussions, editors are not to edit the page(s) in question to fit their preference and instead must seek resolution on the talk page.

All editors are required to respect and adhere to election rulings from June 24, 2024 onward. Rulings made prior to this date that never underwent a community voting process or any form of community consensus are eligible to be contested and therefore undergo a community voting process to determine a new outcome.

How Voting Works

Either within a Talk page or a community page like the Treehouse, Staff members will add a "Support/Oppose" section where users can add a short reason for their support or opposition followed with their signature (type in ~~~~); an example is given below.

Support

  • I support this initiative. ~~~~
  • I too support this. ~~~~
  • I agree with this proposal. ~~~~

Oppose

  • I disagree with this. ~~~~
  • Not a fan. ~~~~
  • I do not agree with this proposal. ~~~~

Proposals made by Staff members can seek for votes using the Support/Oppose system from their initial proposal. However, community members are not to add them. Community members are to add their proposals while other community members weigh in naturally. After seven (7) days allotted for ample discussion, a Staff member is to add the Support/Oppose section. At this point, another seven (7) days are given to allow community members enough time in their busy lives to cast their vote. Fourteen (14) days after the proposal was first made, it can then be finalized and concluded. A vote can be ended prematurely in less than 7 days if one side has over a dozen (12) votes compared to the other side after at least three (3) days of voting.

The resolution to community consensus voting is determined when one outcome has more votes than the other on a ratio of 1.5:1 or more, with a minimum of seven (7) votes cast.

Tiers

While the community is welcome to participate in all eligible discussions, the wiki splits all decisions into tiers:

  • Tier 1: A wiki decision that requires majority approval. All eligible community members have the ability to vote, and the outcome of the vote must be honored if it is in adherence with policies, specifically versions of the policies that were in effect at the time the proposal was posted. This includes, but is not limited to, proposals to rename character, item, event or location pages in adherence with policies. Any Treehouse proposal made by a bureaucrat falls under Tier 1 unless explicitly stated otherwise in the proposal.
  • Tier 2: A wiki decision that seeks community consensus. All eligible community members have the ability to vote, although the final outcome is not determined by the majority community vote, but rather a majority decision made by Staff members (which includes bureaucrats, administrators, content moderators, and when eligible, discussion/thread and/or server moderators) based on community consensus. The community is still allowed to have a voice and share their input to guide Staff decision. Tier 2 should not be invoked by Staff for all changes they propose in order to allow the community a fair chance to have a deciding voice in community decision making process. Tier 2 automatically applies to all policies; while eligible community members are able to use the Talk page of any policies in order to post suggestions for amendment, Staff members have final approval and vote on policies. This applies to any new policies enacted by bureaucrats and administrators, which must receive majority approval from other Staff members. However, the community must also be aware of any new policies or massive policy amendments so that they have the chance to share their thoughts on it on the policy's Talk page. All proposals posted in the Treehouse by community members fall under Tier 2. However, if a bureaucrat or administrator replies to the proposal seeking for a community vote, it shifts to Tier 1 unless explicitly stated otherwise.
  • Tier 3: A wiki decision that solely requires Staff consensus. These discussions often occur on Discord Staff channels, where Staff members (which includes bureaucrats, administrators, content moderators, and when eligible, discussion/thread and/or server moderators) vote on the decision at hand. General community voting consensus does not occur. Tier 3 rarely applies to proposals on the Treehouse, the community space intended for proposals. Instead, Tier 3 is reserved to Wiki site decisions, including but not limited to, changes to an Infobox structure, Hub page link format, or discussing SEO options.
  • Tier 4: A wiki decision that requires solely bureaucratic/administrative consensus. These discussions occur in private channels where users with bureaucrat and/or administrator rights can vote and ultimately decide. This tier is reserved for key wiki decisions, including but not limited to restructuring pages (ex. Playground becoming Treehouse), site design, administrative tools and functions, and community partnerships.

Voting Eligibility

Voting eligibility requires site editors to have a certain level of productivity in order to participate in votes affecting the wiki and its community. Users who do not meet the eligibilty requirements will have any votes they cast stricken from the record by Staff members. Votes by any users whose accounts are younger than three (3) months, have fewer than seventy-five (75) valid edits (as defined below) or who are using sockpuppet accounts will not be counted.

  • In order to be eligible to vote, a user account must be at least three (3) months old and must have made at least seventy-five (75) constructive edits. Edits to userpages, talk pages or sandboxes do not count, nor do automated edits or edits that have been reverted or undone.
  • A user who is blocked is also not allowed to cast votes for the entire duration of their block.

No Consensus

  • If the outcome is inconclusive, the discussion and/or election is closed as a no consensus and the status quo is retained.
Advertisement