Jump to content

Template:Failed proposal/doc: Difference between revisions

From BattleIntelligence
imported>Deadfire
m Text replacement - "BattleTechWiki:Template index/BattleTechWiki namespace" to "BattleTechWiki:Template index/Project namespaces"
 
m Text replacement - "BattleTechWiki" to "BattleIntelligence"
 
Line 8: Line 8:


== When to use ==
== When to use ==
:''See also: [[BattleTechWiki:Policies, Essays, Procedures, & Projects#failed|BattleTechWiki:Policies and guidelines - Failed proposals]]''
:''See also: [[BattleIntelligence:Policies, Essays, Procedures, & Projects#failed|BattleIntelligence:Policies and guidelines - Failed proposals]]''
A failed proposal is one for which consensus for acceptance has not developed after a reasonable time period. Consensus need not be fully opposed; if consensus is neutral or unclear on the issue and unlikely to improve, the proposal has likewise failed.
A failed proposal is one for which consensus for acceptance has not developed after a reasonable time period. Consensus need not be fully opposed; if consensus is neutral or unclear on the issue and unlikely to improve, the proposal has likewise failed.


Line 33: Line 33:
== See also ==
== See also ==


* [[BattleTechWiki:How to create policy]]
* [[BattleIntelligence:How to create policy]]
* [[:Category:Failed proposals]]
* [[:Category:Failed proposals]]
* [[BattleTechWiki:Template index/Project namespaces|Template index/BattleTechWiki namespace]] for related [[:Category:Header templates|Header templates]]
* [[BattleIntelligence:Template index/Project namespaces|Template index/BattleIntelligence namespace]] for related [[:Category:Header templates|Header templates]]


<includeonly>{{Sandbox other||
<includeonly>{{Sandbox other||

Latest revision as of 00:16, 1 May 2025

To include a shortcut, pass a parameter: {{Failed proposal|BTW:SHORT}}.

Failed proposals are categorized in Category:Failed proposals.

When adding this template, it is recommended to provide links to any new proposals that superseded it, if known.

When to use

See also: BattleIntelligence:Policies and guidelines - Failed proposals

A failed proposal is one for which consensus for acceptance has not developed after a reasonable time period. Consensus need not be fully opposed; if consensus is neutral or unclear on the issue and unlikely to improve, the proposal has likewise failed.

When not to use

It is not necessary or desirable to put this template on every page that has undergone a formal BTW:PROPOSAL. Sometimes the proposal process identifies a better approach (e.g., that an informative and practical page should be a Help: page instead of a {{Guideline}}); these are in no way "failures" and tagging them as such might discourage editors from benefiting from the information on the page. In other cases, such as with the, editors prefer to retain an {{essay}} tag.

If you feel a need to document the existence of a prior proposal, consider putting a generic {{tmbox}} note on the talk page.

How to use

{{Failed|shortcut}}

The first unnamed parameter (or named as |1=) is optional. If supplied, it displays as a link to the appropriate shortcut page for the proposal. (Note that this is not automatic; MediaWiki cannot determine the shortcut from the page itself. You need to discover or create the shortcut yourself.) Please do not create shortcuts for failed proposals; intelligible shortcuts are a finite resource. In fact, shortcuts may be usurped from long-failed proposals to redirect to something active.

The |date= parameter can be used to add the date at which the page was tagged as failed, or at which a formal BTW:PROPOSAL process did not accept the proposal. It accepts any valid date format.

A |result= AKA |reason= parameter can also be used to add free-form text explaining the failure (e.g. linking to a BTW:PROPOSAL discussion, quoting from an RfC summary statement, etc.). This should be kept short (e.g., a concise sentence or two), since this is a banner template. The content of this parameter will be auto-formatted as a separate paragraph below the default text (and thus should not itself contain paragraph markup).

Redirects

See also