Rosetta Code:Add a Task: Difference between revisions

Line 2:

==Prerequisites==

===Draft vs non-draft===

Not all tasks are immediately ready to be thrown at the casual Rosetta Code participant. Some need a review or draft phase before they're in good shape.

* For a non-draft task, one would use [[Template:Task]] by putting '''[[Template:Task|<nowiki>{{task}}</nowiki>]]''' at the top of the page.

⚫

* If there is some question on the general suitability of the task then create a draft task and discuss the reason for it being a draft in the talk page. ~~<br>~~ This will warn potential contributors that there may be substantial changes in the task description whilst still in draft status.~~<br> Reasons for draft status might include, but not be limited to:~~

* To note that a task is a draft, use [[Template:draft task]], by putting '''[[Template:draft task|<nowiki>{{draft task}}</nowiki>]]''' at the top, rather than '''<nowiki>{{{task}}}</nowiki>'''.

⚫

** A task that is too large.

⚫

** A task that is too general and so hard to compare implementations.

⚫

It's up to you to decide which you start with, but another community member may choose to change your created task to a draft. If there is some question on the general suitability of the task then create a draft task and discuss the reason for it being a draft in the talk page. This will warn potential contributors that there may be substantial changes in the task description whilst still in draft status.

⚫

** A task that may be too specific and so only implementable by a single language.

** ...

'''Reasons for draft status might include, but not be limited to:'''

⚫

* A task that is too large.

⚫

* A task that is too general and so hard to compare implementations.

⚫

* A task that may be too specific and so only implementable by a single language.

===Task focus inclusion===