Some tips for getting to know a new software project
Learning how a large software project works is essential if you want to contribute to it. However, when faced with the task it can be hard to know where to start. Mitchell Hashimoto has written an article with some useful tips on how to do this:
These are great tips, both for working on open and closed source projects. Does anybody have any others?