It means that if you’re going to attempt this:
…then you should make yourself aware of any previous attempts to merge and reasons that it didn’t happen. I don’t know the history, but the original binding was created long enough ago that I imagine a PR was discussed at some point.
Some other things to consider:
- Merging for 3.4 doesn’t really do much, because developers are now working toward 4.0 and there won’t be a 3.5. So you’d want to aim for 4.0 compatibility in a PR.
- The official Broadlink thermostat binding has been expanded to include IR remote functionality, I gather that it’s limited, but there would be redundancy. (I think this is what @matt1 was referring to as “the other binding”)
If you submit a PR, you would (in my opinion) be taking on the role of developer/maintainer to ensure that the binding continues to work in the future. It’s great if you plan to do that, but not so much if you were thinking of this as a one-time deal.
Alternatively, you can just compile the binding and post it in the third-party marketplace, which may not have existed when the previous developer was still active in the community. This avoids the burden of merging a PR, and if you decide to walk away in the future, you can just say that you’re no longer updating it.