These were not any special “initiatives”, that’s common sense. We need to make a public release, we make a deeper dive into our app, we fix bugs. If a bug is in an external library, we try to fix it upstream because we don’t want to support/update a separate fork of a library.
Sure, I see you have your pet peeves in the app, but try installing a version from the beginning of 2018 and compare it to what we have now
So, my logic behind all this is that if the app is getting better, it means that what we do works, somehow. Sure it is a very subjective feeling, but the last thing I want is to make everyone to try to optimize some metric as a KPI. In general, treating code quality by then number of open bugs is hardly better then measuring programmer’s productivity by lines of code written.
A huge amount of issues in the repo is also explained by the fact that we used to use them for project management and coordination and now we mostly not. So it is good that the bot is closing them.
On the other hand, you are doing a nice job of keeping some of the bugs alive, thanks!