[gchp]

This is great!

Something I'd love to see is an overview of what parts of the source tree are responsible for what. As a new contributor to projects, that's the part I find takes the longest. Figuring out what modules do the things that I want to work on.

The guts of servo seems to be the the "components" directory. Is there a place that gives some information on each of the components in there?

[larsberg]

I did some training at our last Mozilla workweek that covered the major areas of Servo and had some simple exercises to get you started in each of them:

https://drive.google.com/file/d/0B9-EBhw4XiWEOWFfc0NiUkk5Tjg...

Servo has polyrepo style (many separate source repositories), as opposed to the monorepo style of other browsers. So, it's not just the `components` directory, but many of the ~140 other Cargo crates (https://crates.io/) and raw GitHub packages that come together to form Servo. I have a "deliverable" for Q4 to improve our documentation situation and explain how it all is put together, though this gist is an awesome start!

[lastontheboat]

https://github.com/servo/servo/blob/master/ORGANIZATION.md has a REALLY high-level overview.