Jump to content

Template:Draft proposal/doc: Difference between revisions

From BattleIntelligence
imported>Deadfire
Template Doc Creation
 
m Text replacement - "BattleTechWiki" to "BattleIntelligence"
 
Line 15: Line 15:


== Purpose ==
== Purpose ==
The BTW community roughly follows a set of [[BattleTechWiki:policies and guidelines|official policies and guidelines]] (collectively often referred to simply as "policy"). Pages reflecting policy are written by ordinary editors in the "BattleTechWiki:" [[Help:Namespace|namespace]]. Other editors review these [[:Category:Proposals|proposals]] and edit to improve them and move toward greater [[BattleTechWiki:Consensus|consensus]]. Over time, many things may happen to a proposal – it may be changed substantially, be moved to a new location, become adopted as a policy or guideline, be rejected by the community, be recast as simply a [[Template:Essay|essay]], or fail to sufficiently develop into a viable proposal.
The BTW community roughly follows a set of [[BattleIntelligence:policies and guidelines|official policies and guidelines]] (collectively often referred to simply as "policy"). Pages reflecting policy are written by ordinary editors in the "BattleIntelligence:" [[Help:Namespace|namespace]]. Other editors review these [[:Category:Proposals|proposals]] and edit to improve them and move toward greater [[BattleIntelligence:Consensus|consensus]]. Over time, many things may happen to a proposal – it may be changed substantially, be moved to a new location, become adopted as a policy or guideline, be rejected by the community, be recast as simply a [[Template:Essay|essay]], or fail to sufficiently develop into a viable proposal.


When a proposal is being advanced it is usual to tag the page with {{tlx|Proposed}}. Although a proposal is generally written in advisory tone, it is ''not policy'' until adopted by the community through the consensus-building process, and should not yet be tagged with {{tlx|Policy}} or {{tlx|Guideline}}.
When a proposal is being advanced it is usual to tag the page with {{tlx|Proposed}}. Although a proposal is generally written in advisory tone, it is ''not policy'' until adopted by the community through the consensus-building process, and should not yet be tagged with {{tlx|Policy}} or {{tlx|Guideline}}.


If a proposal is still in the early formative stages and it is desired to gather creative suggestions from others on what purpose and direction such a proposal should have, one may wish to temporarily use the {{tlx|Brainstorming}} header template, and later use {{tlx|Draft proposal}} when these matters are clearer. Once proponents of a proposal are satisfied with the form it has taken and it is desired to move forward to the more intense debate that precedes policy acceptance by the community, {{tlx|Draft proposal}} should be replaced with {{tlx|Proposed}}. This change in status should be advertised so that interested parties have a fair chance to participate before anyone designates the proposal as rejected or adopted as policy. If there is a lack of discussion from the community, the proposal may be tagged with {{tlx|Dormant}}. Usual places to advertise a proposal are the talk pages of relevant other policies and guidelines and of topically connected wikiprojects, and/or our [[BattleTechWiki:Discord|community discord]].  
If a proposal is still in the early formative stages and it is desired to gather creative suggestions from others on what purpose and direction such a proposal should have, one may wish to temporarily use the {{tlx|Brainstorming}} header template, and later use {{tlx|Draft proposal}} when these matters are clearer. Once proponents of a proposal are satisfied with the form it has taken and it is desired to move forward to the more intense debate that precedes policy acceptance by the community, {{tlx|Draft proposal}} should be replaced with {{tlx|Proposed}}. This change in status should be advertised so that interested parties have a fair chance to participate before anyone designates the proposal as rejected or adopted as policy. If there is a lack of discussion from the community, the proposal may be tagged with {{tlx|Dormant}}. Usual places to advertise a proposal are the talk pages of relevant other policies and guidelines and of topically connected wikiprojects, and/or our [[BattleIntelligence:Discord|community discord]].  


== Usage ==
== Usage ==
Line 43: Line 43:
* <code>4          </code>: Same as 1 (for multiple shortcuts)
* <code>4          </code>: Same as 1 (for multiple shortcuts)
* <code>5          </code>: Same as 1 (for multiple shortcuts)
* <code>5          </code>: Same as 1 (for multiple shortcuts)
* <code>type      </code>: The dealio of what kind of thing it's being proposed for. The default is "[[BattleTechWiki:Policies and guidelines|policy, guideline, or process]]".
* <code>type      </code>: The dealio of what kind of thing it's being proposed for. The default is "[[BattleIntelligence:Policies and guidelines|policy, guideline, or process]]".
* <code>discussion </code>: Link to specific discussion. Default is to link to the page's talk page (i.e. if your proposal is at [[Example|BattleTechWiki:Meowing guidelines]], it will link to [[Example|BattleTechWiki talk:Meowing guidelines]]), but it can be set up to link elsewhere, like [[Example|Module talk:Meowing]].
* <code>discussion </code>: Link to specific discussion. Default is to link to the page's talk page (i.e. if your proposal is at [[Example|BattleIntelligence:Meowing guidelines]], it will link to [[Example|BattleIntelligence talk:Meowing guidelines]]), but it can be set up to link elsewhere, like [[Example|Module talk:Meowing]].
* <code>section    </code>: Section link. For example, if the discussion is at [[Example|Module talk:Meowing#We need guidelines for when to meow in articles]].  
* <code>section    </code>: Section link. For example, if the discussion is at [[Example|Module talk:Meowing#We need guidelines for when to meow in articles]].  
* <code>category  </code>: Replace [[:Category:Draft proposals|Category:Draft proposals]] with something else, like [[Example|Category:Draft proposals on redirecting]].
* <code>category  </code>: Replace [[:Category:Draft proposals|Category:Draft proposals]] with something else, like [[Example|Category:Draft proposals on redirecting]].
Line 51: Line 51:


== See also ==
== See also ==
* [[BattleTechWiki:Policy writing is hard]]
* [[BattleIntelligence:Policy writing is hard]]
* [[:Category:Draft proposals]]
* [[:Category:Draft proposals]]
* [[:Category:Header templates]]
* [[:Category:Header templates]]

Latest revision as of 00:03, 1 May 2025

Usage

{{Proposal}} or {{Draft proposal}}

This adds pages to Category:Proposals or Category:Draft proposals if {{Draft proposal}} is used. Categorization of drafts can be suppressed with the |categories=no parameter.

Purpose

The BTW community roughly follows a set of official policies and guidelines (collectively often referred to simply as "policy"). Pages reflecting policy are written by ordinary editors in the "BattleIntelligence:" namespace. Other editors review these proposals and edit to improve them and move toward greater consensus. Over time, many things may happen to a proposal – it may be changed substantially, be moved to a new location, become adopted as a policy or guideline, be rejected by the community, be recast as simply a essay, or fail to sufficiently develop into a viable proposal.

When a proposal is being advanced it is usual to tag the page with {{Proposed}}. Although a proposal is generally written in advisory tone, it is not policy until adopted by the community through the consensus-building process, and should not yet be tagged with {{Policy}} or {{Guideline}}.

If a proposal is still in the early formative stages and it is desired to gather creative suggestions from others on what purpose and direction such a proposal should have, one may wish to temporarily use the {{Brainstorming}} header template, and later use {{Draft proposal}} when these matters are clearer. Once proponents of a proposal are satisfied with the form it has taken and it is desired to move forward to the more intense debate that precedes policy acceptance by the community, {{Draft proposal}} should be replaced with {{Proposed}}. This change in status should be advertised so that interested parties have a fair chance to participate before anyone designates the proposal as rejected or adopted as policy. If there is a lack of discussion from the community, the proposal may be tagged with {{Dormant}}. Usual places to advertise a proposal are the talk pages of relevant other policies and guidelines and of topically connected wikiprojects, and/or our community discord.

Usage

{{Draft proposal
 | 1          = 
 | 2          = 
 | 3          = 
 | 4          = 
 | 5          = 
 | type       = 
 | discussion = 
 | section    = 
 | categories = 
 | category   = 
 | nocat      = 
}}

The parameters are as follows:

See also