Difference between revisions of "Lylat Wiki:Draft Policies"

m
Text replacement - "{{tl" to "{{t"
(removed mention of template)
m (Text replacement - "{{tl" to "{{t")
Line 14: Line 14:
Launch a discussion at [[Lylat Wiki:Starting a Policy Discussion]]. In it, explain what you think the policy will be called, it's scope, intention and any initial details you have.  
Launch a discussion at [[Lylat Wiki:Starting a Policy Discussion]]. In it, explain what you think the policy will be called, it's scope, intention and any initial details you have.  


If you can prove to community that it might be worth something to have, then please launch it as a new page (with <code>Lylat Wiki:</code> before its title) and stick all the details you can in it. At the top of the page, place {{tl|draft-policy}}, in order to ensure people know it is currently a draft. Save, and continue to step 2.  
If you can prove to community that it might be worth something to have, then please launch it as a new page (with <code>Lylat Wiki:</code> before its title) and stick all the details you can in it. At the top of the page, place {{t|draft-policy}}, in order to ensure people know it is currently a draft. Save, and continue to step 2.  


=== Step 2:Getting Community Feed Back ===
=== Step 2:Getting Community Feed Back ===
Once you have launched the page, talking about the policy now moves from the page under [[Lylat Wiki:Starting a Policy Discussion]] to the new page's respective discussion page. Be sure the old conversation is marked as closed, and include a link to the new discussion page. It's time to improve the draft.  
Once you have launched the page, talking about the policy now moves from the page under [[Lylat Wiki:Starting a Policy Discussion]] to the new page's respective discussion page. Be sure the old conversation is marked as closed, and include a link to the new discussion page. It's time to improve the draft.  


Using feedback given to you on the discussion page, cultivate the policy to include anything you think would be useful in elaborating the policy's purpose and scope, but don't include anything that is too far away from the topic to be useful. Encourage others to be contributors to the draft if you feel comfortable with the idea, otherwise mark the page with {{tl|please-stick-to-the-discussions}} ('''NOTE''': this is only to be used on draft policies, not on any articles).   
Using feedback given to you on the discussion page, cultivate the policy to include anything you think would be useful in elaborating the policy's purpose and scope, but don't include anything that is too far away from the topic to be useful. Encourage others to be contributors to the draft if you feel comfortable with the idea, otherwise mark the page with {{t|please-stick-to-the-discussions}} ('''NOTE''': this is only to be used on draft policies, not on any articles).   


Once the community has deiced the policy is good, alert a level [[Lylat Wiki:Administration#Level 0|Level 0]] to inform them of this. If they approve, then congratulations your draft policy no longer being a draft; it's a full policy. Now, continue on to Step 3 to finalize the policy, and to make sure it is known around the wiki.  
Once the community has deiced the policy is good, alert a level [[Lylat Wiki:Administration#Level 0|Level 0]] to inform them of this. If they approve, then congratulations your draft policy no longer being a draft; it's a full policy. Now, continue on to Step 3 to finalize the policy, and to make sure it is known around the wiki.  


=== Step 3:Finalizing The Policy ===
=== Step 3:Finalizing The Policy ===
When the policy has been approved, replace {{tl|draft-policy}} with {{tl|approved-policy}}, and mark it on any related discussions. This doesn't mean that the policy can't be talked about more; it just we need to know what conversation(s) happened before, during and after it's approval.  
When the policy has been approved, replace {{t|draft-policy}} with {{t|approved-policy}}, and mark it on any related discussions. This doesn't mean that the policy can't be talked about more; it just we need to know what conversation(s) happened before, during and after it's approval.  


In order to finalize the policy, it needs to get known around the wiki, be easily [[Lylat Wiki:Accessible|Accessible]] and [[Lylat Wiki:Findability|findable]]. But how does this get done?
In order to finalize the policy, it needs to get known around the wiki, be easily [[Lylat Wiki:Accessible|Accessible]] and [[Lylat Wiki:Findability|findable]]. But how does this get done?
Line 31: Line 31:


== Shortcuts ==
== Shortcuts ==
Each shortcut is a small word, symbol and/or letter combination template that automatically places a link to the page through redirects. So for example, this page is called Lylat Wiki:Draft Policies. To link to it, you would usually type {{link|Lylat Wiki:Draft Policies}}. But with a shortcut set up, all you need to type is {{tl|LW:Draft}}, and it will automatically but the needed text in for you.  
Each shortcut is a small word, symbol and/or letter combination template that automatically places a link to the page through redirects. So for example, this page is called Lylat Wiki:Draft Policies. To link to it, you would usually type {{link|Lylat Wiki:Draft Policies}}. But with a shortcut set up, all you need to type is {{t|LW:Draft}}, and it will automatically but the needed text in for you.  


Please note, just like each policy page starts with <code>Lylat Wiki:</code> Each shortcut needs to start with <code>LW:</code>.
Please note, just like each policy page starts with <code>Lylat Wiki:</code> Each shortcut needs to start with <code>LW:</code>.
8,161

edits