Rosetta Code:TODO: Difference between revisions
(problem) |
(Ideal minimum penetration) |
||
| Line 11: | Line 11: | ||
* Go through the "needs-review" examples on the [[String length]] page and make sure they're correct. |
* Go through the "needs-review" examples on the [[String length]] page and make sure they're correct. |
||
==Ideal Minimum Penetration== |
|||
* Put together a list of the task pages with five or fewer languages |
|||
===Tasks=== |
|||
* Put together a list of the task pages with ten or fewer languages |
|||
Tasks should have a minimum language penetration of 25% of the languages on Rosetta Code. That is to say, if there are 100 [[:Category:Solutions by Programming Language|languages]] on Rosetta Code, a task should have examples in at least 25 languages. An exception to this would be if there are fewer than 25 languages capable of implementing the task. |
|||
* Put together a list of languages used in twenty or fewer tasks |
|||
** I gotta say, I don't think categories are the right tool for this. It just creates a maintenance headache. These should be done via database queries, such as those used in [[Special:Mostlinkedcategories]] and [[Special:Mostcategories]]. --[[User:IanOsgood|IanOsgood]] 08:56, 22 February 2008 (MST) |
|||
===Languages=== |
|||
::The problem is that there's nothing in the database (apart from page content) that identifies how many languages are used in a task. Yes, each page is in each language's category, but it may also be in categories for libraries or a Solutions by Programming Task subcategory --[[User:Short Circuit|Short Circuit]] 10:53, 24 February 2008 (MST) |
|||
Languages should have a minimum penetration of 25% of the tasks on Rosetta Code. That is to say, if there are 100 [[:Category:Solutions by Programming Task|tasks]] on Rosetta Code, a language should have examples written for at least 25 tasks. An exception to this would be if there aren't enough tasks in the language's domain for this to be possible. (Though if this is the case, there should be discussion aimed toward introducing tasks that fall in a given language's domain.) |
|||
[[Category:Maintenance]] |
|||
Revision as of 03:23, 26 February 2008
Here's a list of "Someone needs to..." items. If you're looking for something to do, you can always do something on this list.
TODO
- Look through the stubs, and research and fill in useful information. Cite sources as needed, of course. Remove stub template when done with each page.
- Comb through the suggestions on the task request page and put a few together. Or drop some into a "Questionable" category, so they can be debated.
- Merge similar tasks together:
- Singly-linked list from Singly-Linked List (element), Singly-Linked List (element insertion), Singly-Linked List (traversal)
- Doubly-linked list from Doubly-Linked List (element), Doubly-Linked List (element insertion)
- Basic array operations from Creating an Array, Assigning Values to an Array, Retrieving an Element of an Array
- Go through language pages and add external links pointing to relevant page(s) in the HOPL.
- Go through the "needs-review" examples on the String length page and make sure they're correct.
Ideal Minimum Penetration
Tasks
Tasks should have a minimum language penetration of 25% of the languages on Rosetta Code. That is to say, if there are 100 languages on Rosetta Code, a task should have examples in at least 25 languages. An exception to this would be if there are fewer than 25 languages capable of implementing the task.
Languages
Languages should have a minimum penetration of 25% of the tasks on Rosetta Code. That is to say, if there are 100 tasks on Rosetta Code, a language should have examples written for at least 25 tasks. An exception to this would be if there aren't enough tasks in the language's domain for this to be possible. (Though if this is the case, there should be discussion aimed toward introducing tasks that fall in a given language's domain.)