My (very subjective and not at all scientific) advice is to take it one thing at a time. Find a ticket that looks like a low hanging fruit, fix it, and now you understand what that part of the code is doing. After a few months of this, you'll find yourself with a decent understanding of the project as a whole.

I would also try to push hard for more/better documentation along the way.