This codebase is documented and well structured. I would simply being by tackling the issues on github first and sending pull requests. No need to take over it

This codebase is documented and well structured. I would simply being by tackling the issues on github first and sending pull requests. No need to take over it right away. After you feel comfortable reading the code and knowing where is what, you can ask to become a maintainer. I'd try to fix it using the same style used in the codebase. This way anybody else reading, maintaining ,or using it won't have to make sense of the new style. Pay attention to how each method is defined. They are very readable. Very few traces of complex one line statements. Most importantly, be patient. You won't be any good with it in less than 2 weeks of constant tinkering. Good luck.