Hey Robert; what sort of areas would you like to be involved in?

I’d like to work on the compiler, as it has the highest density of problem domains that interest me (which are those domains I listed on the internals forum). Are there tasks that I can do that would also allow me to get familiar with the rustc code base and development process? I would like to eventually work up to the point of being able to participate in conversations about the type system, type/lifetime inference and other semantic analysis issues, and the algorithm design that services those aspects of the compiler. But right now I think I am at the software engineering equivalent of, “sweep the floors,” rather than, “design the building,” by which I mean I don’t know enough to be of use in major infrastructure conversations yet.

Can anyone please suggest a beginner roadmapShoud I start with documentation and testing or should i simply jump to development?

Which area should i familliarize
myself first?

Hi! I'm new to Rust. What really excites me about the language is its applications to embedded systems as an alternative to C / C++.

I'd like to get started with some basic contributions: documentation, testing, first timers' pull-requests, etc.
This will be my first time really interacting with an open-source community, so I want to learn the right way.

After I get comfortable, I'd really like to help out on the embedded side of things.
If someone could refer me to a mentor in that area, that'd be awesome!