Motivation
There are so many ways to improve Botcha module! Some of them are just exercises for novice, some are hard enough. We should decrease a barrier to entry if we want to attract more developers.
So let's do it this way: let's turn each @todo tag in the code into a link to an appropriate issue. See for example how it was done:
http://drupalcode.org/project/botcha.git/blob/refs/heads/7.x-3.x:/botcha...
http://drupalcode.org/project/botcha.git/blob/refs/heads/7.x-3.x:/contro...
or even just
http://drupalcode.org/project/botcha.git?a=search&h=refs%2Fheads%2F7.x-3...
or
http://drupalcode.org/project/botcha.git?a=search&h=refs%2Fheads%2F7.x-3...
Creating an issue for each @todo gives these opportunities:

  • Public discussion and "double-check" (community verification) of each decision (like in extreme programming paradigm)
  • Could attract interested people from elsewhere (Google searching, drupal.org linkings, drupal.org groups or else)
  • Simpletest-bot for each patch attached (which, of course, is not available for each task in @todo-list)
  • Definitely decreasing a barrier to entry