Rosetta Code:Village Pump/Task creation process discussion: Difference between revisions

Undo revision 165652 by 218.108.170.168 (talk) Removed Vandalism & blocked Vandal.
(→‎New issue, if it is an issue: about how the history is)
(Undo revision 165652 by 218.108.170.168 (talk) Removed Vandalism & blocked Vandal.)
 
(6 intermediate revisions by 4 users not shown)
Line 1:
{{Vptopic
|topic=Task creation process discussion
|summary=Question on what kinds of restrictions should be applied to creation of tasks
}}
===Many tasks versus many languages===
The new [[J]] and [[Python]] contributors are creating lots of new tasks in preference to solving existing tasks. Should we be providing guidance on the types of tasks suitable for Rosetta Code? Here are my ideas, feel free to contradict.
Line 44 ⟶ 48:
::Hm, ... could it be done (with efforts :( ) the following way? Adding ''hidden'' templates to tasks, like placeholders for all RC-known languages... when a user adds a language, ''automatically'' the template is superseded by the header|lang template... or the user ''simply'' must remove it by hand... Then the finding of a task unimplemented in the language X will be the same as the finding of a task implemented in the language X (Solutions by Language)... but I don't know the details of running a wiki, so maybe it is not a good idea...? --[[User:ShinTakezou|ShinTakezou]] 23:28, 8 December 2008 (UTC)
:::I'd like an automatic solution. Giving users too many instructions for adding an example may discourage it. I really think a bot is the best way. --[[User:Mwn3d|Mwn3d]] 02:19, 9 December 2008 (UTC)
: Well, the feature existed for [[User:ImplSearchBot|a few months]] this year. Needs to be replaced. --[[User:Short Circuit|Michael Mol]] 17:45, 13 September 2009 (UTC)
 
 
===New issue, if it is an issue===
Anonymous user