The API documentation is organized by file/library, which makes sense, but I'm not sure how easy that is for people to understand. Should we have an overview of how the code is organized so that someone new to the project knows what to look for where? E.g. mailing list crawling is done within these 4 files, archives and analysis is in these, these files were experimental and aren't regularly used, etc.
322 - Contributor guidelines. Should tell people where to put contributions.
498 - Visualization code is currently spread ad hoc throughout the module. If it were better organized, it would be easier to describe the organization