Rosetta Code talk:Village Pump/Suggest a programming task: Difference between revisions

Content added Content deleted

Inline

Revision as of 19:01, 24 December 2007

Get moving on these

Can we get moving on some of these? --Short Circuit 23:00, 7 November 2007 (MST)

Task guidelines?

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.

Rosetta Code is about language comparison. We should encourage solving existing tasks in preference to creating new tasks.
We encourage contribution from the public in their free time. If we choose tasks that are too large or difficult, then we are likely to only get a few solutions. Tasks should be chosen which can be implemented succinctly in a variety of languages.
Rosetta Code started mostly with trivial tasks designed to demonstrate language features. Do we want to retain that focus? Are there any feature areas we forgot?
The more tasks we have, the more each individual task gets lost within Category:Solutions by Programming Task. We can solve this either by adding structure (subcategories) or restricting the number of tasks (merging and rejecting).
Duplication should be avoided. If two tasks are demonstrating the same language features, then one should be cut.

I think it would be fine to restrict our focus considering that there are other sites, like Literate Programs, for showing off public code. --IanOsgood 12:01, 24 December 2007 (MST)

@@ Line 1: / Line 1: @@
 ==Get moving on these==
 Can we get moving on some of these? --[[User:Short Circuit|Short Circuit]] 23:00, 7 November 2007 (MST)
+== Task guidelines? ==
+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.
+* Rosetta Code is about language ''comparison''. We should encourage solving existing tasks in preference to creating new tasks.
+* We encourage contribution from the public in their free time. If we choose tasks that are too large or difficult, then we are likely to only get a few solutions. Tasks should be chosen which can be implemented succinctly in a variety of languages.
+* Rosetta Code started mostly with trivial tasks designed to demonstrate language features. Do we want to retain that focus? Are there any feature areas we forgot?
+* The more tasks we have, the more each individual task gets lost within [[:Category:Solutions by Programming Task]]. We can solve this either by adding structure (subcategories) or restricting the number of tasks (merging and rejecting).
+* Duplication should be avoided. If two tasks are demonstrating the same language features, then one should be cut.
+I think it would be fine to restrict our focus considering that there are [[Help:Similar Sites|other sites]], like Literate Programs, for showing off public code. --[[User:IanOsgood|IanOsgood]] 12:01, 24 December 2007 (MST)