API module developers

http://lists.drupal.org/pipermail/development/2008-May/029761.html clearly demonstrates that documenting all of contributions on api.drupal.org would be good.

Add concept of projects every project has its own code and set of branches. This should be clear in both the database and UI.

Programmatically manage branch checkouts managing a lot of CVS checkouts would be tedious.

There have been various attempts at upgrading api.module to Drupal 6.x. However, it is a complex module, and until now, none of the attempts has yielded satisfying results. We now have the situation that there are 16 patches in the patch queue, none of them thoroughly reviewed, leaving anyone trying to help on this issue without much help and probably causing her to start from scratch again (at least thats what happened to me). Thats why i think we need to break down this issue into smaller tasks. Smaller tasks can more easily be solved, tested, and reviewed. After a subtask is finished, it can be commited to CVS HEAD, giving anyone else a solid starting point for further tasks, without worrying about the base she is working on.