or, scratching the itch. I decided the best thing I can do to help ClanLib at this point was to volunteer to do documentation. Reference documentation for the API, classes, functions, etc. to tutorials, and F.A.Q.'s. One of the things I want to do is, in developing this documentation, read over all the source code so I really understand what it is doing. Then I will be in a position to do more extensive testing, debugging, or even working with the developers to add new features. As well as explaining the "why" behind the system to make it easier for both developers who use clanlib and developers who work on clanlib. At least that is what I imagine at this point. I just don't get the feeling that the current developers do everything with the most attention to detail, and this seems like a way to go over the architecture with a fine tooth comb and find the boring details that they may have missed in the code because it works "good enough" for themselves. Documentation is also one of the major weak points of clanlib now.