I would suggest that there are times where each is appropriate. I will
take a look at this class and submit a pull request that does both
things - log the info-level stuff at info level, and if there is a
problem log the stacktrace at debug level.
Also, Nathan is very open to pull requests - if you find things you want to improve, by all means submit a pull request! If you are not familiar with the github workflow, the basic idea is that you create a fork of the repository in your own github account, make the changes you want, and then use github to submit a pull request. Nathan can then review the request, make comments on it, and when everyone agrees it looks good, he can merge it in to the main codeline. Once you've done it and seen how easy it is, it is pretty magical.
Also, Nathan is very open to pull requests - if you find things you want to improve, by all means submit a pull request! If you are not familiar with the github workflow, the basic idea is that you create a fork of the repository in your own github account, make the changes you want, and then use github to submit a pull request. Nathan can then review the request, make comments on it, and when everyone agrees it looks good, he can merge it in to the main codeline. Once you've done it and seen how easy it is, it is pretty magical.