Rosetta Code:TODO

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 the "needs-review" and "incorrect" examples on the String length and Bitwise operations pages and make sure they're correct.
• Copy/modify code from Loop Structures to pages in Category:Iteration.
• Change all code examples and creation guides to use <lang> instead of tt or pre. GeshiCodeTag will now quietly wrap those in HTML pre blocks. Use a standardized language ID for each language. I'll alias them to existing or newly supported language IDs as appropriate and possible.
• Add features and paradigms to all language pages using parameters in Template:Language and Template:Language programming paradigm
  • Add features according to the Language Comparison Table where applicable
  • Add features and paradigms to the LCT where missing and known
• Move information from Category:Programming Paradigms to their appropriate pages in Category:Programming paradigm, or merge these categories in some other appropriate way.

Automation Candidates

Any process with a straightforward procedure likely has a programmatic solution, or at least a means to be accelerated programmatically, either via clever usages of templates, page transclusion, a MediaWiki extension, JavaScript, or a bot.

• Anything in the language comparison table should be reflected in the relevant language page. Additionally, everything in Category:Programming_Languages should be reflected in the LCT.

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.)