Revision as of 06:03, 27 October 2005

start of template

Formal proposals are meant for large changes with implementation side-effects, or changes which may be controversial

test proposal

text of what's being proposed

why this is being proposed

any technical background, implementation suggestions, projected complications, etc

(... variable assignments can contain a certain amount of wiki-text (not wiki-tables, aw). sub-headings are okay...)

end of template

Edit this page to see how the template is used here.

Another option is to use {{subst:distro-propsal | title=test2 | [ more arguments ] }} which looks like this:

Formal proposals are meant for large changes with implementation side-effects, or changes which may be controversial

{{{content}}}

{{{benefits}}}

{{{implementation}}}

@@ Line 1: / Line 1: @@
+start of template
+----
 {{distro-proposal | <!-- comments to explain? -->
 title = test proposal
@@ Line 14: / Line 16: @@
 === junk ===
 }}
+----
+end of template
+----
@@ Line 19: / Line 24: @@
 [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} Edit this page] to see how the template is used here.
-<!--Another option is to use {{subst:distro-propsal | [ arguments ]}}.-->
+Another option is to use
+<code>{{subst:distro-propsal | title=test2 | [ more arguments ] }}</code>
+which looks like this:
+''Formal proposals are meant for large changes with implementation side-effects, or changes which may be controversial''
+=test2=
+== Proposal Content ==
+{{{content}}}
+== Potential Benefits & Reasons For Proposal ==
+{{{benefits}}}
+== Implementation Strategy: Issues, Side-Effects, etcetera ==
+{{{implementation}}}
+[[Category:Distro]]