There are several aspects that could help. Yes more reviewers will help, but reviewing new bindings is just very intensive to do, and that is hard to change if we want to keep some kind of level of quality. For example I think it will take me about 4 hours to do an intensive initial review of a new binding and I know most of the pitfalls. What makes it harder is most binding developers have limited programming experience and make lots of small errors, sloppy programming, copy-pasting all over the place. And all those things are important to not have a single binding bring down OH once it runs resulting in bad experiences and even more support questions. So we try to take a good look at the code. But these things result in a lot of review time and iterations.
Having said that there are other things that could improve. For example it would ease the review process if the analysis report messages that the build process puts in a report are directly added into GitHub as review comments. We could even add some more common issues I see regularly to it. I want to look into how this could be made possible with the pull request. This could lift some of the burden of the reviewers. Because reviewing is one thing, what also costs time is the re-review process. Once a developers fixes things, it needs to re-reviewed. Since this mostly takes several iterations it can takes weeks (due to availability) before this completes.
While having the binding merged is great. It’s already possible to distribute the binding to users. At the moment this can be done through the Eclipse Market Place. That way users can already easily install the binding from within openHAB. I use it for new bindings and new features/bug fixes on existing bindings. While the Eclipse Market Place is going away due to changes related to the core there should be something similar become available. And I hope that will also make it easier to have pr pending bindings available.
Related to this specific binding. Technically it was first a wip, which means no reviews. So September isn’t completely accurate. Also with the recent changes to core, which has taken a lot of effort for the core developers that are also reviewers they simply hadn’t time to do reviews only adding more review request to the backlog, and yes that comes back to more reviewers would be great. Even with this: merging bindings still takes a long time…
In the end a binding will be merged at some point, but contributors shouldn’t think to lightly about having their binding merged and need to have some patience. I don’t know if we ever can speed it up. What I did was when I first contributed my first binding is to review other bindings, with the idea if those bindings are reviewed the actual reviewers have more time for my binding. In the process I actually learned a lot about how openHAB works (although I can image not everybody wants to do that).