To make it easier for potential contributers, a developer's guide is in order. We have some good isntructions for the fundamentals (i.e how to get access to source code and provide patches) on beaker-project.org. However, more in depth analysis of our source code would be beneficial.
Maybe a good first step would be to write a detailed description of all the pieces of Beaker and how they fit together. This needn't be just for developers though, it's important for admins and interesting for users as well. Maybe then all you would need to do for developers is point out how the source code maps to the various pieces of Beaker. We currently have these two related but completely separate sections: http://beaker-project.org/guide/Introduction-Beaker_Overview.html http://beaker-project.org/guide/Administration-Beaker_Architecture.html They look like they could both do with expanding and updating.
This has been released. http://beaker-project.org/dev-guide.html