Here is a very tempting suggestion, which might benefit all of us in the long run, but will require some group effort :) As we all know, though lots of efforts have been made to document IMP, getting started on IMP development or usage is (quite naturally) still somewhat far from obvious (missing or outdated documentation or examples, no tutorials etc.). So - the idea is that if we team up, we can improve the documentation and write tutorials in relatively small effort, benefiting new users and developers, and surely also old ones. We can then have peer-reviewing of the resulting documentation (e.g., one team checking the documentation / tutorials written by another team).

* Other teams will validate existing example codes, add missing example codes, and most important, write friendly tutorials on how to accomplish common IMP tasks (both development, e.g., "how to write new code for Monte-Carlo simulation with restraints", and usage e.g. "how to dock from EM")

* Perhaps one team can also go over some key classes and improve their code documentation, especially in the core / kernel / base / atom modules.