-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the status of libmodbus-ascii effort? #659
Comments
Um... bump? :) Over at NUT project we actually have two separate efforts by now that require better libmodbus features than available in the published library (ascii, and now also usb investigated per networkupstools/nut#2063). I would be not too comfortable having NUT publish an alternative fork of the better-featured common library - it would be some burden for us and mostly confusing for end-users (especially if they end up installing two forks and have to resolve conflicts at compile- or run-times), but fear it may come to this for practical reasons... |
Unfortunately, in my opinion, it appears that active development of the project has nearly ended and now it's in maintenance mode, only fixes and cleanups are made without adding any new feature anymore. The maintenance also seems to be not very active, since not even a buffer overflow bug reported early this year has received a response or fix by project maintainers. The only chance that one can bring any real changes in is sending a Pull Request - the good old "patch welcome" - which is fair enough, but most PRs I see are simple fixes. I'm not sure whether more complex patches will be reviewed, especially new-feature patches. Are the project maintainers still willing to review big patches to bring in major features like libmodbus-ascii? If so, perhaps we can make a upstream attempt. If not, I'm afraid that a fork is inevitable... |
Feel free to rebase the ASCII branch and update it. |
Hello, we have had a new NUT driver proposal at networkupstools/nut#1671 which included some combination of libmodbus-ascii sources as needed for that new driver to communicate with an UPS (I am double-checking with the author if that can work with released RTU support instead).
It seems that the libmodbus-ascii sources are around for a quite a while, so there may have been good reasons to not merge them into main codebase and distribute everywhere, e.g. not well enough tested, not too portable, known unreliable, or something around that?
Then there is also a legaleze question about mixing your LGPL with our GPL, if some sources are snatched from the libmodbus project to provide a (fallback at least) implementation for one of many optional programs that can be built in NUT...
Should we be wary about the codebase on technical grounds - that even authors deemed it not mature enough to release, and so insist on rewrite of the submitted NUT driver?
Alternately, maybe it just "fell through the cracks" and you can just merge and release it officially, so NUT with the new driver may just depend on the OS/distro provided builds of libmodbus package (like it already does with some other drivers added in the past year or two)? :)
The text was updated successfully, but these errors were encountered: