Template talk:Proposal outcome
(First topic)[edit]
Should we add a parameter for appeals (and other things along those lines)? The MarioWiki:Appeals page looks awfully unprofessional with the old Comic Sans font that doesn't have the template. 
J-Luigi (talk) 20:19, 24 May 2016 (EDT)
- No. We should make a new template if we create a template for appeal outcomes. In fact, this discussion should be moved to MarioWiki talk:Appeals. --Wildgoosespeeder (talk) (Stats - Contribs) 20:30, 24 May 2016 (EDT)
- You could use the "color" version of the template instead, like "Proposal outcome|green|reminder overturned"
Xiahou Ba(the Nasty Warrior) 20:31, 24 May 2016 (EDT)
Remove typeface property from this template[edit]
|
This talk page proposal has already been settled. Please do not edit this section or its subsections. If you wish to discuss the article, please do so in a new section below the proposal. |
Keep Verdana 1-4
Currently, this template uses the Verdana typeface (or font) set by font-family property, which appears to the chosen by some people in this discussion, but I don't think it makes sense to forcibly use it on this (and possibly other templates) when both the MonoBook and Vector skins defaults the body text to sans-serif, which would be the sans-serif typeface set in the browser (usually defaults to Arial), anyway.[n 1] On most mobile devices, this property also has no effect (both in default mobile view and desktop view) as they don't have Verdana typeface available and thus falls back to the sans-serif typeface. This proposal thus would decide whether to change the font-family property to sans-serif for consistency across body texts.
- ^ I am aware that most of MonoBook's user interface does use Verdana, but this still look out of place compared to body texts.
Proposer: Stache (talk)
Deadline: March 6, 2025, 23:59 GMT
Change the font-family property to sans-serif (support)[edit]
- Super Mario RPG (talk) The current font looks awful.
Keep Verdana (oppose)[edit]
- Nintendo101 (talk) I honestly like the way it looks as is. Sometimes inconsistent formats are a good thing because they are subtly more eye-catching.
- Power Flotzo (talk) Per N101. This feels like change for the sake of change.
- Camwoodstock (talk) The difference in font is fine enough as-is; plus, as N101 points out, it does serve a (rather unintentional) role of clearly denoting that it's the proposal outcome.
- Technetium (talk) Per all.
Comments[edit]
what benefit would this change have, besides a bit more font consistency? — 
eviemaybe (talk / contributions) 11:42, February 20, 2025 (EST)
- Per Evie. I feel like it doesn't matter that much in the grand scheme of things. The Proposal outcome template is supposed to stand out and easily convey... well, the outcome of an ended proposal, not necessarily to be consistent with the rest of the body text.
Also, I would like if you set out an example of how the template's text would look like with your proposed changes applied (like, with a screenshot or something).
rend (talk) (edits) 12:07, February 20, 2025 (EST)
Show approval rate when needed[edit]
The vote summary is not always sufficient to determine whether a proposal can be settled since it does not take into account the number of unique voters, which can be smaller that the total number of votes. For example, a 4-3-0 vote outcome could mean that consensus has not been reached (4 out of 7 voters = 57.1% approval, less than the 60% threshold when vote margin is less than 3), but if a given voter has voted for the first two options, then consensus is reached (4 out of 6 voters = 66.7% approval).
To avoid confusion, I think we should add template parameters (e.g., approvers and total_voters) for such cases where whether consensus is reached depends on the approval rate.
{{proposal outcome|passed|4-3-0|split|approvers=4|total_voters=6}}
This could be displayed like this:
split 4-3-0
4 out of 6 voters (66.7%) approve the first place option.
