Rosetta Code talk:Add a Task: Difference between revisions

From Rosetta Code
Content added Content deleted
(Drafting this page.)
 
No edit summary
Line 3: Line 3:
*Go through our existing set of tasks and use this page as a benchmark for gauging task quality. If the task seems of good quality (i.e. matches the prerequisites), despite not matching this page well, then the page likely requires modification.
*Go through our existing set of tasks and use this page as a benchmark for gauging task quality. If the task seems of good quality (i.e. matches the prerequisites), despite not matching this page well, then the page likely requires modification.
*Build a list (somewhere, anywhere, wikicode or semantic query, be as practical or creative as necessary) where we can see our existing task set and see how well the task description matches this page. --[[User:Short Circuit|Michael Mol]] 17:41, 20 September 2010 (UTC)
*Build a list (somewhere, anywhere, wikicode or semantic query, be as practical or creative as necessary) where we can see our existing task set and see how well the task description matches this page. --[[User:Short Circuit|Michael Mol]] 17:41, 20 September 2010 (UTC)

I certainly like the requirement for an implementation. It almost always makes things much easier for other implementors if they can study a working example. Perhaps the requirement for graduating a task from draft status should be taken to be multiple implementations of it and a consensus that the task is clear enough (typically formed by having multiple implementations that people can agree are all correct). –[[User:Dkf|Donal Fellows]] 21:06, 21 September 2010 (UTC)

Revision as of 21:06, 21 September 2010

I've been asked numerous times about how to create a task. I've never had a good answer. This page represents a draft of my best idea of it.

  • Please examine, edit, refine, review and debate it.
  • Go through our existing set of tasks and use this page as a benchmark for gauging task quality. If the task seems of good quality (i.e. matches the prerequisites), despite not matching this page well, then the page likely requires modification.
  • Build a list (somewhere, anywhere, wikicode or semantic query, be as practical or creative as necessary) where we can see our existing task set and see how well the task description matches this page. --Michael Mol 17:41, 20 September 2010 (UTC)

I certainly like the requirement for an implementation. It almost always makes things much easier for other implementors if they can study a working example. Perhaps the requirement for graduating a task from draft status should be taken to be multiple implementations of it and a consensus that the task is clear enough (typically formed by having multiple implementations that people can agree are all correct). –Donal Fellows 21:06, 21 September 2010 (UTC)