I wish! All I can contribute is expressing my concerns.
Don't want to be impolite, don't want to complain. Just express my concerns.
I find it quite frustrating that open source/current company projects have no or little documentation. Even for a 12 days project it is frustrating. It is just good habit that documentation is as important as code. I like to say that if it has no documentation, it does not exist (to the user/contributor). I also think that code is a way of communicating with your future self or future developers. So clear code and clear documentation is important. Code is not important to the computer, the computer does not care about naming things.
From another perspective: Whilst I am likely to spend far more time documenting than coding in my work, when I build something at home to fix a problem just for me I'm far less likely because it's for me.
In the case of this particular developer, it isn't just for themselves, but also in a different language, and they've done their best just to reflect an existing API. They've asked for pull requests.
I can understand not wanting to do the enormous amount of work of translating an API that is already pretty-much documented when I won't really see any return at all.
I find it quite frustrating that open source/current company projects have no or little documentation. Even for a 12 days project it is frustrating. It is just good habit that documentation is as important as code. I like to say that if it has no documentation, it does not exist (to the user/contributor). I also think that code is a way of communicating with your future self or future developers. So clear code and clear documentation is important. Code is not important to the computer, the computer does not care about naming things.