Rosetta Code:Village Pump/Old draft tasks: Difference between revisions
Rosetta Code:Village Pump/Old draft tasks (view source)
Revision as of 01:21, 12 May 2011
, 13 years agoCustodian roles and task modifications
(Some specifics) |
(Custodian roles and task modifications) |
||
Line 22:
:::: Some draft tasks just have big problems. For example, [[Loading animated 3D data|this]] is a really tough one to do without a very specialized support library, and [[VList|this]] doesn't have a real implementation in any language (an interface spec is usually not a solution, and certainly isn't for a data structure task). OTOH, I added undone drafts to the template report of things not done for each language to make it easier for people to step up and provide implementations; that's generally the best way of helping a task make it to full task (even if in some cases that's not all that's required). –[[User:Dkf|Donal Fellows]] 23:36, 11 May 2011 (UTC)
What if we were to add a 'custodian' role to draft tasks, where someone who sees a draft without a custodian can be the go-to guy for clarifying the task idea into something that can be implemented or built upon? Once the task graduates to full-task status, it falls under the more general behaviors we already have. As for things like [[VList]] and [[Loading animated 3D data]], perhaps those tasks should be modified such that they're more achievable or implementable. (VList might also include a "demonstrate its use" section, while the 3d animated data task might not be so specific to require the use of Smil and X3D, but go on to show how to proceed along the individual model "frames") --[[User:Short Circuit|Michael Mol]] 01:21, 12 May 2011 (UTC)
| |||