LCM Status

[Kyle Kauffman]

Hi all,

Until recently, the LCM project displayed a notice stating that it was seeking a new maintainer. My team makes extensive use of LCM internally, so we volunteered to step in and keep LCM updated with bugfixes and stable releases. However, we would love to collaborate with anyone here who has time and interest to pitch in. If that describes you, please let us know.

Our current priorities are to keep the Java, Python, and C/C++ targets up to date. We don't have use cases for the other targets, so in the short term we are planning to mark them as unmaintained. The goal here is to let users know to expect issues if they try to use them. Ideally all of the LCM targets would stay active and find maintainers who were interested in keeping them current. To that end, if anyone here is actively using the Lua, .NET, or Go targets and would like to help keep them up to date, we would love to hear from you. Otherwise, we will proceed with the plan to keep them in the tree but marked as unmaintained. We will still review PRs for them, but they will not be actively/continuously tested.

We are planning to make a new release in the near future, once the roadmap[1] issues are addressed.

Please let us know if there are any questions or issues.

[1] https://github.com/lcm-proj/lcm#roadmap

[Tim Perkins]

You can count me as the maintainer of the Lua binding. I am the original author. I can do code reviews.